The correct command to start npm is actually npm run dev, not npm dev run. If you get the order reversed, you'll encounter various errors, and many beginners have fallen into this trap.
View Original
This page may contain third-party content, which is provided for information purposes only (not representations/warranties) and should not be considered as an endorsement of its views by Gate, nor as financial or professional advice. See Disclaimer for details.
11 Likes
Reward
11
6
Repost
Share
Comment
0/400
ForkMaster
· 11h ago
Oh no, I wouldn't make such a basic mistake anymore. I understood it back when I reviewed the code for the project team. Now, even when teaching three kids to write scripts, I don't make such errors.
View OriginalReply0
SchrodingerAirdrop
· 11h ago
Oops, I've also fallen into this trap before. npm run dev vs npm dev run, the order really matters.
View OriginalReply0
MeltdownSurvivalist
· 11h ago
npm run dev is correct; dev run really misleads people.
View OriginalReply0
GlueGuy
· 11h ago
npm run dev, remember that this order is really crucial
View OriginalReply0
RooftopVIP
· 11h ago
Haha, I also fell for it when the order was reversed. It took me a while to realize that's what was going on.
View OriginalReply0
YieldWhisperer
· 11h ago
Haha, after trying it the other way once, now it's a conditioned reflex.
The correct command to start npm is actually npm run dev, not npm dev run. If you get the order reversed, you'll encounter various errors, and many beginners have fallen into this trap.