Question

App Platform keeps using cached node_modules despite changes

I have been deploying a node.js server application via app platform without issue. In the last push to github, I have introduced typescript which has made significant changes to my package.json and package-lock.json including adding typescript 4.1.3.

my build command is now

"build": "tsc",

But my build is failing because with the following because it can’t find the tsc command. relevant bit of the deployment logs below…

tsystems-server | 16:28:37 Installing node_modules using npm
tsystems-server | 16:28:44 added 119 packages in 5.537s
tsystems-server | 16:28:45 Running custom build command: npm run build
tsystems-server | 16:28:45 
tsystems-server | 16:28:45 > tsystems-server@1.0.0 build /workspace
tsystems-server | 16:28:45 > tsc
tsystems-server | 16:28:45 
tsystems-server | 16:28:45 sh: 1: tsc: not found

Not sure what is going wrong, the npm run build command works locally. I have tried manually referencing “./node_modules/…etc…/tsc” in the build command but that didn’t work. Also tried npx tsc but that just got really wierd.

Any clues?

Michael

Subscribe
Share

Ok this is getting ridiculous now, this is now my build command in package.json…

"build": "rm -rf node_modules & npm install --force && npm list -depth 0 && tsc"

but the build process still won’t make the new packages (including typescript) available in the npm environment when the tsc command is run.

Am I missing something? Seems to be broken to me.

This is the relevant bit of the build logs…

tsystems-server | 09:00:30 > tsystems-server@1.0.0 build /workspace
tsystems-server | 09:00:30 > rm -rf node_modules & npm install --force && npm list -depth 0 && tsc
tsystems-server | 09:00:30 
tsystems-server | 09:00:31 npm WARN using --force I sure hope you know what you are doing.
tsystems-server | 09:00:37 added 119 packages from 75 contributors and audited 379 packages in 5.67s
tsystems-server | 09:00:37 found 0 vulnerabilities
tsystems-server | 09:00:37 
tsystems-server | 09:00:38 tsystems-server@1.0.0 /workspace
tsystems-server | 09:00:38 +-- cookie-session@1.4.0
tsystems-server | 09:00:38 +-- cors@2.8.5
tsystems-server | 09:00:38 +-- dotenv@8.2.0
tsystems-server | 09:00:38 +-- express@4.17.1
tsystems-server | 09:00:38 +-- googleapis@66.0.0
tsystems-server | 09:00:38 +-- passport@0.4.1
tsystems-server | 09:00:38 +-- passport-google-oauth20@2.0.0
tsystems-server | 09:00:38 `-- pg@8.5.1
tsystems-server | 09:00:38 
tsystems-server | 09:00:38 sh: 1: tsc: not found

Submit an answer
You can type!ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Accepted Answer

This is a known issue with App Platform node builds NOT installing dev dependencies (which is really stoopid).

to fix, alter your build command to this.

npm install --only=dev && npm run build && npm prune --production

The issue is discussed here…

https://www.digitalocean.com/community/questions/how-do-you-use-node-js-devdependencies-in-the-app-platform-builds

Hello,

I understand that you are experiencing an issue with compiling TypeScript while building the app. You need to call “tsc” from an npm script by including command such as ( npm install typescript -g ) because I can see the build is failing at below line with “tsc not found” error:

tsc -p ./server/tsconfig.json --outDir ./dist && next build

Can you try this and keep us posted, if this helped!

Cheers, Sri Charan