Topic: No ESLint configuration found
Виталий Малиновский (L2poisk) free asked 6 years ago
Hi. i have a problem with ESlint. Try to explain whats happened..
1. I download a .zip from your website. for development in vue js. everything is Ok (run dev, run build), working good.
2. when i finish my project and push it on my github repository after that download it on my device, i run "npm install" and install all dependencies.
3. When all dependencies are installed. I try to build my project and get the error:
ERROR in ./src/main.js
Module build failed (from ./node_modules/eslint-loader/index.js):
Error: No ESLint configuration found.
at Config.getLocalConfigHierarchy (/Users/olarisrey/Desktop/test/node_modules/eslint/lib/config.js:255:39)
at Config.getConfigHierarchy (/Users/olarisrey/Desktop/test/node_modules/eslint/lib/config.js:179:43)
at Config.getConfigVector (/Users/olarisrey/Desktop/test/node_modules/eslint/lib/config.js:286:21)
at Config.getConfig (/Users/olarisrey/Desktop/test/node_modules/eslint/lib/config.js:329:29)
at processText (/Users/olarisrey/Desktop/test/node_modules/eslint/lib/cli-engine.js:163:33)
at CLIEngine.executeOnText (/Users/olarisrey/Desktop/test/node_modules/eslint/lib/cli-engine.js:620:17)
at lint (/Users/olarisrey/Desktop/test/node_modules/eslint-loader/index.js:253:17)
at Object.module.exports (/Users/olarisrey/Desktop/test/node_modules/eslint-loader/index.js:248:21)
Build failed with errors.
And i don't have any .eslintrs.js on my project. but when i downloaded from your site .eslintrs.js was there.
Best regard,
VITALIY
Jakub Strebeyko staff answered 6 years ago
Hi there @Виталий Малиновский (L2poisk),
Welcome to the support board! Happy to see you're using the library.
So, the issue here is caused by what you said yourself - the webpack.base.conf.js you're using for compilation tries to pull the code through a eslint-loader, while there is no eslintrc.js anywhere.
The problems keep on piling on, though. In general, your webpack conf expects a PostCSS config file, too, nowhere to be found. How did you end up with a webpack config that obviously is not fit for your project?
Suggestion: Maybe I'm missing something -- please prove me wrong -- but why use a custom webpack build step if there is Vue CLI 3 and up? You can use it to cut all that messy config out of your project (have it done for you, hidden from sight) while scaffolding the whole project structure and importing mdbvue through npm. Doing there two easy steps and adding your original content (components, router etc.) should have you working in no time.
With Best Regards,
Kuba
FREE CONSULTATION
Hire our experts to build a dedicated project. We'll analyze your business requirements, for free.
Answered
- ForumUser: Free
- Premium support: No
- Technology: MDB Vue
- MDB Version: 4.8.2
- Device: MacBook Pro 2016
- Browser: Chrome
- OS: Mac OS Mojave 10.14.1
- Provided sample code: Yes
- Provided link: Yes