This repository was archived by the owner on Apr 12, 2024. It is now read-only.
build(*): update Node from 6 to 8, update Yarn #16360
Merged
Conversation
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
|
Travis is red. Other than that seems reasonable 😃 |
Angular (2+) switched to Node 8 and so should we. Ref angular/angular#20807 Ref angular/angular#20832
mgol
changed the title
i run |
mgol
added a commit
that referenced
this pull request
Dec 7, 2017
Angular (2+) switched to Node 8 and so should we. Closes #16360 Ref angular/angular#20807 Ref angular/angular#20832
|
thanks @mgol!! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Build-related.
What is the current behavior? (You can also link to an open issue here)
We use Node 6 & an old Yarn version.
What is the new behavior (if this is a feature change)?
We use Node 8 & a new Yarn version.
Does this PR introduce a breaking change?
No.
Please check if the PR fulfills these requirements
Other information:
Angular (2+) switched to Node 8 and so should we.
Ref angular/angular#20807
Ref angular/angular#20832