Error while creating nuxt3 project. Failed to download template from registry-CodePudding

When I use this command to create a new Nuxt 3 project:

npx nuxi init nuxt-app

It outputs this error:

 ERROR  (node:1752) ExperimentalWarning: The Fetch API is an experimental feature. This feature could change at any time                         09:53:25
(Use `node --trace-warnings ...` to show where the warning was created)


 ERROR  Failed to download template from registry: fetch failed                                                                                  09:53:25

  at /C:/Users/myname/AppData/Local/npm-cache/_npx/a95e0f536cf9a537/node_modules/nuxi/dist/chunks/init.mjs:13269:11
  at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
  at async downloadTemplate (/C:/Users/myname/AppData/Local/npm-cache/_npx/a95e0f536cf9a537/node_modules/nuxi/dist/chunks/init.mjs:13268:20)
  at async Object.invoke (/C:/Users/myname/AppData/Local/npm-cache/_npx/a95e0f536cf9a537/node_modules/nuxi/dist/chunks/init.mjs:13336:15)
  at async _main (/C:/Users/myname/AppData/Local/npm-cache/_npx/a95e0f536cf9a537/node_modules/nuxi/dist/cli.mjs:50:20)

My environments:

Operating System: Windows 11
node version : 18.12.0
npm version: 8.12.1

At first I suspected that this was due to my network. But I didn't get an error when I tried to install other npm packages.

CodePudding user response：

I got the same issue while working at a client (bank), this is mainly a network restriction indeed. They are limiting the access to only a few NPM packages and this one is not whitelisted (mainly the template).

Not sure how to properly bypass it other than manually getting the code with an SSH/HTTP clone or maybe asking them to allow that specific endpoint.

CodePudding user response：

I found the reason in here.

It's indeed a network issue. It couldn't access raw.githubusercontent.com from the command line because it couldn't find the corresponding IP address.

After adding the correct ip address of raw.githubusercontent.com to the Windows hosts file, the issue was fixed