We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
In lesson 1, I get this error
yarn start yarn run v1.16.0 $ node dist/index.js internal/modules/cjs/loader.js:626 throw err; ^ Error: Cannot find module '/Users/vincentleleux/introg/dist/index.js' at Function.Module._resolveFilename (internal/modules/cjs/loader.js:623:15) at Function.Module._load (internal/modules/cjs/loader.js:527:27) at Function.Module.runMain (internal/modules/cjs/loader.js:837:10) at internal/main/run_main_module.js:17:11 { code: 'MODULE_NOT_FOUND', requireStack: [] } error Command failed with exit code 1.
There is indeed no dist folder and the package.json got this line : "start": "node dist/index.js"
"start": "node dist/index.js"
so why is it not throwing an error for you ?
The text was updated successfully, but these errors were encountered:
Hello! What I did was:
node src/index.js
node dist/index.js
To connect to db, make sure you follow these instructions: https://docs.mongodb.com/manual/tutorial/install-mongodb-on-os-x/#install-mongodb-community-edition-on-macos if you're on Mac.
I don't know if is the correct way of doing it but it worked for me. Regards!
Sorry, something went wrong.
The dist folder is generated by running the yarn build command.
yarn build
Hey @Vince2301 , You just need to run yarn build and then yarn start :)
yarn start
Edit nest-cli.json
{ "collection": "@nestjs/schematics", "sourceRoot": "src", "entryFile": "your/main/js/path" }
No branches or pull requests
In lesson 1, I get this error
There is indeed no dist folder and the package.json got this line :
"start": "node dist/index.js"
so why is it not throwing an error for you ?
The text was updated successfully, but these errors were encountered: