Create a new pull request by comparing changes across two branches #1117
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
…on in favor of `stringToFileBuffer` BREAKING CHANGE: The deprecated `fileBuffer` function is no longer available. Update your code to use `stringToFileBuffer` instead to maintain compatibility. **Note:** that this change does not affect application developers.
These server tests frequently fail due to timeouts. Despite efforts, the root cause has not yet been identified, so they are being marked as flaky to prevent blocking the pipeline while further investigation continues.
The `resetAngularServerApp` method was identical to `destroyAngularServerApp` and was mistakenly retained due to an incorrect merge. This commit removes the redundant method.
…lize/init` polyfill and related warnings The logic that automatically added the `@angular/localize/init` polyfill has been removed. BREAKING CHANGE: The `@angular/localize/init` polyfill will no longer be added automatically to projects. To prevent runtime issues, ensure that this polyfill is manually included in the "polyfills" section of your "angular.json" file if your application relies on Angular localization features.
…erverApp` Introduce support for handling request signal abortions in the `AngularServerApp`. This is particularly useful in the development server integration where a 30-second timeout is enforced for requests/responses.
…rget` The `browserTarget` option has been removed as part of the refactoring process. This option was part of a private API and is no longer used. Projects relying on this option should migrate to using the `buildTarget` option. BREAKING CHANGE: The `browserTarget` option has been removed from the DevServer and ExtractI18n builders. `buildTarget` is to be used instead.
…tyle budget thresholds The 2kB/4kB warning/error thresholds for any component style within an application has now been increased to 4kB/8kB for warnings/errors respectively. This allows for more complex styles within a component while also reducing the likelihood of the budget rule being disabled or removed. The new limits still provide diagnostics for extreme size cases such as accidentally importing all Bootstrap or Material styles into an individual component. Such instances are a primary use case for the budget.
…in `AngularServerApp` Removed redundant `.push()` call by directly adding the provider during array initialization phase.
…export The `@angular/compiler-cli/private/tooling` package export is now used instead of the main package export to allow cleanup of the compiler-cli package. This secondary export has existed for several major versions.
…vate tooling export The `@angular/compiler-cli/private/tooling` package export is now used instead of the main package export to allow cleanup of the compiler-cli package. This secondary export has existed for several major versions.
…port The `@angular/compiler-cli/private/tooling` package export is now used instead of the main package export to allow cleanup of the compiler-cli package. This secondary export has existed for several major versions.
The exclude field has been removed from `tsconfig-build.json` as it is redundant. This configuration is used by Bazel, which already specifies the input files explicitly, making the exclude field unnecessary. This change simplifies the configuration without impacting the build process.
…server` This is a required peer dependency which was not listed.
GulajavaMinistudio
merged commit 0bad3b7
into
angular-indonesia:master
4 of 37 checks passed
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.
PR Checklist
Please check to confirm your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Issue Number: N/A
What is the new behavior?
Does this PR introduce a breaking change?
Other information