question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[Bug]: Express CLI starter doesn't appear to run

See original GitHub issue

Which 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

Create a new project and run through the prompts using the executable script and choose to create the project with Express in Typescript.

❯ node -v
v16.13.0
❯ npm -v
8.1.0
❯ npx create-remix@latest

R E M I X

💿 Welcome to Remix! Let's get you set up with a new project.

? Where would you like to create your app? ./test-remix
? Where do you want to deploy? Choose Remix if you're unsure, it's easy to change deployment targets. Express Server
? TypeScript or JavaScript? TypeScript
? Do you want me to run `npm install`? Yes

> postinstall
> remix setup node

Successfully setup Remix for node.

added 392 packages, and audited 393 packages in 21s

107 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities
💿 That's it! `cd` into "test-remix" and check the README for development and deploy instructions!

Try to run the development environment and see that the server never starts.

❯ npm run dev

> dev
> remix watch

Watching Remix app in development mode...
💿 Built in 323ms

Expected Behavior

I expected to be able to see that localhost:3000 is ready in the logs but don’t see it and can’t access the site.

Actual Behavior

The script halts and does not start the local development server.

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Comments:6

github_iconTop GitHub Comments

2reactions
antgonzalescommented, Nov 23, 2021

@mikebobadilla Adding @remix-run/serve had no effect unfortunately. @pixelmund’s solution appears to work tho. You have to build and then start dev.

npm run build && npm run start:dev
1reaction
pixelmundcommented, Nov 23, 2021

For express you have to run the start:dev command separately i guess.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Start script missing error when running npm start
It looks like you might not have defined a start script in your package.json file or your project does not contain a server.js...
Read more >
How to Diagnose a No Crank No Start Issue - YouTube
In this video I go over how you can perform a no crank no start diagnosis, whether all you hear is a click...
Read more >
Solving Common Aftermarket Starter Problems - OnAllCylinders
Problem: Starter does not turn or turns over slowly when key is turned. Solution #1: Check the rest of the electrical system for...
Read more >
Car Won't Start & There's a Clicking Noise? - CarParts.com
No-crank-no-start condition – means the engine barely turns over or doesn't turn over at all. Typically, this points to a problem somewhere in ......
Read more >
Quick Start | Electron
author and description can be any value, but are necessary for app packaging. Your package.json file should look something like this: {
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found