Build fails with: ts-node: not found
My build is failing with the error that it cannot find ts-node
I have checked a previous thread and it hasn't helped, some extra info:
- ts-node is only used in building the app
- ts-node is declared as a dependency, not a dev dependency
- I have no railway.config file
30 Replies
Project ID:
aa4accc0-a714-470d-98af-7b29e22282d9aa4accc0-a714-470d-98af-7b29e22282d9
I've confirmed it works locally by running nixpacks and starting the container
It's just on the railway platform that it's crashing due to not finding ts-node
Any support would be appreciated
how have you verified that ts-node is being installed?
How can I verify that on a build on railway?
It's in my dependencies and it works locally
verbose mode for npm ci maybe
What would the fix be for this given it's already in my dependencies?
first we need to find out if it's being installed
Why wouldn't it be, though?
I don't get an NPM error
I'm sorry I don't have all these answers, you're going to have to dig into this and debug it
I'm going to assume that wouldn't be the case
Because it doesn't make sense given it's in my dependencies + I would see an NPM install error
something is misconfigured somehow, you are going to need to debug this
Any support line for paying customers?
unfortunately we can't offer in depth support for application level issues for users on the Hobby plan
Im on pro
you are not according to my admin dashboard
alternatively, can I get a refund?
Or if you allow deployments without using docker containers / nixpacks?
then that's a different account, the railway account connected to this discord account is not a part of any teams
Correct, this is on behalf of a client
yes, you can request that from within your billing page
railway is a containerized environment
have you tried adding verbose mode to the install command?
no I haven't
I'm sorry but I don't have the magical answer for you, all I can do is help you debug this
If I find out that it isn't being installed, what would I do?
Might be quicker just to do that and see if it works
I don't know yet, that's not how debugging works 😆
That's the issue
If it is the case that one package isn't being installed even though it's in my deps, then it's an unlikely fix
Thanks anyway, i'm going to move to a non-containerized platform
I wasn't saying it's going to fix anything, this is what debugging is about, gathering more information to help make further decisions.
but you do what's right for you in the end.
Right
Maybe ts-node is a devDep and you are using npm in production, so devDep are not installed?
It was a normal dependency
No idea why it didn't work
I recollect having the issue before with tsx but couldn't remember the fix