vite build failed with vite-plugin-eslint 1.8.0
See original GitHub issuefailure in npm run build
(vite build)
[commonjs--resolver] Cannot read config file: ***********************/node_modules/@css-render/vue3-ssr/.eslintrc.js
Error: Cannot find module '@rushstack/eslint-config/patch/modern-module-resolution'
even after @rushstack/eslint-config
installed, the error would be
[commonjs--resolver] Failed to load config "@css-render/eslint-config/base" to extend from.
Referenced from:***********************/node_modules/@css-render/vue3-ssr/.eslintrc.js
rolling back to 1.7.0 would just work fine.
Issue Analytics
- State:
- Created a year ago
- Comments:5 (1 by maintainers)
Top Results From Across the Web
vite-plugin-eslint - npm
Will cause the module build to fail if there are any warnings, based on emitWarning . failOnError. Type: boolean; Default: true. Will cause...
Read more >gxmari007/vite-plugin-eslint - GitHub
Will cause the module build to fail if there are any warnings, based on emitWarning . failOnError. Type: boolean; Default: true. Will cause...
Read more >Vite-plugin-eslint - npm.io
Will cause the module build to fail if there are any warnings, based on emitWarning . failOnError. Type: boolean; Default: true. Will cause...
Read more >Storybook vite failed to build with ChakraUI / React 18
I'm creating a UI library with Vite and Storybook. Sadly, the storybook build is broken. In dev mode, i have some error during...
Read more >[eslint] failed to load config "@vue/prettier" to extend from.
My assumption is that "no-layout-rules" means that the build is missing dependencies. In my case, after removing "@vue/prettier" from my config NPM right...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I have same issue. fix by replacing include value
I can confirm the bugfix 👍