I'm getting 'module' is not defined error from the eslint in .eslintrc.js file.
What does this mean and how do I fix it?
1
- Does this answer your question? ESLint - 'process' is not definedHenke– Henke2023-11-09 16:00:58 +00:00Commented Nov 9, 2023 at 16:00
Add a comment |
3 Answers
You need to add an environment setting inside your .eslintrc.js file, i.e.:
... env: { node: true }, ... That said, the error in the .eslintrc.js file itself should only appear in Visual Studio Code, because ESLint ignores file names that start with a dot per default.
3 Comments
Minh Nghĩa
If my
.eslintrc.js is used in a React project, should this line be added?
Max Stevens
What worked for me was adding
/* eslint-env node */ to the top of my .eslintrc.js, thus avoiding setting the environment to nodeBe careful blindly setting the node environment in all projects. If the application is not going to be running on node (e.g. a browser application), don't set the whole project to use the node environment just to prevent linting errors in the config file. It's better to just not lint this file instead, or potentially set up a different set of rules for it.
To ignore it, just add the following to the .eslintrc.js file.
'ignorePatterns': [ '.eslintrc.js' ], 
1 Comment
Muhammad Amir
Please could you explain what is the reason for this error?
convert to es5 by writing export default { } instead of module.export = {}
2 Comments
Community
As it’s currently written, your answer is unclear. Please edit to add additional details that will help others understand how this addresses the question asked. You can find more information on how to write good answers in the help center.
Simo Kivistö
Tested with the as-of-the-moment lastest eslint version 8.48.0 and getting
"SyntaxError: Unexpected token 'export'" after changing .eslintrc to use export default.