create-nuxt-app
create-nuxt-app copied to clipboard
Problem with yarn dev command
yarn dev yarn run v1.21.1 $ nuxt i Parsed 1 files in 0,0 seconds @nuxt/content 12:54:57
╭───────────────────────────────────────╮ │ │ │ Nuxt.js @ v2.14.3 │ │ │ │ ▸ Environment: development │ │ ▸ Rendering: server-side │ │ ▸ Target: server │ │ │ │ Listening: http://localhost:3000/ │ │ │ ╰───────────────────────────────────────╯
i Preparing project for development 12:55:00 i Initial build may take a while 12:55:00
WARN Components directory not found: ~/components/global 12:55:00
√ Builder initialized 12:55:00 √ Nuxt files generated 12:55:00
ERROR Plugin not found: F:[PROJECTS]\web\Nuxt.js\netlify-cms.nuxt\components\plugin.js 12:55:00
at node_modules@nuxt\builder\dist\builder.js:6075:15 at async Promise.all (index 0) at async Builder.build (node_modules@nuxt\builder\dist\builder.js:5640:5) at async Object._buildDev (node_modules@nuxt\cli\dist\cli-dev.js:106:5) at async Object.startDev (node_modules@nuxt\cli\dist\cli-dev.js:64:7) at async Object.run (node_modules@nuxt\cli\dist\cli-dev.js:51:5) at async NuxtCommand.run (node_modules@nuxt\cli\dist\cli-index.js:2810:7)
thanks in advance for the help
I use this config when create the project
Language: Javascript Package manager: Yarn UI framework: Vuetify.js Modules: [ Axios, Content, PWA ] Linting: ESLint Testing: None Rendering mode: Universal Target: Server
I just moved one folder to Nuxt components and got this warning !
WARN Components directory not found: ~/components/global
I'm having the same problem. Any one have a guess on this?
Its just a warning to tell you that there is no global folder inside components. This is only needed if you want to add components inside your markdown without having to write any import statements. So it should be more a friendly tip than a warning in my opinion. We could also add it to create nuxt-app with a readMe inside explaining what it does 🧐
Hi @debs-obrien ! Thanks for taking the time to reply. "We could also add it to create nuxt-app with a readMe inside explaining what it does" Good call! as for newbies like myself will save us time. :)
any news ? how to fix it ?
I am stuck on this from last two days can't found any solution
But that issue only come when auto import component by using components: true in nuxt.config.js. If components:false set than working fine
╭───────────────────────────────────────╮ │ │ │ Nuxt @ v2.15.8 │ │ │ │ ▸ Environment: development │ │ ▸ Rendering: server-side │ │ ▸ Target: static │ │ │ │ Listening: http://localhost:3000/ │ │ │ ╰───────────────────────────────────────╯
i Preparing project for development 20:47:42
i Initial build may take a while 20:47:42
i Discovered Components: .nuxt/components/readme.md 20:47:42
√ Builder initialized 20:47:42
√ Nuxt files generated 20:47:42
ERROR Plugin not found: C:\Users\akaas\Documents\GitHub\pachmisheli.nuxt\components\plugin.js 20:47:42
at node_modules@nuxt\builder\dist\builder.js:740:15 at async Promise.all (index 0) at async Builder.build (node_modules@nuxt\builder\dist\builder.js:324:5) at async Object._buildDev (node_modules@nuxt\cli\dist\cli-dev.js:107:5) at async Object.startDev (node_modules@nuxt\cli\dist\cli-dev.js:65:7) at async Object.run (node_modules@nuxt\cli\dist\cli-dev.js:52:5) at async NuxtCommand.run (node_modules@nuxt\cli\dist\cli-index.js:413:7)
same problem !!!!!!!!!!!!!!!!!!!!
ERROR Plugin not found:
I watch too many video and read many articles but problems continues come, for now i set components:false in nuxt.config.js and it's run. it's not a proper solution but for now I doing other basic staff

This problem seems to appear only on windows.
After trying the @ElyFura's tip i had to run the below command to get rid of all the errors
export NODE_OPTIONS=--openssl-legacy-provider
I tried in ubuntu after run export NODE_OPTIONS=--openssl-legacy-provider, it's working fine
but on windows no solutions work
I my case the problem, was the node version i was using on my Windows 11. I was using 17.x, I switched to 16 and the problem was gone. You will find in the documentation nuxtjs.org that the LTS is the version to use.
@MarienMupenda thanks bro, finally fixed. same issue
after switch latest stable version of node js which is 16.5 and latest nuxtjs verison which is currently 2.15.8, my issue is finally fixed.
So that's the issue because of nuxtjs and nodjs lts verison mismatch. Really Thanks
You're welcome @mahesh2237, happy coding!