flying-hero
96f6318101
新增: - backend/venv/ - Python 虚拟环境 - backend/start.sh - 启动脚本（使用虚拟环境） - backend/requirements.txt - 依赖列表 - .gitignore - 忽略虚拟环境和缓存文件 说明: - 每个项目使用独立虚拟环境 - 避免依赖冲突 - 启动脚本自动创建和激活虚拟环境
977 B
977 B
import/no-amd
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:
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: report CommonJSrequireandexports- Source: https://github.com/xjamundx/eslint-plugin-modules