Skip to content
New issue

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

Failed to execute command: node @nestjs/schematics:service #14090

Closed
3 of 15 tasks
Martelinok opened this issue Oct 25, 2024 · 6 comments
Closed
3 of 15 tasks

Failed to execute command: node @nestjs/schematics:service #14090

Martelinok opened this issue Oct 25, 2024 · 6 comments
Labels
needs triage This issue has not been looked into

Comments

@Martelinok
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Current behavior

Failed to execute command: node @nestjs/schematics:service --name=services/products --no-dry-run --no-skip-import --language="ts" --source-root="src" --spec --flat --spec-file-suffix="spec"

Minimum reproduction code

https://github.com/Martelinok/2716-Coffee-Backend.git

Steps to reproduce

im try to create my services files

Expected behavior

Create the files

Package

  • I don't know. Or some 3rd-party package
  • @nestjs/common
  • @nestjs/core
  • @nestjs/microservices
  • @nestjs/platform-express
  • @nestjs/platform-fastify
  • @nestjs/platform-socket.io
  • @nestjs/platform-ws
  • @nestjs/testing
  • @nestjs/websockets
  • Other (see below)

Other package

No response

NestJS version

10.4.5

Packages versions

{ "name": "2716-coffee", "version": "0.0.1", "description": "", "author": "", "private": true, "license": "UNLICENSED", "scripts": { "build": "nest build", "format": "prettier --write \"src/**/*.ts\" \"test/**/*.ts\"", "start": "nest start", "start:dev": "nest start --watch", "start:debug": "nest start --debug --watch", "start:prod": "node dist/main", "lint": "eslint \"{src,apps,libs,test}/**/*.ts\" --fix", "test": "jest", "test:watch": "jest --watch", "test:cov": "jest --coverage", "test:debug": "node --inspect-brk -r tsconfig-paths/register -r ts-node/register node_modules/.bin/jest --runInBand", "test:e2e": "jest --config ./test/jest-e2e.json" }, "dependencies": { "@nestjs/common": "^10.0.0", "@nestjs/core": "^10.0.0", "@nestjs/platform-express": "^10.0.0", "reflect-metadata": "^0.2.0", "rxjs": "^7.8.1" }, "devDependencies": { "@nestjs/cli": "^10.0.0", "@nestjs/schematics": "^10.2.2", "@nestjs/testing": "^10.0.0", "@types/express": "^5.0.0", "@types/jest": "^29.5.2", "@types/node": "^20.3.1", "@types/supertest": "^6.0.0", "@typescript-eslint/eslint-plugin": "^8.0.0", "@typescript-eslint/parser": "^8.0.0", "eslint": "^9.0.0", "eslint-config-prettier": "^9.0.0", "eslint-plugin-prettier": "^5.0.0", "jest": "^29.5.0", "prettier": "^3.0.0", "source-map-support": "^0.5.21", "supertest": "^7.0.0", "ts-jest": "^29.1.0", "ts-loader": "^9.4.3", "ts-node": "^10.9.1", "tsconfig-paths": "^4.2.0", "typescript": "^5.1.3" }, "jest": { "moduleFileExtensions": [ "js", "json", "ts" ], "rootDir": "src", "testRegex": ".*\\.spec\\.ts$", "transform": { "^.+\\.(t|j)s$": "ts-jest" }, "collectCoverageFrom": [ "**/*.(t|j)s" ], "coverageDirectory": "../coverage", "testEnvironment": "node" } }

Node.js version

23.0.0

In which operating systems have you tested?

  • macOS
  • Windows
  • Linux

Other

I'm learning node + nest and i try to create all of the files, the controllers works

@Martelinok Martelinok added the needs triage This issue has not been looked into label Oct 25, 2024
@micalevisk
Copy link
Member

please share the command that reproduces the issue

@Martelinok
Copy link
Author

nest generate s services/products

@micalevisk
Copy link
Member

micalevisk commented Oct 25, 2024

@Martelinok try using the local @nestjs/cli instead, so: npx nest generate s services/products

Looks like you got a version mismatch. Everything went fine here

image

@Martelinok
Copy link
Author

Screenshot 2024-10-25 at 5 45 55 PM

@micalevisk
Copy link
Member

micalevisk commented Oct 25, 2024

what if you use nodejs 22? odd versions are not supposed to be used in a real project

I didn't manage to reproduce that error here on my linux

@micalevisk
Copy link
Member

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs triage This issue has not been looked into
Projects
None yet
Development

No branches or pull requests

2 participants