fix(@angular-devkit/build-angular): update vite to version 5.4.14#29602
Merged
clydin merged 2 commits intoangular:17.3.xfrom Feb 12, 2025
Merged
fix(@angular-devkit/build-angular): update vite to version 5.4.14#29602clydin merged 2 commits intoangular:17.3.xfrom
clydin merged 2 commits intoangular:17.3.xfrom
Conversation
clydin
added
the
target: lts
clydin
force-pushed
the
vite-allowed-hosts-17.3.x
branch
2 times, most recently
from
ff47713 to
92fd484
Compare
Version update from 5.1.8 to address advisory GHSA-vg6x-rcgg-rjx6 Vite version 5.4.12+, 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-17.3.x
branch
from
92fd484 to
d44bee2
Compare
…wn error: Chrome failed to start: crashed` This fixes an issue where protractor integration tests are failing with ``` [07:38:37] I/direct - Using ChromeDriver directly... [07:38:39] E/launcher - unknown error: Chrome failed to start: crashed. (unknown error: DevToolsActivePort file doesn't exist) ``` (cherry picked from commit 0718e1b)
clydin
added
the
action: review
alan-agius4
approved these changes
Feb 12, 2025
alan-agius4
added
action: merge
clydin
added
action: merge
|
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. |
This file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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 5.1.8 to address advisory GHSA-vg6x-rcgg-rjx6
Vite version 5.4.12+, 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: