Topic: ESLint Error at npm start --open
Hello, im getting the following error when im afther unzipping the folder and running npm start --open
"
ERROR Failed to compile with 1 errors 1:47:20 PM
Module build failed (from ./node_modules/eslint-loader/index.js): Error: No ESLint configuration found. at Config.getLocalConfigHierarchy (/var/www/html/PDS/node_modules/eslint/lib/config.js:255:39) at Config.getConfigHierarchy (/var/www/html/PDS/node_modules/eslint/lib/config.js:179:43) at Config.getConfigVector (/var/www/html/PDS/node_modules/eslint/lib/config.js:286:21) at Config.getConfig (/var/www/html/PDS/node_modules/eslint/lib/config.js:329:29) at processText (/var/www/html/PDS/node_modules/eslint/lib/cli-engine.js:163:33) at CLIEngine.executeOnText (/var/www/html/PDS/node_modules/eslint/lib/cli-engine.js:620:17) at lint (/var/www/html/PDS/node_modules/eslint-loader/index.js:253:17) at Object.module.exports (/var/www/html/PDS/node_modules/eslint-loader/index.js:248:21)
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.
"
Can someone help me?
Duplicate of vue/mdb-vue-pro-cant-start-lint-erro
Could you share some more details on which package/what version/from where you are downloading? If it is a pro vue-demo package from GL or our website, they all have the eslintconf.js file the error regards, that's why I'm asking.
Best
Friessen commented 6 years ago
It’s the version 5.0.0 form you’re website and it’s a pro vue package
Jakub Strebeyko staff commented 6 years ago
Sure.
Downloading -> unzipping -> installing dependencies using npm i, and running npm run demo does not bear problems on my end, except a pretty long wait using npm.
Is there anything specific on your way to the eslint warning? Are you running the demo, or rather directly implementing the package into an existing project? Or maybe eslint installed globally is causing the issue? Any details to accurately mimic your local setup are appreciated. When everything else fails, you may always try go initialize the ESlint config file yourself with eslint --init in either the root of the app or /node_modules/.bin/eslint and see, whether it helps.
With Best Regards, Kuba
FREE CONSULTATION
Hire our experts to build a dedicated project. We'll analyze your business requirements, for free.
Answered
- User: Free
- Premium support: No
- Technology: MDB Vue
- MDB Version: 4.8.2
- Device: Linux
- Browser: Chrome
- OS: Ubuntu
- Provided sample code: No
- Provided link: No
Friessen commented 6 years ago
This is output on terminal before the error ocurrs:
npm start --open
yarn run v1.13.0 $ webpack-dev-server --inline --progress --config build/webpack.dev.conf.js --open 94% after asse 94% after seal
Friessen commented 6 years ago
And this is the output of npm install:
npm install
npm WARN deprecated browserslist@2.11.3: Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools. npm WARN deprecated browserslist@1.7.7: Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools. npm WARN deprecated circular-json@0.3.3: CircularJSON is in maintenance only, flatted is its successor. loadDep:yargs → retry ▌ ╢██████████████████████████████████████████████░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░╟ npm WARN prefer global npm@6.7.0 should be installed with -g
Please consider donating to our open collective to help us maintain this package.
https://opencollective.com/webpack/donate
npm WARN optional Skipping failed optional dependency /chokidar/fsevents: npm WARN notsup Not compatible with your operating system or architecture: fsevents@1.2.7 npm WARN acorn-dynamic-import@4.0.0 requires a peer of acorn@^6.0.0 but none was installed. npm WARN vue-demo@5.0.0 No repository field.