-
Notifications
You must be signed in to change notification settings - Fork 27.3k
Upgrade to Node v4 #4375
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
Closed
Closed
Upgrade to Node v4 #4375
Changes from all commits
Commits
Show all changes
12 commits
Select commit
Hold shift + click to select a range
648d0b3
build(travis): bump node version to 4.1.1 and npm to 2.14.5
IgorMinar 24d89d7
build(gulp): bump check-environment node version to 4.1.1 and npm to …
IgorMinar 8c2d29c
build(npm): update chokidar and karma* dependencies
IgorMinar 192ccdd
build(npm): upgrade gulp-sass to v2.0.4
IgorMinar 47b0394
build(npm): resolve shrinkwrap conflicts after rebase
IgorMinar dec80ad
fix(tslint): fix d.ts file paths for node_modules dependencies
IgorMinar 7306914
fix(karma-dart-evalcache): make the code compatible with karma 0.13.x
IgorMinar d0b10d9
fix(karma): socket.io 1.x transport is now called 'polling' instead o…
IgorMinar 16213e0
test(tools): temporarily disable tests that depend on mock-fs
IgorMinar 5f5f304
style(gulp): make code more readable
IgorMinar 5bb2057
build(travis): add travis log folding for verbose tasks
IgorMinar 16fd7f0
fix(gulp): use the new karma.Server api
IgorMinar File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you really want to pin it that much? 0.12 was a range (currently matching 0.12.7).
Related: angular/protractor#2543
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I just want to ensure that ci uses the same version as what we use locally. So my preference is to pin it down to an exact version and update that once in a while. (especially since newer node version could update npm and cause conflicts...)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm, makes sense, I guess. We can still use a newer version locally but CI might be more stable when no unplanned Node update happens.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yup
On Wed, Sep 30, 2015 at 3:18 PM Michał Gołębiowski notifications@github.com
wrote: