guyulmaz
commented
6 years ago I found the reason, at https://github.com/nestjs/typescript-starter there is no .nestcli.json file existing, this is the problem. I think https://github.com/nestjs/typescript-starter should be updated.
lock[bot]
Hello, I git cloned the ts-starter project. I updated the package.json to latest packages like:
{ "name": "nest-typescript-starter", "version": "1.0.0", "description": "Nest TypeScript starter repository", "license": "MIT", "scripts": { "format": "prettier --write \"src/*/.ts\"", "start": "ts-node -r tsconfig-paths/register src/main.ts", "start:dev": "nodemon", "start:debug": "nodemon --config nodemon-debug.json", "prestart:prod": "rimraf dist && tsc", "start:prod": "node dist/main.js", "start:hmr": "node dist/server", "lint": "tslint -p tsconfig.json -c tslint.json", "test": "jest", "test:watch": "jest --watch", "test:cov": "jest --coverage", "test:e2e": "jest --config ./test/jest-e2e.json", "webpack": "webpack --config webpack.config.js" }, "dependencies": { "@nestjs/common": "^5.1.0", "@nestjs/core": "^5.1.0", "@nestjs/microservices": "^5.1.0", "@nestjs/testing": "^5.1.0", "@nestjs/websockets": "^5.1.0", "reflect-metadata": "^0.1.12", "rxjs": "^6.2.2", "typescript": "^2.8.0" }, "devDependencies": { "@types/express": "^4.16.0", "@types/jest": "^23.3.1", "@types/node": "^10.5.5", "@types/supertest": "^2.0.5", "jest": "^23.4.2", "nodemon": "^1.18.3", "prettier": "^1.14.0", "rimraf": "^2.6.2", "supertest": "^3.1.0", "ts-jest": "^23.0.1", "ts-loader": "^4.4.2", "ts-node": "^7.0.0", "tsconfig-paths": "^3.5.0", "tslint": "^5.11.0", "webpack": "^4.16.3", "webpack-cli": "^3.1.0", "webpack-node-externals": "^1.7.2", "ajv": "^6.5.2" }, "jest": { "moduleFileExtensions": [ "js", "json", "ts" ], "rootDir": "src", "testRegex": ".spec.ts$", "transform": { "^.+\.(t|j)s$": "ts-jest" }, "coverageDirectory": "../coverage" } }
so now when I run command
nest g co about
at project dir, I 'm getting error
[Nest] 19956 - 8/2/2018, 2:06:32 PM [NestFactory] Starting Nest application... [Nest] 19956 - 8/2/2018, 2:06:32 PM [InstanceLoader] AppModule dependencies initialized +14ms [Nest] 19956 - 8/2/2018, 2:06:32 PM [RoutesResolver] AppController {/}: +24ms [Nest] 19956 - 8/2/2018, 2:06:32 PM [RouterExplorer] Mapped {/, GET} route +60ms [Nest] 19956 - 8/2/2018, 2:06:32 PM [NestApplication] Nest application successfully started +16ms Terminate batch job (Y/N)? y PS C:\ozel\nestjs\apps\nestjs-ts-starter> nest g co about (node:11240) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, open 'C:\ozel\nestjs\apps\nestjs-ts-starter.nestcli.json' (node:11240) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1) (node:11240) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code. PS C:\ozel\nestjs\apps\nestjs-ts-starter> nest g co about (node:18452) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, open 'C:\ozel\nestjs\apps\nestjs-ts-starter.nestcli.json' (node:18452) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1) (node:18452) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
what can be the problem?