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
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>
38 lines
977 B
Markdown
38 lines
977 B
Markdown
# import/no-amd
|
|
|
|
<!-- end auto-generated rule header -->
|
|
|
|
Reports `require([array], ...)` and `define([array], ...)` function calls at the
|
|
module scope. Will not report if !=2 arguments, or first argument is not a literal array.
|
|
|
|
Intended for temporary use when migrating to pure ES6 modules.
|
|
|
|
## Rule Details
|
|
|
|
This will be reported:
|
|
|
|
```js
|
|
define(["a", "b"], function (a, b) { /* ... */ })
|
|
|
|
require(["b", "c"], function (b, c) { /* ... */ })
|
|
```
|
|
|
|
CommonJS `require` is still valid.
|
|
|
|
## When Not To Use It
|
|
|
|
If you don't mind mixing module systems (sometimes this is useful), you probably
|
|
don't want this rule.
|
|
|
|
It is also fairly noisy if you have a larger codebase that is being transitioned
|
|
from AMD to ES6 modules.
|
|
|
|
## Contributors
|
|
|
|
Special thanks to @xjamundx for donating his no-define rule as a start to this.
|
|
|
|
## Further Reading
|
|
|
|
- [`no-commonjs`](./no-commonjs.md): report CommonJS `require` and `exports`
|
|
- Source: <https://github.com/xjamundx/eslint-plugin-modules>
|