| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
heads-up that there might be a test failure but I'm not sure why it's happening only on test-npm but I'll check that out tomorrow. Edit: there was a thing with tap, and manually bumping to tap@7 fixed the issue. Next release will probably include that, but since it's just a testrunner issue. I've included a patch in this PR to that effect. |
Sorry, something went wrong.
|
@zkat So all tests passed except for one, and that one was fixed by upgrading to tap@7? |
Sorry, something went wrong.
|
@gibfahn all tests should pass. I pushed a patch that bumps the tap version. This PR should not have any failing tests. |
Sorry, something went wrong.
|
git am fails with a conflict...? curl -L https://github.com/nodejs/node/pull/8706.patch | git am
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 138 0 138 0 0 355 0 --:--:-- --:--:-- --:--:-- 355
100 3817k 0 3817k 0 0 1490k 0 --:--:-- 0:00:02 --:--:-- 1815k
Applying: deps: upgrade npm to 3.10.8
/Users/Jeremiah/Documents/node/.git/rebase-apply/patch:2388: trailing whitespace.
The `--ignore-scripts` argument will cause npm to not execute any
/Users/Jeremiah/Documents/node/.git/rebase-apply/patch:2527: trailing whitespace.
3. Developer, works on packages they are given access to.
/Users/Jeremiah/Documents/node/.git/rebase-apply/patch:2536: trailing whitespace.
* Grant access:
/Users/Jeremiah/Documents/node/.git/rebase-apply/patch:2549: trailing whitespace.
default will only publish internally.
/Users/Jeremiah/Documents/node/.git/rebase-apply/patch:3139: trailing whitespace.
<p>The <code>--ignore-scripts</code> argument will cause npm to not execute any
error: deps/npm/node_modules/request/node_modules/form-data/README.md: already exists in working directory
Patch failed at 0001 deps: upgrade npm to 3.10.8
The copy of the patch that failed is found in:
/Users/Jeremiah/Documents/node/.git/rebase-apply/patch
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".
|
Sorry, something went wrong.
|
Hmm, git am -3 seems to have worked. Running tests. |
Sorry, something went wrong.
|
@Fishrock123 that's the casing bug again. It looks like my local copy of form-data's README is README.md (???), but the version in their repo is Readme.md (?!?!?!) Siiiigh :\ |
Sorry, something went wrong.
|
Tests passing, LGTM |
Sorry, something went wrong.
|
Thanks! Landed in 33aa953...6b443d1 |
Sorry, something went wrong.
PR-URL: #8706 Reviewed-By: Jeremiah Senkpiel <fishrock123@rocketmail.com>
PR-URL: #8706 Reviewed-By: Jeremiah Senkpiel <fishrock123@rocketmail.com>
PR-URL: #8706 Reviewed-By: Jeremiah Senkpiel <fishrock123@rocketmail.com>
PR-URL: #8706 Reviewed-By: Jeremiah Senkpiel <fishrock123@rocketmail.com>
PR-URL: #8706 Reviewed-By: Jeremiah Senkpiel <fishrock123@rocketmail.com>
PR-URL: #8706 Reviewed-By: Jeremiah Senkpiel <fishrock123@rocketmail.com>
* fs: - `SyncWriteStream` now inherits from `Stream.Writable`. (Anna Henningsen) #8830 - Practically, this means that when stdio is piped to a file, stdout and stderr will still be `Writable` streams. - `fs.existsSync()` has been undeprecated. `fs.exists()` remains deprecated. (Dan Fabulich) #8364 * http: `http.request()` now accepts a `timeout` option. (Rene Weber) #8101 * module: The module loader now maintains its own realpath cache. (Anna Henningsen) #8100 * npm: Upgraded to 3.10.8 (Kat Marchán) #8706 * stream: `Duplex` streams now show proper `instanceof Stream.Writable`. (Anna Henningsen) #8834 * timers: Improved `setTimeout`/`Interval` performance by up to 22%. (Brian White) #8661 PR-URL: #9034
* fs: - `SyncWriteStream` now inherits from `Stream.Writable`. (Anna Henningsen) #8830 - Practically, this means that when stdio is piped to a file, stdout and stderr will still be `Writable` streams. - `fs.existsSync()` has been undeprecated. `fs.exists()` remains deprecated. (Dan Fabulich) #8364 * http: `http.request()` now accepts a `timeout` option. (Rene Weber) #8101 * module: The module loader now maintains its own realpath cache. (Anna Henningsen) #8100 * npm: Upgraded to 3.10.8 (Kat Marchán) #8706 * stream: `Duplex` streams now show proper `instanceof Stream.Writable`. (Anna Henningsen) #8834 * timers: Improved `setTimeout`/`Interval` performance by up to 22%. (Brian White) #8661 PR-URL: #9034
* fs:
- `SyncWriteStream` now inherits from `Stream.Writable`. (Anna
Henningsen) nodejs/node#8830
- Practically, this means that when stdio is piped to a file,
stdout and stderr will still be `Writable` streams.
- `fs.existsSync()` has been undeprecated. `fs.exists()` remains
deprecated. (Dan Fabulich) nodejs/node#8364
* http: `http.request()` now accepts a `timeout` option. (Rene Weber)
nodejs/node#8101
* module: The module loader now maintains its own realpath cache. (Anna
Henningsen) nodejs/node#8100
* npm: Upgraded to 3.10.8 (Kat Marchan)
nodejs/node#8706
* stream: `Duplex` streams now show proper `instanceof
Stream.Writable`. (Anna Henningsen)
nodejs/node#8834
* timers: Improved `setTimeout`/`Interval` performance by up to 22%.
(Brian White) nodejs/node#8661
Signed-off-by: Ilkka Myller <ilkka.myller@nodefield.com>
* fs:
- `SyncWriteStream` now inherits from `Stream.Writable`. (Anna
Henningsen) nodejs/node#8830
- Practically, this means that when stdio is piped to a file,
stdout and stderr will still be `Writable` streams.
- `fs.existsSync()` has been undeprecated. `fs.exists()` remains
deprecated. (Dan Fabulich) nodejs/node#8364
* http: `http.request()` now accepts a `timeout` option. (Rene Weber)
nodejs/node#8101
* module: The module loader now maintains its own realpath cache. (Anna
Henningsen) nodejs/node#8100
* npm: Upgraded to 3.10.8 (Kat Marchan)
nodejs/node#8706
* stream: `Duplex` streams now show proper `instanceof
Stream.Writable`. (Anna Henningsen)
nodejs/node#8834
* timers: Improved `setTimeout`/`Interval` performance by up to 22%.
(Brian White) nodejs/node#8661
Signed-off-by: Ilkka Myller <ilkka.myller@nodefield.com>
| Back | FazBrowse Home | New Git URL |
Checklist
Affected core subsystem(s)
Description of change
Hey y'all!
I know it's been a while, since the npm CLI team moved to a monthly release cadence, but here's the latest and greatest in packaging technology!
Also! It might be of interest to y'all to know that the CLI team is planning to release npm@4 as our next latest with that October release. Of course, npm@3 will continue to be supported, since we're assuming it's what's gonna go into node@6 LTS. The breaking changes in npm@4 will be much less significant than those in npm@3 so it should have less impact overall. 👍
Notable Changes:
Changelogs
r: @thealphanerd
r: @addaleax