fix(@angular/build): update vite to version 6.0.11 #29471
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
clydin
force-pushed
the
vite-allowed-hosts-19.1.x
branch
from
42180fa to
c130c77
Compare
clydin
added
the
action: review
alan-agius4
reviewed
Jan 24, 2025
alan-agius4
reviewed
Jan 24, 2025
packages/angular/build/src/builders/dev-server/tests/execute-fetch.ts
Outdated
Show resolved
Hide resolved
alan-agius4
reviewed
Jan 24, 2025
packages/angular/build/src/builders/dev-server/tests/execute-fetch.ts
Outdated
Show resolved
Hide resolved
alan-agius4
approved these changes
Jan 24, 2025
Version update from 6.0.7 to address advisory GHSA-vg6x-rcgg-rjx6 Vite version 6.0.9+, which is now used by the Angular CLI with the `application`/`browser-esbuild` builders, contains a potentially breaking change for some development setups. Examples of such setups include those that use reverse proxies or custom host names during development. The change within a patch release was made by Vite to address a security vulnerability. For projects that directly access the development server via `localhost`, no changes should be needed. However, some development setups may now need to adjust the `allowedHosts` development server option. This option can include an array of host names that are allowed to communicate with the development server. The option sets the corresponding Vite option within the Angular CLI. For more information on the option and its specific behavior, please see the Vite documentation located here: https://vite.dev/config/server-options.html#server-allowedhosts The following is an example of the configuration option allowing `example.com`: ``` "serve": { "builder": "@angular-devkit/build-angular:dev-server", "options": { "allowedHosts": ["example.com"] }, ```
clydin
force-pushed
the
vite-allowed-hosts-19.1.x
branch
from
c130c77 to
f500423
Compare
clydin
added
action: merge
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Version update from 6.0.7 to address advisory GHSA-vg6x-rcgg-rjx6
Vite version 6.0.9+, which is now used by the Angular CLI with the
application/browser-esbuildbuilders, contains a potentially breaking change for some development setups. Examples of such setups include those that use reverse proxies or custom host names during development. The change within a patch release was made by Vite to address a security vulnerability. For projects that directly access the development server vialocalhost, no changes should be needed. However, some development setups may now need to adjust theallowedHostsdevelopment server option. This option can include an array of host names that are allowed to communicate with the development server. The option sets the corresponding Vite option within the Angular CLI. For more information on the option and its specific behavior, please see the Vite documentation located here:https://vite.dev/config/server-options.html#server-allowedhosts
The following is an example of the configuration option allowing
example.com: