-
Notifications
You must be signed in to change notification settings - Fork 12k
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
ServerBuilder: bundleDependencies "none" no longer works on Windows #14333
Comments
@enten, I have checked this and this should have been already solved in the recent RC versions. Kindly update to the latest RC versions and try again, If the problem persists kindly open a new issue, with the exact steps to reproduce it. Thanks. |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
🐞 Bug report
Command (mark with an
x
)Is this a regression?
Yes, the previous version in which this bug was not present was:
@angular/cli v8.0.0-beta.4
or@angular-devkit/build-angular v0.14.0-beta.4
(before commit 309b483).Description
Commit 309b483 add changes on server builder model (
packages/angular_devkit/build_angular/src/angular-cli-files/models/webpack-configs/server.ts
) which breaks option"bundleDependencies": "none"
on Windows.After these changes, main server entry path will be consider as external/node module (because
require.resolve
succeeded to resolve main server entry path).Consequently:
Before these changes, Windows paths were consider as "system thing" because some path like
C:\code\src\main.server.ts
doesn't match^\.{0,2}\/
, can be resolve withrequire.resolve
but doesn't containnode_modules
.Temporarily fix: we can use
"bundleDependencies": "all"
to ensure main server entry will be transpile but all server dependencies will be transpile (and bundle) too.🔬 Minimal Reproduction
🔥 Exception or Error
🌍 Your Environment
Anything else relevant?
May there is another issue on Windows to resolve path to builder.
During writing this issue, I hit issue below but I don't have time to investigate more. May that it's related to another issue.
The text was updated successfully, but these errors were encountered: