build: update to angular v15 #131
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
- npx browserslist@latest --update-db - npx ng update @angular/core@14 @angular/cli@14 @angular-eslint/schematics@14 @nguniversal/express-engine@14 @nguniversal/builders@14 --force
- npm i -D ajv@latest core-js@latest - npx ng update @angular/core@15 @angular/cli@15 @angular-eslint/schematics@15 @nguniversal/express-engine@15 @nguniversal/builders@15 --force
|
- sudo usage prevented ENVIRONMENT variables being passed to scripts
|
👋 friendly ping to review the PR @willmendesneto |
|
That's amazing, @chimurai ! I'll check that in details tomorrow and I'll reply in here. Thanks for that, mate! <3 |
willmendesneto
approved these changes
Feb 2, 2023
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.
Please check if the PR fulfills these requirements
guidelines
What kind of change does this PR introduce? (check one with "x")
If it is a Bugfix, please describe the root cause and what could have been done to prevent it…
What is the current behavior? (You can link to an open issue here, add screenshots…)
What is the new behavior?
Does this PR introduce a breaking change? (check one with "x")
If this PR contains a breaking change, please describe the impact and migration
path for existing applications: …
Will need to be using Angular 15+
Other information (if applicable):
Please @mention @people to review this PR…