Error message when setting up a Vite React project: npm warns about unknown config

Other Questions NPM
1

I’m having trouble setting up a new Vite React project. When I run the command to create it, I get a weird warning about an unknown config. Here’s what I typed:

npm create vite@latest my-cool-app -- --template react -y

But then I see this:

npm WARN Unknown cli config "--template"

The app doesn’t get created like it should. I’m using Node v22.14.0 and npm v11.2.0 on Windows 10 Pro.

I also tried without the double dashes, but no luck. Any ideas on how to fix this? I just want to make a Vite React project without having to pick options manually. Help would be awesome!

2

hey dancingfox, i had the same issue! try using ‘npm init vite@latest my-cool-app --template react’ instead. the ‘–’ isn’t needed for npm init. also, make sure ur using the latest npm version (run ‘npm update -g npm’). hope this helps ya out!

3

I encountered a similar issue recently. The problem lies in how npm interprets command-line arguments. For Vite projects, it’s better to use ‘npm create’ or ‘yarn create’ instead of ‘npm init’. Here’s the command that worked for me:

npm create vite@latest my-cool-app --template react

This syntax avoids the warning about unknown configs. Also, ensure you’re in the directory where you want to create the project before running the command. If you’re still having trouble, try using Yarn as an alternative package manager:

yarn create vite my-cool-app --template react

These methods should create your Vite React project without manual intervention. Let me know if the issue persists.

4

I’ve dealt with this exact problem before, and it can be frustrating. The issue is actually with how npm handles the command-line arguments for Vite. Here’s what worked for me:

Instead of using ‘npm create’, try using ‘npx’ directly. Run this command:

npx create-vite@latest my-cool-app --template react

This bypasses the npm wrapper and calls the create-vite package directly, which should avoid the config warning. Make sure you’re in the right directory before running it.

If that doesn’t work, you might want to check your global npm configurations. Sometimes, old or conflicting configs can cause issues. Try running ‘npm config list’ to see if there’s anything unusual.

Lastly, if all else fails, consider using a different package manager like Yarn or pnpm. They sometimes handle these edge cases better than npm.