Comment by roy_goodwin_ on 15/10/2024 at 08:05 UTC

1 upvotes, 1 direct replies (showing 1)

View submission: Legacy project not running on one machine

Hmm that's a tricky one. Since it works on one machine but not the other with the same setup, I wonder if there could be some subtle difference in the environment or dependencies.

A few things I might try:

• Double check the node and npm versions are identical on both
• Delete the node_modules folder and package-lock.json, then do a fresh npm install
• Look closely at the tsconfig.json and see if there are any absolute paths that could be different between the machines
• Check if there are any globally installed packages on the working machine that the broken one is missing

Routing issues can definitely be a pain to debug. Hope you're able to track down the culprit! Let us know if you find a solution.

Replies

Comment by Floorman1 at 15/10/2024 at 09:46 UTC

1 upvotes, 0 direct replies

All good suggestions but i did all of this …

Checked node and npm multiple times, even uninstalled node and did a fresh installing using same version.

Deleted modules and package lock and reinstalled way more times than I care to admit!

Pasted tsconfig over the top from each instance to make sure it’s the same.

Double checked no global libraries too.

I think it’s still some sort of incompatibility of dependencies somewhere. I tried npm force resolution but didn’t work nor did npm dedupe.

In the end I changed to yarn and after a dedupe and install I managed to get things working. Can’t say I’m overly satisfied with the solution as it’s a distinct difference between environments, but I really had to move on.