[Bug]: Could not locate @remix-run/serve on npm run dev
See original GitHub issueWhich Remix packages are impacted?
-
remix(Remix core) -
create-remix -
@remix-run/architect -
@remix-run/cloudflare-workers -
@remix-run/dev -
@remix-run/express -
@remix-run/netlify -
@remix-run/node -
@remix-run/react -
@remix-run/serve -
@remix-run/server-runtime -
@remix-run/vercel
What version of Remix are you using?
1.0.4
Steps to Reproduce
npx create-remix@latest- npm run dev
- Selected
Remix App ServerandTypescript
Expected Behavior
It should start a remix server and serve the app
Actual Behavior
It exits the process with an error Could not locate @remix-run/serve. Please verify you have it installed to use the dev command.
More Info:
Node Version - 12.14.1
NPM Version - 7.19.0
OS:

Please ask out if you need more info.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:3
- Comments:20 (4 by maintainers)
Top Results From Across the Web
Why I can not run Npm run dev? - Stack Overflow
First run npm install cross-env npm install. Then run npm run dev.
Read more >@remix-run/server-runtime - npm
Implement and export values for each type in interface.ts; Re-export types in reexport.ts. Each Remix server runtime package MAY: Re-export the ...
Read more >sass-loader - npm
Start using sass-loader in your project by running `npm i ... Node Sass does not work with Yarn PnP feature and doesn't support...
Read more >echarts - npm
Start using echarts in your project by running `npm i echarts`. ... Issues for bug report and feature requests; Email dev@echarts.apache.org ...
Read more >npm-install - npm Docs
If <folder> sits outside the root of your project, npm will not install the ... and devDependencies will be installed, and the prepare...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

I’m facing the same issue on node v12
but node 16 occurs the same error