-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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 application is not opening nx run app-api:serve:development #21838
Comments
Hey, can you provide the output of |
I am also seeing this behaviour, and was able to reproduce it like this: Create a new workspace
Modify project.json to add a dependency: "targets": {
"some-task": {
"command": "npx -y cowsay Moo"
},
... "build": {
"dependsOn": ["some-task"],
... Run a build
The command will hang, never complete and not respond to Ctrl-C. It needs to be manually killed in the task manager.
Removing the |
Looks like setting the environment variable |
I have the same issue after upgrading from
This didn't help in my case.
My Node : 21.6.2
OS : darwin-arm64
npm : 10.4.0
nx : 18.0.4
@nx/js : 18.0.4
@nx/linter : 18.0.4
@nx/eslint : 18.0.4
@nx/workspace : 18.0.4
@nx/cypress : 18.0.4
@nx/devkit : 18.0.4
@nx/eslint-plugin : 18.0.4
@nx/react : 18.0.4
@nrwl/tao : 18.0.4
@nx/vite : 18.0.4
@nx/web : 18.0.4
typescript : 5.3.3 My {
"root": ".",
"name": "frontend",
"targets": {
"start": {
"executor": "nx:run-script",
"options": { "script": "start" },
"configurations": {}
},
"build": {
"executor": "@nx/vite:build",
"dependsOn": ["^build"],
"inputs": ["production", "^production"],
"outputs": ["{options.outputPath}"],
"defaultConfiguration": "production",
"options": { "outputPath": "dist/frontend" },
"configurations": {
"development": { "mode": "development" },
"production": { "mode": "production" }
}
},
"test": {
"executor": "@nx/vite:test",
"inputs": ["default", "^production"],
"outputs": ["{projectRoot}/coverage/frontend"],
"options": {
"passWithNoTests": true,
"reportsDirectory": "coverage/frontend"
},
"configurations": {}
},
"lint": {
"executor": "@nx/eslint:lint",
"inputs": [
"default",
"{workspaceRoot}/.eslintrc.json",
"{workspaceRoot}/.eslintignore"
],
"cache": true,
"options": { "lintFilePatterns": ["./src/**/*.{ts,tsx,js,jsx}"] },
"configurations": {}
},
"serve": {
"executor": "@nx/vite:dev-server",
"defaultConfiguration": "development",
"options": { "buildTarget": "frontend:build" },
"configurations": {
"development": {
"buildTarget": "frontend:build:development",
"hmr": true
},
"production": {
"buildTarget": "frontend:build:production",
"hmr": false
}
}
},
"preview": {
"executor": "@nx/vite:preview-server",
"defaultConfiguration": "development",
"options": { "buildTarget": "frontend:build" },
"configurations": {
"development": { "buildTarget": "frontend:build:development" },
"production": { "buildTarget": "frontend:build:production" }
}
}
},
"$schema": "node_modules/nx/schemas/project-schema.json",
"sourceRoot": "./src",
"projectType": "application",
"tags": [],
"implicitDependencies": []
} My project is a pretty simple Vite, React and TypeScript Project - so it is probably also easy to reproduce. |
Having the same problem on Windows 10 going from Nx v17.2.8 to v18.0.4 with
So it seems like it can only run one thing before it just hangs where Ctrl+C doesn't even work. In my case, setting |
This issue has been automatically marked as stale because it hasn't had any recent activity. It will be closed in 14 days if no further activity occurs. |
Replying so it stays active... many people seem to have this issue. |
This issue has been automatically marked as stale because it hasn't had any recent activity. It will be closed in 14 days if no further activity occurs. |
Not stale |
This issue has been automatically marked as stale because it hasn't had any recent activity. It will be closed in 14 days if no further activity occurs. |
This issue still persist. And this fix worked for me. Anybody knows what this |
This issue has been automatically marked as stale because it hasn't had any recent activity. It will be closed in 14 days if no further activity occurs. |
Just ran into it, so not stale. |
Any solution for this yet? I migrated my Nx repo from 14.1.9 to 15.1.1 and I'm start to face this as well. My angular app is stuck is at the "sealing" phase. My NestJs app on the other hand is serving fine but stuck at the building phase. |
This issue has been automatically marked as stale because it hasn't had any activity for 6 months. |
Current Behavior
Whenever I tried to serve the NX application I did not get any error or response.
this is what is shown in the terminal
Expected Behavior
My expectation is application will run or throw some error
GitHub Repo
No response
Steps to Reproduce
just run pnpm nx serve app-api
Nx Report
The text was updated successfully, but these errors were encountered: