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

ng serve / ng build does not work on Windows dev drive mounted as a volume #27119

Open
gingters opened this issue Feb 16, 2024 · 0 comments
Open
Labels
needs: investigation Requires some digging to determine if action is needed

Comments

@gingters
Copy link

Which @angular/* package(s) are the source of the bug?

compiler-cli, compiler

Is this a regression?

No

Description

I'm on Windows 11, using a dev drive ( D: ). The dev drive is mounted to C:\Dev as a mounted volume.

I have ng newed a project on this dev drive (i.e. D:\sg\projects\test-project ).

When I run ng serve and also ng build from D:\sg\projects\test-project all is fine.
When I run ng serve from C:\Dev\sg\projects\test-project (the usual location) it builds the projects, starts the dev server, but in the served index.html file the two script tags at the end of the body (polyfills-xxx.js and main-xxx.js) are missing. So the application won't start. When running ng build from the mounted volume the same problem can be seen. Both script tags are missing in the generated file.

There is also no output that would hint at a problem.

Expected behaviour: It should workl.
Alternatively, if it won't generate the script tags, it should at least print a warning or error to the console that something is wrong and the generated application won't run, and maybe not running the command from a mounted volume but directly onthe volume should be done instead. That said, i would be really unhappy with that alternative.

Please provide a link to a minimal reproduction of the bug

ng new on mounted dev drive

Please provide the exception or error you saw

There is no exception.

Please provide the environment you discovered this bug in (run ng version)

Angular CLI: 17.2.0
Node: 21.6.1 (Unsupported)
Package Manager: yarn 1.22.19
OS: win32 x64

Angular:
...

Package                      Version
------------------------------------------------------
@angular-devkit/architect    0.1702.0 (cli-only)
@angular-devkit/core         17.2.0 (cli-only)
@angular-devkit/schematics   17.2.0 (cli-only)
@schematics/angular          17.2.0 (cli-only)

Anything else?

No response

@JoostK JoostK transferred this issue from angular/angular Feb 16, 2024
@clydin clydin added the needs: investigation Requires some digging to determine if action is needed label Feb 20, 2024
@alan-agius4 alan-agius4 self-assigned this Mar 4, 2024
@alan-agius4 alan-agius4 removed their assignment Mar 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs: investigation Requires some digging to determine if action is needed
Projects
None yet
Development

No branches or pull requests

3 participants