hatch-surf/node_modules/eslint-plugin-import/docs/rules/no-nodejs-modules.md
Riley Zhang df378d33ef
Some checks failed
CI / go (push) Waiting to run
CI / docker (push) Waiting to run
CI / lint-go (push) Waiting to run
CI / lint-docs (push) Waiting to run
CI / check-paperclip (push) Waiting to run
Deploy static site / Deploy to GitHub Pages (push) Has been cancelled
Deploy static site / Deploy via Docker to hatch.surf (push) Has been cancelled
Merge GitHub main into Gitea repo (allow unrelated histories)
Resolved conflicts by taking GitHub versions for:
- .dockerignore, .gitignore, Dockerfile, README.md, docker-compose.yml

Kept deploy.sh updated to:
- Pull from GitHub (primary source)
- Push to Gitea (push-mirror)
- Build from site/ directory (GitHub structure)

Co-Authored-By: Paperclip <noreply@paperclip.ing>
2026-06-25 05:20:46 +02:00

43 lines
829 B
Markdown

# import/no-nodejs-modules
<!-- end auto-generated rule header -->
Forbid the use of Node.js builtin modules. Can be useful for client-side web projects that do not have access to those modules.
## Options
This rule supports the following options:
- `allow`: Array of names of allowed modules. Defaults to an empty array.
## Rule Details
### Fail
```js
import fs from 'fs';
import path from 'path';
var fs = require('fs');
var path = require('path');
```
### Pass
```js
import _ from 'lodash';
import foo from 'foo';
import foo from './foo';
var _ = require('lodash');
var foo = require('foo');
var foo = require('./foo');
/* eslint import/no-nodejs-modules: ["error", {"allow": ["path"]}] */
import path from 'path';
```
## When Not To Use It
If you have a project that is run mainly or partially using Node.js.