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
Dev dependencies are as the name implies for development, I am not sure why you would need @loopback/build during production but you have to add it to dependencies then. I asked a related questions on stackoverflow 4 years ago but I would generally just recommend to use docker to deploy your app to production which looks like is what you are doing.
If you can provide your Dockerfile and more details on why you need @loopback/build in production, I can give you some suggestions.
Describe the bug
Hi! In all examples
@loopback/build
is installed as dev dependency --->npm i @loopback/build --save-dev
This causes issues with NODE_ENV=production (specially when trying to deploy the app) as dev dependencies are not resolved...
I fixed this by using
npm i --include=dev
in my Dockerfile. But I don't think that's entirely right...What's the recommendation here?
Thanks in advance!
Logs
No response
Additional information
No response
Reproduction
export NODE_ENV=production; npm i
The text was updated successfully, but these errors were encountered: