-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
nx:nest:serve Daemon process terminated and closed the connection #23287
Comments
Having the same issue using pnpm on a mac Nx Version:
Pnpm Version:
Node Version:
package.json: {
"name": "@app",
"version": "0.0.0",
"license": "MIT",
"scripts": {},
"private": true,
"devDependencies": {
"@angular-devkit/build-angular": "~17.3.7",
"@angular-devkit/core": "~17.3.7",
"@angular-devkit/schematics": "~17.3.7",
"@angular-eslint/eslint-plugin": "~17.3.0",
"@angular-eslint/eslint-plugin-template": "~17.3.0",
"@angular-eslint/template-parser": "~17.3.0",
"@angular/cli": "~17.3.7",
"@angular/compiler-cli": "~17.3.8",
"@angular/language-service": "~17.3.8",
"@nestjs/schematics": "^10.0.1",
"@nestjs/testing": "^10.0.2",
"@nx/angular": "19.0.2",
"@nx/devkit": "19.0.2",
"@nx/eslint": "19.0.2",
"@nx/eslint-plugin": "19.0.2",
"@nx/jest": "19.0.2",
"@nx/js": "19.0.2",
"@nx/nest": "19.0.2",
"@nx/node": "19.0.2",
"@nx/playwright": "19.0.2",
"@nx/web": "19.0.2",
"@nx/webpack": "19.0.2",
"@nx/workspace": "19.0.2",
"@playwright/test": "^1.44.0",
"@schematics/angular": "~17.3.7",
"@swc-node/register": "~1.8.0",
"@swc/core": "~1.5.7",
"@swc/helpers": "~0.5.11",
"@types/d3": "^7.4.3",
"@types/jest": "^29.5.12",
"@types/node": "18.16.9",
"@typescript-eslint/eslint-plugin": "^7.8.0",
"@typescript-eslint/parser": "^7.8.0",
"autoprefixer": "^10.4.19",
"eslint": "~8.57.0",
"eslint-config-prettier": "^9.1.0",
"eslint-plugin-playwright": "^0.15.3",
"jest": "^29.7.0",
"jest-environment-jsdom": "^29.7.0",
"jest-environment-node": "^29.4.1",
"jest-preset-angular": "~14.0.4",
"nx": "19.0.2",
"postcss": "^8.4.38",
"prettier": "^2.8.8",
"tailwindcss": "^3.4.3",
"ts-jest": "^29.1.2",
"ts-node": "10.9.1",
"typescript": "~5.4.5",
"webpack-cli": "^5.1.4"
},
"dependencies": {
"@angular/animations": "~17.3.8",
"@angular/cdk": "^17.3.8",
"@angular/common": "~17.3.8",
"@angular/compiler": "~17.3.8",
"@angular/core": "~17.3.8",
"@angular/forms": "~17.3.8",
"@angular/material": "^17.3.8",
"@angular/platform-browser": "~17.3.8",
"@angular/platform-browser-dynamic": "~17.3.8",
"@angular/router": "~17.3.8",
"@nestjs/cli": "^10.3.2",
"@nestjs/common": "^10.0.2",
"@nestjs/core": "^10.0.2",
"@nestjs/platform-express": "^10.0.2",
"@nestjs/swagger": "^7.3.1",
"axios": "^1.6.0",
"class-transformer": "^0.5.1",
"class-validator": "^0.14.1",
"d3": "^7.9.0",
"reflect-metadata": "^0.1.13",
"rxjs": "~7.8.1",
"tslib": "^2.6.2",
"zone.js": "~0.14.5"
}
} |
Hey, can you create a repro I tested this and it's working correctly. You can also try resetting the daemon using |
https://github.com/junxiaotan/nx-latest-demo_bug
PS:Using |
My device is Mac M2 |
node: |
Running into the same issue - only when attempting to use pnpm. I can run my app: nx dev my-app, but can't lint, build, etc. |
I see exactly this issue in my setup, and I think I found the reason (at least in my case): adding I was able to reproduce this in a fresh container with fresh Basic installation:
First build:
Throwing the wrench and clearing :
Fixing things:
|
Found the answer to my problem. I was using version 9.x of pnpm. Go back to version 8.5.1 and everything is fine. It looks like 9.x isn't quite ready for primetime. Hope this helps others... |
This issue has been automatically marked as stale because no reproduction was provided within 7 days. |
Current Behavior
nx nest serve error
Expected Behavior
nx nest ok
GitHub Repo
No response
Steps to Reproduce
npx create-nx-workspace@latest --pm pnpm
(None)npx nx --version
// Local: v19.0.2npx nx add @nx/nest
npx nx g @nx/nest:app nest-demo
npx nx run nest-demo:serve:development
(error)Nx Report
Failure Logs
No response
Package Manager Version
No response
Operating System
Additional Information
No response
The text was updated successfully, but these errors were encountered: