You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I say pnpm because I haven't tested npm or yarn, but my hypothesis should hold true for either of those since the way the binary is executed is the same via all three package managers.
hypothesis: The problem is that when cli is installed and run through node, it is run through this file. Then, on ctrl + c the railway.js file quits, killing the underlying cli process.
Experimentally proven to be a problem with pnpm installed version of cli on 2023-08-20, installing manually using a download + editing PATH does not yield the same error
CLI Version: 3.4.0
Installed via: pnpm 8.6.12
Potential fix: detect railway shell startup in the railway.js file
The text was updated successfully, but these errors were encountered:
I say pnpm because I haven't tested npm or yarn, but my hypothesis should hold true for either of those since the way the binary is executed is the same via all three package managers.
hypothesis: The problem is that when cli is installed and run through node, it is run through this file. Then, on ctrl + c the
railway.js
file quits, killing the underlying cli process.Experimentally proven to be a problem with pnpm installed version of cli on 2023-08-20, installing manually using a download + editing PATH does not yield the same error
CLI Version: 3.4.0
Installed via: pnpm 8.6.12
Potential fix: detect railway shell startup in the railway.js file
The text was updated successfully, but these errors were encountered: