the development server in all my Gitpod workspaces are throwing errors

[johnston9]

Bug description

All my workspaces have errors withe opening the development server
that is running npm start for a React app etc

I react project I put npm start in the terminal and get this in all my React app
I my DRF I get a different set of errors.

in the React app I get this:
Starting the development server...

node:events:368
throw er; // Unhandled 'error' event
^

Error: spawn gp preview --external ENOENT
at Process.ChildProcess._handle.onexit (node:internal/child_process:282:19)
at onErrorNT (node:internal/child_process:477:16)
at processTicksAndRejections (node:internal/process/task_queues:83:21)
Emitted 'error' event on ChildProcess instance at:
at Process.ChildProcess._handle.onexit (node:internal/child_process:288:12)
at onErrorNT (node:internal/child_process:477:16)
at processTicksAndRejections (node:internal/process/task_queues:83:21) {
errno: -2,
code: 'ENOENT',
syscall: 'spawn gp preview --external',
path: 'gp preview --external',
spawnargs: [ 'http://localhost:3000' ]
}
npm notice
npm notice New major version of npm available! 8.0.0 -> 9.7.1
npm notice Changelog: https://github.com/npm/cli/releases/tag/v9.7.1
npm notice Run npm install -g npm@9.7.1 to update!

in the DRF it get this

gitpod /workspace/shot-caller-production-api (main) $ npm start
npm ERR! code ENOENT
npm ERR! syscall open
npm ERR! path /workspace/shot-caller-production-api/package.json
npm ERR! errno -2
npm ERR! enoent ENOENT: no such file or directory, open '/workspace/shot-caller-production-api/package.json' npm ERR! enoent This is related to npm not being able to find a file. npm ERR! enoent

npm ERR! A complete log of this run can be found in:
npm ERR! /home/gitpod/.npm/_logs/2023-06-13T00_29_10_111Z-debug.log

Steps to reproduce

run npm start

these are one I need right now

Workspace affected

https://gitpod.io/start/#amaranth-firefly-no299baq

Expected behavior

should open the app in the browser
instead it shows lots of errors

Example repository

Anything else?

All my workspaces are like this

[axonasif]

Hi @johnston9, it looks like your code is using gp preview command in the wrong way.
I might be able to help if your repo is public.

[AndypSheridan]

Hi @johnston9, any luck resolving this issue yet? I'm having the same problem.

[nazarja]

This issue appears to be affecting workspaces overnight.

Nothing appears to fix the issue, I tried changing node version, reinstalling the node_modules etc...

Does anyone know what the actual cause of the error is and if there's a fix that can be implemented by a user?

[johnston9]

I have no idea why it suddenly started or even what the actual issue is but it is on Gitpod's side. I sent them an email about it.

…

On Tue, Jun 13, 2023 at 9:28 AM Sean Murphy ***@***.***> wrote: This issue appears to be affecting workspaces overnight. Nothing appears to fix the issue, I tried changing node version, reinstalling the node_modules etc... Does anyone know what the actual cause of the error is and if there's a fix that can be implemented by a user? — Reply to this email directly, view it on GitHub <#17913 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AQNQQIB4VUJVJ23DQHXWZE3XLAQC7ANCNFSM6AAAAAAZEFKUCQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[AndypSheridan]

I have no idea why it suddenly started or even what the actual issue is but it is on Gitpod's side. I sent them an email about it.

Can you post their response please? I'm working on a project and nearly done; the tutor support team suggested migrating to CodeAnywhere but as I'm so close to the end, I'm reluctant to go that route.

[Karasp1980]

also wondering

[johnston9]

I logged it with there support. I think if enough people do it they will have to fix it.

…

On Tue, Jun 13, 2023 at 1:31 PM karasp80 ***@***.***> wrote: also wondering — Reply to this email directly, view it on GitHub <#17913 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AQNQQIEROIPLJW446J4B6CLXLBMRDANCNFSM6AAAAAAZEFKUCQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[SamOBrienOlinger]

Exact same problem for me.

This lost day will have a major impact on delivering a project by an imminent deadline.

[johnston9]

Get on to them please, I sent in a request for support but have heard nothing. Must be happening to tons of people.

…

On Tue, Jun 13, 2023 at 4:17 PM SamOBrienOlinger ***@***.***> wrote: Exact same problem for me. This lost day will have a major impact on delivering a project by an imminent deadline. [image: image] <https://user-images.githubusercontent.com/97180898/245523594-ec4b55a1-be81-45d1-870e-0c725431e87f.png> — Reply to this email directly, view it on GitHub <#17913 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AQNQQICB2M7KUF6KVJASXA3XLCABLANCNFSM6AAAAAAZEFKUCQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[axonasif]

Hey folks, sorry for the inconvenience. It seems to be happening because of a recent addition of the $BROWSER environment variable to Gitpod task terminals and npm does not seem to be compatible with it as it expects a file path.

To workaround this issue, you can create a new terminal manually and then execute npm start or any other command that you use. We'll get this fixed meanwhile.

Another workaround is to run export BROWSER=/ide/bin/helpers/browser.sh before running npm start.

Thank you for your patience.