-
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
fix(nextjs): fix custom server templates #17266
fix(nextjs): fix custom server templates #17266
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
I found another bug related to custom server. // The output is in `dist/apps/<project-name>/server/main.js`
// but @nx/js:node tries to find `dist/apps/<project-name>/main.js`
"build-custom-server": {
"executor": "@nx/js:tsc",
"defaultConfiguration": "production",
"options": {
"outputPath": "dist/apps/client",
"outputFileName": "server/main.js", // 👈 outputFileName is missing
"main": "apps/client/server/main.ts",
"tsConfig": "apps/client/tsconfig.server.json",
"clean": false,
"assets": []
}, |
5a9db75
to
50878c9
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @puku0x
This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request. |
Current Behavior
server/main.ts
."tsBuildInfoFile": "../..//tmp/buildcache/apps/client/server",
Expected Behavior
server/main.ts
."tsBuildInfoFile": "../../tmp/buildcache/apps/client/server",
Related Issue(s)
Fixes #