components
components copied to clipboard
Problem after 2.1.8, app breaks if using lodash as plugin
Describe the bug If I run npm update, it will update all dependencies and my app stop to work. With only npm i, its all fine. I've debug and discover that the problem comes from @nuxt/components Where 2.1.8 it's all good, and with last 2.2.1 it breaks. I've added a screenshot of the error it appears on console.
To Reproduce It can be related too all the packages I've installed, so dunno how to reproduce this issue alone. I am assuming it will break any app that make use of lodash. I am loading lodash via plugin.
Expected behavior I was not expecting it to break, plus I am not expecting to start needing to import manually in each file the lodash since I'm loading via plugin.
Screenshots Error: https://i.imgur.com/qKOItgf.png Code difference between what works and when it doesn't: https://i.imgur.com/v4FyBgM.png
+1
Do you mind somehow providing a reprodution @Daniel4Digital @andreladocruz ?
From the screenshot above, i can see cache loader is enabled which is an experimental feature. If you can at least use npx nuxi-edge info to share basic information would be nice too :)
Cleaning up node_modules, yarn.lock, and .nuxt might help.
Nuxt project info:
- Operating System:
Linux - Node Version:
v14.17.4 - Nuxt Version:
2.15.8 - Package Manager:
npm - Bundler:
Webpack - User Config:
ssr,head,css,plugins,components,build,buildModules,modules,server,router,axios,proxy,i18n,googleAnalytics,publicRuntimeConfig,recaptcha,vuetify - Runtime Modules:
@nuxtjs/[email protected],8n,@nuxtjs/[email protected],@nuxtjs/[email protected],@nuxtjs/[email protected] - Build Modules:
@nuxtjs/[email protected]
Thanks, @Daniel4Digital. Didn't cleanup help?
Cleaning up node_modules, package-lock, and .nuxt, didn't helped.
And the problem still exist with cache and parallel disabled.
Strange... Do you mind sending me a message on discord (pi0#6582) finding a way you share screen or repo with me and quickly finding the issue together? :)