I wanted to create a new remotion project, so I ran npm init video to set it up. The project was created successfully. But now when I run npm start in the project I am met with the following error.
An error occurred:
Error: Timeout (1000ms) occurred waiting for 127.0.0.1:3000 to be available
at Socket.<anonymous> (C:\dev\remotion\metromemos\node_modules\@remotion\bundler\dist\get-port.js:19:16)
at Socket.emit (events.js:210:5)
at Socket._onTimeout (net.js:469:8)
at listOnTimeout (internal/timers.js:531:17)
at processTimers (internal/timers.js:475:7)

Bug Report 🐛
To reproduce:
- Create new project
- Attempt to run the preview
I have an old remotion project that I can run successfully, ie launches at localhost:3000. So I don't think it's my local setup.
Looking through the code I see the get-port.ts file changed yesterday. Is the 'available'/'unavailable' logic backwards?

My thought would be that "connect" should lead to an "available" status and "timeout" and "error" should lead to an "unavailable" status.
I downgraded all my remotion dependencies to 3.0.12 and it is working as expected.

I wanted to create a new remotion project, so I ran
npm init videoto set it up. The project was created successfully. But now when I runnpm startin the project I am met with the following error.Bug Report 🐛
To reproduce:
I have an old remotion project that I can run successfully, ie launches at localhost:3000. So I don't think it's my local setup.
Looking through the code I see the get-port.ts file changed yesterday. Is the 'available'/'unavailable' logic backwards?
My thought would be that "connect" should lead to an "available" status and "timeout" and "error" should lead to an "unavailable" status.
I downgraded all my remotion dependencies to 3.0.12 and it is working as expected.