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
typeorm-ts-node-esm doesn't work on linux environments, due to env shebang with multiple arguments
Expected Behavior
Running npx typeorm-ts-node-esm should work on linux.
Actual Behavior
npx typeorm-ts-node-esm returns:
'node --loader ts-node/esm --no-warnings' no such file exists
This is a result of the shebang being parsed incorrectly, a known issue with env on almost all linux distros.
Running into this issue trying to run migrations from inside a docker container (on a CI pipeline)
Steps to Reproduce
On linux, install typeorm
Run npx typeorm init.
Run npx typeorm-ts-node-esm
My Environment
Dependency
Version
Operating System
Linux Alpine
Node.js version
16.14.2
Typescript version
4.4.4
TypeORM version
0.3.4
Are you willing to resolve this issue by submitting a Pull Request?
✅ Yes, I have the time, and I know how to start.
✖️ Yes, I have the time, but I don't know how to start. I would need guidance.
✖️ No, I don’t have the time, but I can support (using donations) development.
✖️ No, I don’t have the time and I’m okay to wait for the community / maintainers to resolve this issue.
Fixing this has the potential issue of breaking compatibility in other places. It's possible that the best way to approach this is to but an alternate path in to work around the shebang, and still correctly set the environment variables.
The text was updated successfully, but these errors were encountered:
Issue Description
typeorm-ts-node-esm doesn't work on linux environments, due to env shebang with multiple arguments
Expected Behavior
Running npx typeorm-ts-node-esm should work on linux.
Actual Behavior
npx typeorm-ts-node-esm returns:
This is a result of the shebang being parsed incorrectly, a known issue with env on almost all linux distros.
Running into this issue trying to run migrations from inside a docker container (on a CI pipeline)
Steps to Reproduce
My Environment
Are you willing to resolve this issue by submitting a Pull Request?
Fixing this has the potential issue of breaking compatibility in other places. It's possible that the best way to approach this is to but an alternate path in to work around the shebang, and still correctly set the environment variables.
The text was updated successfully, but these errors were encountered: