Skip to content
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

build: update repository to node@16 locally #44211

Closed
wants to merge 2 commits into from

Conversation

josephperrott
Copy link
Member

@josephperrott josephperrott commented Nov 18, 2021

As node 16 is now active LTS, updating to node 16 is a better choice for our own development. Notably its
support for M1 chips is an important value add for us.

@josephperrott josephperrott added comp: build & ci target: patch labels Nov 18, 2021
@ngbot ngbot bot added this to the Backlog milestone Nov 18, 2021
@ngbot ngbot bot added this to the Backlog milestone Nov 18, 2021
@google-cla google-cla bot added the cla: yes label Nov 18, 2021
In node@16 the URL constructor fails for for a malformed URL such as http://<empty>/. Instead http://_empty_ is
used as this conveys the same information in tests but is correctly formed.
As node 16 is now active LTS, updating to node 16 is a better choice for our own development. Notably its
support for M1 chips is an important value add for us.
@josephperrott josephperrott marked this pull request as ready for review Nov 20, 2021
@pullapprove pullapprove bot requested review from AndrewKushnir and atscott Nov 20, 2021
@josephperrott josephperrott removed the request for review from atscott Nov 22, 2021
@AndrewKushnir
Copy link
Contributor

@AndrewKushnir AndrewKushnir commented Nov 24, 2021

@josephperrott just wanted to ask if this PR is ready for merge :)

@josephperrott josephperrott added the action: merge label Nov 24, 2021
@jessicajaniuk
Copy link
Contributor

@jessicajaniuk jessicajaniuk commented Nov 24, 2021

This PR was merged into the repository by commit 0ad0054.

jessicajaniuk pushed a commit that referenced this issue Nov 24, 2021
…4211)

In node@16 the URL constructor fails for for a malformed URL such as http://<empty>/. Instead http://_empty_ is
used as this conveys the same information in tests but is correctly formed.

PR Close #44211
jessicajaniuk pushed a commit that referenced this issue Nov 24, 2021
As node 16 is now active LTS, updating to node 16 is a better choice for our own development. Notably its
support for M1 chips is an important value add for us.

PR Close #44211
jessicajaniuk pushed a commit that referenced this issue Nov 24, 2021
As node 16 is now active LTS, updating to node 16 is a better choice for our own development. Notably its
support for M1 chips is an important value add for us.

PR Close #44211
@josephperrott josephperrott deleted the update-node branch Nov 29, 2021
dimakuba pushed a commit to dimakuba/angular that referenced this issue Dec 28, 2021
…gular#44211)

In node@16 the URL constructor fails for for a malformed URL such as http://<empty>/. Instead http://_empty_ is
used as this conveys the same information in tests but is correctly formed.

PR Close angular#44211
dimakuba pushed a commit to dimakuba/angular that referenced this issue Dec 28, 2021
As node 16 is now active LTS, updating to node 16 is a better choice for our own development. Notably its
support for M1 chips is an important value add for us.

PR Close angular#44211
@angular-automatic-lock-bot
Copy link

@angular-automatic-lock-bot angular-automatic-lock-bot bot commented Dec 30, 2021

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Dec 30, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge cla: yes comp: build & ci target: patch
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants