npm run dev not opening port #747

sysmat · 2023-07-05T09:29:30Z

Describe the Bug

npm run dev -> nothing happend

Which package is affected (leave empty if unsure)

react-email

Link to the code that reproduces this issue

https://stackblitz.com/edit/stackblitz-starters-tcqzzt?file=react-email-starter%2Freadme.md

To Reproduce

npx create-email@latest
ncu -u
npm i
npm run dev -> nothing happend

Expected Behavior

to start dev server on http://localhost:3001 as in readme documentation

What's your node version? (if relevant)

Node: 18.16.0

bukinoshita · 2023-07-06T17:17:10Z

@sysmat Can you share more information? Is this on Mac? Windows? Linux?

Here's the same steps

CleanShot.2023-07-06.at.14.13.34.mp4

sysmat · 2023-07-07T07:24:06Z

@bukinoshita on windows power shell

zedo-san · 2023-07-07T09:10:13Z

I also have the same setup and is experiencing the same issue

Rivoks · 2023-07-09T11:37:39Z

Hello me too, when launching npm run dev it is starting and then closing immediately the process.
Node version: v19.8.1

mortocks · 2023-07-11T06:47:13Z

+1

node 18.16.0
pnpm 8.6.3

on Mac

bukinoshita · 2023-07-11T15:41:40Z

All windows? Or anyone having this issue on Mac?

mezg0 · 2023-07-12T11:29:39Z

Yeah same issue for me on Mac

mortocks · 2023-07-12T14:09:06Z

All windows? Or anyone having this issue on Mac?

Mac (sorry should have said). M2 running 13.4.1

mortocks · 2023-07-12T14:28:25Z

Today (24 hours after my original post) it suddenly started working (no changes to the code base or system restarts. The first thing it did was download a bunch of dependancies.

I'm wondering if perhaps a host for one of these dependancies was down and there's no error handing in the startup process? 🤷‍♂️

Just a new data point

bighoho123 · 2023-07-13T07:36:27Z

Same here.
Mac M1 react-email@1.9.4

Running email script exits immediately (without error)

bighoho123 · 2023-07-13T11:17:14Z

npm uninstall react-email
then
npm install react-email -D -E fixed my issue

zedo-san · 2023-07-14T02:21:09Z

I tried installing the previous version "react-email": "1.9.0" and it works fine for me. I'm using a windows machine. Here's my full package.json file

{
  "name": "react-email-p1",
  "version": "1.0.0",
  "description": "",
  "main": "index.js",
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1",
    "dev": "email dev"
  },
  "author": "",
  "license": "ISC",
  "dependencies": {
    "@react-email/button": "0.0.7",
    "@react-email/components": "0.0.4",
    "@react-email/container": "0.0.8",
    "@react-email/html": "0.0.4",
    "@react-email/tailwind": "0.0.7",
    "react-email": "1.9.0"
  }
}

stbensonimoh · 2023-07-14T20:41:05Z

I had the same issue. I had to use npx react-email dev instead of npm run dev before it worked for me.

Rivoks · 2023-07-22T14:35:16Z

With the latest version 1.9.4 i got this error when I run the npm dev:

> email dev --port 8888 --dir src/emails

(node:30994) [DEP0164] DeprecationWarning: Implicit coercion to integer for exit code is deprecated.
(Use `node --trace-deprecation ...` to show where the warning was created)

I am on Mac OS 13.2.1 and on a M1 chipset.

EavOutDom · 2023-09-23T04:44:00Z

I also have the same issue on windows

Aleksandern · 2023-11-06T02:40:45Z

react-email downloads the client code on the start (about 24 MB) so make sure you have a good internet connection or just wait for a while.
That was my issue.

gabrielmfern · 2024-01-27T11:53:31Z

This should not happen the same as of react-email@2.0.0 and should now be fixed.

Check the changelog and our blog post for more info on this.

If anyone is still experiencing this with 2.0.0 let me know and I'll reopen this issue.

Yashhh08 · 2024-02-09T07:34:12Z

$ npm run email

> emails@0.1.0 email
> email dev

    React Email 2.0.0
    Running preview at:          http://localhost:3000

  ⠙ Getting react-email preview server ready...
Error: > Couldn't find any `pages` or `app` directory. Please create one under the project root
    at findPagesDir (D:\Yash Yerunkar\Email Templates\emails\node_modules\react-email\node_modules\next\dist\lib\find-pages-dir.js:42:15)
    at initialize (D:\Yash Yerunkar\Email Templates\emails\node_modules\react-email\node_modules\next\dist\server\lib\router-server.js:71:69)
    at async NextCustomServer.prepare (D:\Yash Yerunkar\Email Templates\emails\node_modules\react-email\node_modules\next\dist\server\next.js:240:28)

shutting down dev server

getting above issue my package.json configs are as below:

{
"name": "emails",
"version": "0.1.0",
"private": true,
"scripts": {
"dev": "next dev",
"build": "next build",
"start": "next start",
"lint": "next lint",
"email": "email dev"
},
"dependencies": {
"@react-email/components": "0.0.14",
"next": "14.1.0",
"react": "^18",
"react-dom": "^18",
"react-email": "2.0.0"
},
"devDependencies": {
"@types/node": "^20",
"@types/react": "^18",
"@types/react-dom": "^18",
"autoprefixer": "^10.0.1",
"postcss": "^8",
"tailwindcss": "^3.3.0",
"typescript": "^5"
}
}

codeScourge · 2024-04-16T09:34:10Z

I am still having this issue on Windows (inside WSL) when working with Bun on the latest version of react-email@2.1.1
I can get it to work by downgrading to react-email@1.9.0

When starting, it just automatically closes the dev server without any error:

scourge@ivan:/mnt/c/Users/codes/code/playground/react-email-starter$ bun dev
$ email dev
    React Email 2.1.1
    Running preview at:          http://localhost:3000

  ⠙ Getting react-email preview server ready...

shutting down dev server

gabrielmfern · 2024-04-19T15:46:36Z

@codeScourge Could you provide a reproduction for this? Seems to be another issue other than the one here.

codeScourge · 2024-04-21T07:04:31Z

@codeScourge Could you provide a reproduction for this? Seems to be another issue other than the one here.

Hi, thank you for helping. Here is the reproduction: https://github.com/codeScourge/react-email
There are some more details in the ReadME

gabrielmfern · 2024-04-23T14:44:25Z

@codeScourge I think I've figured it out. When running on WSL you might have not installed Node at all, in that case, it seems like it fails the same you mentioned. It also fails the same way when running with bun --bun dev while having Node installed. So it seems like bun falls back to running with its runtime if Node isn't installed, so basically it runs bun --bun dev. Haven't checked on their code and I couldn't find anything related to this on their docs.

Could you open an issue with your reproduction and this documented as well? Some error might be happening due to some incompatibility with bun, and I'll try taking a look right now. Just want to move our conversation there instead.

codeScourge · 2024-04-25T06:05:10Z

@codeScourge I think I've figured it out. When running on WSL you might have not installed Node at all, in that case, it seems like it fails the same you mentioned. It also fails the same way when running with bun --bun dev while having Node installed. So it seems like bun falls back to running with its runtime if Node isn't installed, so basically it runs bun --bun dev. Haven't checked on their code and I couldn't find anything related to this on their docs.

Could you open an issue with your reproduction and this documented as well? Some error might be happening due to some incompatibility with bun, and I'll try taking a look right now. Just want to move our conversation there instead.

Sure, it is up at #1429

sysmat added the Type: Bug Confirmed bug label Jul 5, 2023

bukinoshita added Resolution: Needs More Information More information is needed on this issue and removed Type: Bug Confirmed bug labels Jul 6, 2023

bukinoshita changed the title ~~"react-email": "1.9.4" nothing works~~ npm run dev not opening port Jul 6, 2023

bukinoshita added Type: Bug Confirmed bug Package: react-email This is the CLI we generally use as just `email` on the temrinal. and removed Resolution: Needs More Information More information is needed on this issue labels Jul 14, 2023

gabrielmfern closed this as completed Jan 27, 2024

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

npm run dev not opening port #747

npm run dev not opening port #747

sysmat commented Jul 5, 2023

bukinoshita commented Jul 6, 2023

sysmat commented Jul 7, 2023

zedo-san commented Jul 7, 2023

Rivoks commented Jul 9, 2023 •

edited

Loading

mortocks commented Jul 11, 2023 •

edited

Loading

bukinoshita commented Jul 11, 2023

mezg0 commented Jul 12, 2023

mortocks commented Jul 12, 2023

mortocks commented Jul 12, 2023

bighoho123 commented Jul 13, 2023

bighoho123 commented Jul 13, 2023

zedo-san commented Jul 14, 2023

stbensonimoh commented Jul 14, 2023

Rivoks commented Jul 22, 2023 •

edited

Loading

EavOutDom commented Sep 23, 2023 •

edited

Loading

Aleksandern commented Nov 6, 2023

gabrielmfern commented Jan 27, 2024

Yashhh08 commented Feb 9, 2024 •

edited

Loading

codeScourge commented Apr 16, 2024

gabrielmfern commented Apr 19, 2024

codeScourge commented Apr 21, 2024

gabrielmfern commented Apr 23, 2024 •

edited

Loading

codeScourge commented Apr 25, 2024

npm run dev not opening port #747

npm run dev not opening port #747

Comments

sysmat commented Jul 5, 2023

Describe the Bug

Which package is affected (leave empty if unsure)

Link to the code that reproduces this issue

To Reproduce

Expected Behavior

What's your node version? (if relevant)

bukinoshita commented Jul 6, 2023

sysmat commented Jul 7, 2023

zedo-san commented Jul 7, 2023

Rivoks commented Jul 9, 2023 • edited Loading

mortocks commented Jul 11, 2023 • edited Loading

bukinoshita commented Jul 11, 2023

mezg0 commented Jul 12, 2023

mortocks commented Jul 12, 2023

mortocks commented Jul 12, 2023

bighoho123 commented Jul 13, 2023

bighoho123 commented Jul 13, 2023

zedo-san commented Jul 14, 2023

stbensonimoh commented Jul 14, 2023

Rivoks commented Jul 22, 2023 • edited Loading

EavOutDom commented Sep 23, 2023 • edited Loading

Aleksandern commented Nov 6, 2023

gabrielmfern commented Jan 27, 2024

Yashhh08 commented Feb 9, 2024 • edited Loading

codeScourge commented Apr 16, 2024

gabrielmfern commented Apr 19, 2024

codeScourge commented Apr 21, 2024

gabrielmfern commented Apr 23, 2024 • edited Loading

codeScourge commented Apr 25, 2024

Rivoks commented Jul 9, 2023 •

edited

Loading

mortocks commented Jul 11, 2023 •

edited

Loading

Rivoks commented Jul 22, 2023 •

edited

Loading

EavOutDom commented Sep 23, 2023 •

edited

Loading

Yashhh08 commented Feb 9, 2024 •

edited

Loading

gabrielmfern commented Apr 23, 2024 •

edited

Loading