You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
$ npm run serve
> my-project@0.1.0 serve
> vue-cli-service serve
INFO Starting development server...
98% after emitting CopyPlugin
ERROR Failed to compile with 1 errors 19:48:55
Module build failed (from ./node_modules/@vue/cli-plugin-eslint/node_modules/eslint-loader/index.js):
TypeError: eslint.CLIEngine is not a constructor
at Object.module.exports (~/work/oss-gate/my-project/node_modules/@vue/cli-plugin-eslint/node_modules/eslint-loader/index.js:223:27)
You may use special comments to disable some warnings.
Use // eslint-disable-next-line to ignore the next line.
Use /* eslint-disable */ to ignore all warnings in a file.
What is expected?
It seems that the problem has already been fixed in the dev branch (vuejs/vue-cli#6714), but I don't think the fix has been applied to the v4 branch.
Is is possible to backport that fix to v4 branch?
What is actually happening?
TypeError: eslint.CLIEngine is not a constructor is raised.
Supplementary information
If you ignore the vulnerability issue message and don't run npm audit fix --force, you won't get an error when you run npm run serve.
The text was updated successfully, but these errors were encountered:
Version
4.5.15
Environment info
Steps to reproduce
npm install -g @vue/cli
to install the Vue CLI globally.vue create my-project
to create the project.cd my-project
and navigate to the directory where the project you created is located.npm audit fix --force
because you will get a message that there is a vulnerability problem during installation.npm run serve
.TypeError: eslint.CLIEngine is not a constructor
is raised.What is expected?
It seems that the problem has already been fixed in the
dev
branch (vuejs/vue-cli#6714), but I don't think the fix has been applied to thev4
branch.Is is possible to backport that fix to
v4
branch?What is actually happening?
TypeError: eslint.CLIEngine is not a constructor
is raised.Supplementary information
If you ignore the vulnerability issue message and don't run
npm audit fix --force
, you won't get an error when you runnpm run serve
.The text was updated successfully, but these errors were encountered: