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

1 upvotes, 0 direct replies (showing 0)

View submission: Legacy project not running on one machine

View parent comment

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.

Replies

There's nothing here!