-
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
assets folder not working when using ng serve with --serve-path #26509
Labels
area: @angular-devkit/build-angular
devkit/build-angular:dev-server
freq1: low
Only reported by a handful of users who observe it rarely
severity3: broken
type: bug/fix
Comments
alan-agius4
added
type: bug/fix
freq1: low
Only reported by a handful of users who observe it rarely
area: @angular-devkit/build-angular
devkit/build-angular:dev-server
severity3: broken
labels
Nov 28, 2023
alan-agius4
added a commit
to alan-agius4/angular-cli
that referenced
this issue
Nov 28, 2023
…erve-path` When the `serve-path` option is used assets are now correctly servered from this location. Closes angular#26509
alan-agius4
added a commit
to alan-agius4/angular-cli
that referenced
this issue
Nov 28, 2023
…erve-path` When the `serve-path` option is used assets are now correctly servered from this location. Closes angular#26509
alan-agius4
added a commit
to alan-agius4/angular-cli
that referenced
this issue
Nov 28, 2023
…erve-path` When the `serve-path` option is used assets are now correctly servered from this location. Closes angular#26509
alan-agius4
added a commit
to alan-agius4/angular-cli
that referenced
this issue
Nov 28, 2023
…erve-path` When the `serve-path` option is used assets are now correctly servered from this location. Closes angular#26509
alan-agius4
added a commit
to alan-agius4/angular-cli
that referenced
this issue
Nov 28, 2023
…erve-path` When the `serve-path` option is used assets are now correctly servered from this location. Closes angular#26509
alan-agius4
added a commit
to alan-agius4/angular-cli
that referenced
this issue
Nov 28, 2023
…erve-path` When the `serve-path` option is used assets are now correctly servered from this location. Closes angular#26509
alan-agius4
added a commit
to alan-agius4/angular-cli
that referenced
this issue
Nov 28, 2023
…erve-path` When the `serve-path` option is used assets are now correctly servered from this location. Closes angular#26509
alan-agius4
added a commit
to alan-agius4/angular-cli
that referenced
this issue
Nov 28, 2023
…erve-path` When the `serve-path` option is used assets are now correctly servered from this location. Closes angular#26509
alan-agius4
added a commit
to alan-agius4/angular-cli
that referenced
this issue
Nov 28, 2023
…erve-path` When the `serve-path` option is used assets are now correctly servered from this location. Closes angular#26509
alan-agius4
added a commit
to alan-agius4/angular-cli
that referenced
this issue
Nov 28, 2023
…erve-path` When the `serve-path` option is used assets are now correctly servered from this location. Closes angular#26509
alan-agius4
added a commit
to alan-agius4/angular-cli
that referenced
this issue
Nov 28, 2023
…erve-path` When the `serve-path` option is used assets are now correctly servered from this location. Closes angular#26509
alan-agius4
added a commit
that referenced
this issue
Nov 28, 2023
…erve-path` When the `serve-path` option is used assets are now correctly servered from this location. Closes #26509
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. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
area: @angular-devkit/build-angular
devkit/build-angular:dev-server
freq1: low
Only reported by a handful of users who observe it rarely
severity3: broken
type: bug/fix
Command
serve
Is this a regression?
The previous version in which this bug was not present was
Angular 16 with webpack
Description
After update to Angular 17 and esbuild + vite assets no longer working when using ng serve with --serve-path option.
Minimal Reproduction
Just but some html file in the
assets
folder and runng serve --serve-path /test
. Than try to access "http://localhost:4200/test/somefile.html" and it will result in an 404 error. No output is logged.Exception or Error
The server is configured with a public base URL of /test- did you mean to visit http://localhost:4200/test/@fs/C:%5CUsers%5C****************%5Csrc%5Cassets%5Csomefile.html instead?
Your Environment
Anything else relevant?
No response
The text was updated successfully, but these errors were encountered: