nest: npm run start:prod is failed, unnecessary modules required (newly created project) v5
I’m submitting a…
[ ] Regression
[x] Bug report
[ ] Feature request
[ ] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead post your question on Stack Overflow.
Current behavior
After setting up a project with CLI as described in docs (without changing code), I have tried to run a command ‘npm run start:prod’ and get this error:
> test@0.0.1 prestart:prod /home/vmois/Projects/Portal/test
> rm -rf dist && tsc
node_modules/@nestjs/common/interfaces/microservices/microservice-configuration.interface.d.ts(3,32): error TS2307: Cannot find module 'mqtt'.
node_modules/@nestjs/common/interfaces/microservices/microservice-configuration.interface.d.ts(4,35): error TS2307: Cannot find module 'grpc'.
npm ERR! Linux 3.16.0-5-amd64
npm ERR! argv "/usr/bin/nodejs" "/usr/local/bin/npm" "run" "start:prod"
npm ERR! node v8.4.0
npm ERR! npm v4.0.5
npm ERR! code ELIFECYCLE
npm ERR! test@0.0.1 prestart:prod: `rm -rf dist && tsc`
npm ERR! Exit status 2
npm ERR!
npm ERR! Failed at the test@0.0.1 prestart:prod script 'rm -rf dist && tsc'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the test package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! rm -rf dist && tsc
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs test
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls test
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR! /home/vmois/Projects/Portal/test/npm-debug.log
Of course the easiest solution is to install these packages, but what if I don’t use them and don’t want to install. Thanks.
Expected behavior
Compile and server in dist/main.js
Minimal reproduction of the problem with instructions
Try to setup up project with CLI, and then run ‘npm run start:prod’
Environment
[Nest Information]
microservices version : 5.0.0-beta.3
websockets version : 5.0.0-beta.3
testing version : 5.0.0-beta.3
common version : 5.0.0-beta.3
core version : 5.0.0-beta.3
For Tooling issues:
- Node version: 8.4.0
- Platform: Linux
Others:
Package manager: yarn
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Reactions: 4
- Comments: 18 (4 by maintainers)
Commits related to this issue
- bugfix(@nestjs/microservices) extract external typings #594 — committed to nestjs/nest by kamilmysliwiec 6 years ago
If you happen to build your project in a Docker container and then run it in a different one for use in production, then don’t use
npm run start:prodbecause it counter-intuitively deletes youdistdirectory.It must have been an idea for an April fools’ day prank. 🤔
Just call
node dist/main.jsdirectly.Just for someone else experimenting this issue, my workaround was to modify the path of main.js :
It works thanks