Skip to content
This repository has been archived by the owner on Apr 22, 2023. It is now read-only.

npm fails on windows 7 x64 when calls to node-gyp.js rebuild #4047

Closed
Babay88 opened this issue Sep 22, 2012 · 31 comments
Closed

npm fails on windows 7 x64 when calls to node-gyp.js rebuild #4047

Babay88 opened this issue Sep 22, 2012 · 31 comments

Comments

@Babay88
Copy link

Babay88 commented Sep 22, 2012

system: Windows7 x64, node.js x64. python 2.7.3.
trying to install pg or sqlite3. both call node-gyp.js rebuild - and that causes an error.
sorry, I have russian windows - that causes "???"

D:\job\TimeRecordService>npm install sqlite3
 npm http GET https://registry.npmjs.org/sqlite3
 npm http 200 https://registry.npmjs.org/sqlite3
 npm http GET https://registry.npmjs.org/sqlite3/-/sqlite3-2.1.5.tgz
 npm http 200 https://registry.npmjs.org/sqlite3/-/sqlite3-2.1.5.tgz

sqlite3@2.1.5 install D:\job\TimeRecordService\node_modules\sqlite3
 node-gyp rebuild

D:\job\TimeRecordService\node_modules\sqlite3>node "C:\Program Files\nodejs\node_modules\npm\bin\node-gyp-bin....\node_modules\node-gyp\bin\node-gyp.js" rebuild
 gyp ERR! configure error
 gyp ERR! stack Error: Command failed: CreateProcessW: ???????? ? ???????.
 gyp ERR! stack
 gyp ERR! stack at ChildProcess.exithandler (child_process.js:540:15)
 gyp ERR! stack at ChildProcess.EventEmitter.emit (events.js:91:17)
 gyp ERR! stack at maybeClose (child_process.js:638:16)
 gyp ERR! stack at Socket.ChildProcess.spawn.stdin (child_process.js:815:11)
 gyp ERR! stack at Socket.EventEmitter.emit (events.js:88:17)
 gyp ERR! stack at Socket._destroy.destroyed (net.js:357:10)
 gyp ERR! stack at process.startup.processNextTick.process._tickCallback (node.js:244:9)
 gyp ERR! System Windows_NT 6.1.7601
 gyp ERR! command "node" "C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js" "rebuil
 d"
 gyp ERR! cwd D:\job\TimeRecordService\node_modules\sqlite3
 gyp ERR! node -v v0.8.9
 gyp ERR! node-gyp -v v0.6.8
 gyp ERR! not ok
 npm ERR! sqlite3@2.1.5 install: node-gyp rebuild
 npm ERR! cmd "/c" "node-gyp rebuild" failed with 1
@TooTallNate
Copy link

Wow, crazy timing. I was literally just booting up my VM to report the same issue.

I should note that when invoking npm install xxx from cmd.exe, things work as expected. But when I invoke the command from a Git Bash, or Mozilla Build (which is also bash) window, then I get this error.

@piscisaureus
Copy link

odd. It works here from git-bash.

@piscisaureus
Copy link

@TooTallNate What error do you get? The ??????? doesn't really help, but I suppose that you don't have a russian windows.

@TooTallNate
Copy link

"The system cannot find the file specified."

@Babay88
Copy link
Author

Babay88 commented Sep 22, 2012

@TooTallNate, nope, I have the same error when I run "node-gyp.js rebuild" from command-line

@TooTallNate
Copy link

@Babay88 Ya, I think that happens when node-gyp tries to spawn python.exe. I think it's the same core issue though.

@TooTallNate
Copy link

@piscisaureus I think this is the same as #3968.

@Babay88
Copy link
Author

Babay88 commented Sep 22, 2012

@TooTallNate, I guess so. but I can't get any additional info on that (

@piscisaureus
Copy link

@piscisaureus I think this is the same as #3968.

@TooTallNate That'd be surprising; that issue is about being unable to spawn .bat/.cmd files, but if python.exe is on your PATH then it should just try to use that.

@Babay88
Copy link
Author

Babay88 commented Sep 22, 2012

@TooTallNate, do you think node-gyp configure runs npm ? that error is for launching bat files, not python.

D:\job\TimeRecordService>node "C:\Program Files\nodejs\node_modules\npm\bin\node-gyp-bin\\..\..\node_modules\node-gyp\bin\node-gyp.js" configure
gyp info it worked if it ends with ok
gyp info using node-gyp@0.6.8
gyp info using node@0.8.9 | win32 | x64
gyp ERR! configure error
gyp ERR! stack Error: Command failed: CreateProcessW: ???????? ? ???????.
gyp ERR! stack
gyp ERR! stack     at ChildProcess.exithandler (child_process.js:540:15)
gyp ERR! stack     at ChildProcess.EventEmitter.emit (events.js:91:17)
gyp ERR! stack     at maybeClose (child_process.js:638:16)
gyp ERR! stack     at Socket.ChildProcess.spawn.stdin (child_process.js:815:11)
gyp ERR! stack     at Socket.EventEmitter.emit (events.js:88:17)
gyp ERR! stack     at Socket._destroy.destroyed (net.js:357:10)
gyp ERR! stack     at process.startup.processNextTick.process._tickCallback (node.js:244:9)
gyp ERR! System Windows_NT 6.1.7601
gyp ERR! command "node" "C:\\Program Files\\nodejs\\node_modules\\npm\\node_modules\\node-gyp\\bin\\node-gyp.js" "config
ure"
gyp ERR! cwd D:\job\TimeRecordService
gyp ERR! node -v v0.8.9
gyp ERR! node-gyp -v v0.6.8
gyp ERR! not ok

@TooTallNate
Copy link

Actually, running node-gyp rebuild manually works for me. Nix my comment
about python.exe.

On Fri, Sep 21, 2012 at 8:14 PM, Bert Belder notifications@git.luolix.topwrote:

@piscisaureus https://github.com/piscisaureus I think this is the same
as #3968 #3968.

@TooTallNate https://github.com/TooTallNate That'd be surprising; that
issue is about being unable to spawn .bat/.cmd files, but if python.exe is
on your PATH then it should just try to use that.


Reply to this email directly or view it on GitHubhttps://github.com//issues/4047#issuecomment-8785071.

@Babay88
Copy link
Author

Babay88 commented Sep 22, 2012

??? - is a "Access is denied" error. I can't get rid of it.
I set full control to users for python27 folder and for folder where nodeJS is located. user has also full control rights for current folder too.
I ran cmd as an administrator - that didn't helped either.
and I can't find, what permission is denied.

@Babay88
Copy link
Author

Babay88 commented Sep 26, 2012

as a result if solving:
the probles was: PYTHON environment variable had value "c:\python27" - and node-gyp tryed to run a directory.
setting PYTHON="c:\python27\python.exe" ot removing it (so node-gym guessed the location) solved the error.
but... error-reporting is bad.

@muchine
Copy link

muchine commented Oct 8, 2012

I had exactly the same problem. node-expat installation worked fine after changing PYTHON env to poin to python.exe file. However, I faced the "msbuild.exe" failure.... I have to dig around it.

@skopp
Copy link

skopp commented Dec 20, 2012

I have this issue... tried with cmd prompt win-mingsys32 shell and then with cygwin, where I force closed the window because it seemed to be stuck.

Gosh, as I was typing, I had been trying a third time using the cmd prompt again... and this is the output:

npm install -g node-gyp
npm http GET https://registry.npmjs.org/node-gyp
npm http 200 https://registry.npmjs.org/node-gyp
npm http GET https://registry.npmjs.org/node-gyp/-/node-gyp-0.8.1.tgz
npm http 200 https://registry.npmjs.org/node-gyp/-/node-gyp-0.8.1.tgz
npm http GET https://registry.npmjs.org/which
npm http GET https://registry.npmjs.org/glob
npm http GET https://registry.npmjs.org/osenv
npm http GET https://registry.npmjs.org/request
npm http GET https://registry.npmjs.org/nopt
npm http GET https://registry.npmjs.org/minimatch
npm http GET https://registry.npmjs.org/rimraf
npm http GET https://registry.npmjs.org/fstream
npm http GET https://registry.npmjs.org/mkdirp
npm http GET https://registry.npmjs.org/graceful-fs
npm http GET https://registry.npmjs.org/semver
npm http GET https://registry.npmjs.org/npmlog
npm http GET https://registry.npmjs.org/tar
npm http 304 https://registry.npmjs.org/glob
npm http 304 https://registry.npmjs.org/nopt
npm http 200 https://registry.npmjs.org/osenv
npm http 304 https://registry.npmjs.org/minimatch
npm http 304 https://registry.npmjs.org/rimraf
npm http 200 https://registry.npmjs.org/which
npm http GET https://registry.npmjs.org/osenv/-/osenv-0.0.3.tgz
npm http GET https://registry.npmjs.org/which/-/which-1.0.5.tgz
npm http 304 https://registry.npmjs.org/request
npm http 304 https://registry.npmjs.org/mkdirp
npm http 304 https://registry.npmjs.org/graceful-fs
npm http 304 https://registry.npmjs.org/semver
npm http 304 https://registry.npmjs.org/tar
npm http 304 https://registry.npmjs.org/npmlog
npm http 200 https://registry.npmjs.org/osenv/-/osenv-0.0.3.tgz
npm http 200 https://registry.npmjs.org/fstream
npm http 200 https://registry.npmjs.org/which/-/which-1.0.5.tgz
npm http GET https://registry.npmjs.org/fstream/-/fstream-0.1.20.tgz
npm http 200 https://registry.npmjs.org/fstream/-/fstream-0.1.20.tgz
npm http GET https://registry.npmjs.org/abbrev
npm http GET https://registry.npmjs.org/ansi
npm http GET https://registry.npmjs.org/lru-cache
npm http GET https://registry.npmjs.org/sigmund
npm http GET https://registry.npmjs.org/inherits
npm http GET https://registry.npmjs.org/inherits
npm http GET https://registry.npmjs.org/inherits
npm http GET https://registry.npmjs.org/block-stream
npm http 304 https://registry.npmjs.org/ansi
npm http 304 https://registry.npmjs.org/abbrev
npm http 304 https://registry.npmjs.org/inherits
npm http 304 https://registry.npmjs.org/inherits
npm http 304 https://registry.npmjs.org/lru-cache
npm http 304 https://registry.npmjs.org/sigmund
npm http 304 https://registry.npmjs.org/inherits
npm http 304 https://registry.npmjs.org/block-stream
C:\Users\Rash\AppData\Roaming\npm\node-gyp -> C:\Users\Rash\AppData\Roaming\npm\
node_modules\node-gyp\bin\node-gyp.js
node-gyp@0.8.1  __path to ...\npm\node_modules\node-gyp
├── osenv@0.0.3
├── which@1.0.5
├── graceful-fs@1.1.14
├── semver@1.1.1
├── rimraf@2.0.3
├── mkdirp@0.3.4
├── nopt@2.0.0 (abbrev@1.0.3)
├── glob@3.1.14 (inherits@1.0.0)
├── fstream@0.1.20 (inherits@1.0.0)
├── request@2.9.203
├── npmlog@0.0.2 (ansi@0.1.2)
├── minimatch@0.2.9 (lru-cache@2.0.4, sigmund@1.0.0)
└── tar@0.1.14 (inherits@1.0.0, block-stream@0.0.6) 

As I said it just processed, so I will check it out and report soon hopefully

@bnoordhuis
Copy link
Member

No activity in 10 months, assuming stale. Closing.

@aodj
Copy link

aodj commented Feb 27, 2014

For any one looking for a solution I found setting the PYTHON environment variable to the full path to the python.exe resolved the issue.

@avinashega
Copy link

setting the path to python.exe resolved the issue for me too. Thanks.

@aurbano
Copy link

aurbano commented Mar 4, 2014

Tried using the solution by @aodj with no luck. Here is the output:

gyp ERR! build error
gyp ERR! stack Error: `C:\Windows\Microsoft.NET\Framework\v4.0.30319\msbuild.exe` failed with exit code: 1
gyp ERR! stack     at ChildProcess.onExit (C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\build.js:267:23)
gyp ERR! stack     at ChildProcess.EventEmitter.emit (events.js:98:17)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (child_process.js:797:12)
gyp ERR! System Windows_NT 6.1.7601
gyp ERR! command "node" "C:\\Program Files\\nodejs\\node_modules\\npm\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild"
gyp ERR! cwd F:\Alejandro\proyects\prerender\node_modules\phantom-cluster\node_modules\phantom\node_modules\dnode\node_modules\weak
gyp ERR! node -v v0.10.26
gyp ERR! node-gyp -v v0.12.2
gyp ERR! not ok

I have installed:

  • Visual Studio C++ 2005, 2008, 2010, and 2012.
  • Win7 64 bit SDK
  • Python 2.7.6

Any ideas?

@avinashega
Copy link

did you try this ?

npm install <module_name> --msvs_version=2012

@aurbano
Copy link

aurbano commented Mar 5, 2014

That did it! I was thinking that the problem might be that it wasn't using
the right version, but I couldn't find a way to do it.
Thanks

@AurelienDevGames
Copy link

@avinashega solution worked for me too 👍

@jafet-gonzalez
Copy link

@aurbano thanks man , i was searching for this all day

@avevlad
Copy link

avevlad commented Sep 25, 2014

c:\Users\Vlad\projects\av\node_modules\base64>node "c:\Program Files\nodejs\node_modules\npm\bin\node-gyp-bin\\..\..\node_modules\node-gyp\bin\node-gyp.js" rebuild
gyp ERR! configure error
gyp ERR! stack Error: spawn ENOENT
gyp ERR! stack     at errnoException (child_process.js:1001:11)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (child_process.js:792:34)
gyp ERR! System Windows_NT 6.2.9200
gyp ERR! command "node" "c:\\Program Files\\nodejs\\node_modules\\npm\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild"
gyp ERR! cwd c:\Users\Vlad\projects\av\node_modules\base64
gyp ERR! node -v v0.10.32
gyp ERR! node-gyp -v v1.0.1
gyp ERR! not ok
-

@pVesian
Copy link

pVesian commented Nov 2, 2014

It's an old issue, but I just had this error with a fresh install on my Windows 7. I just went to http://nodejs.org/ and clicked "install" and executed the MSI (v0.10.33).
If node-gyp needs Python, why isn't it installed with Node if it's a dependency?

Edit: I just figured out I need Visual Studio too. No way install that shit on my PC, I'm out of here.

@evil-shrike
Copy link

I'm experiencing this issue when installing Sinopia (actually crypt3 which it depends on). I have Python installed and in PATH. I also have Visual Studio with C++ installed (2013, 2010) and all VC++ redistributables.

C:\Work\R-n-D> npm install -g sinopia
C:\Program Files\nodejs\sinopia -> C:\Program Files\nodejs\node_modules\sinopia\bin\sinopia

> crypt3@0.1.6 install C:\Program Files\nodejs\node_modules\sinopia\node_modules\crypt3
> node-gyp rebuild


C:\Program Files\nodejs\node_modules\sinopia\node_modules\crypt3>node "C:\Program Files\nodejs\node_modules\npm\bin\node-gyp-bin\\..\..\node_modules\node-gyp\bin\node-gyp.js" rebuild
Building the projects in this solution one at a time. To enable parallel build, please add the "/m" switch.

C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\Microsoft.Cpp.InvalidPlatform.Targets(23,7): error MSB80 07: The Platform for project 'crypt3.vcxproj' is invalid.  Platform='x64'. You may be seeing this message
because you are trying to build a project without a solution file, and have specified a non-default Platfo rm that doesn't exist for this project. [C:\Program Files\nodejs\node_modules\sinopia\node_modules\crypt3\ build\crypt3.vcxproj]
gyp ERR! build error
gyp ERR! stack Error: `msbuild` failed with exit code: 1
gyp ERR! stack     at ChildProcess.onExit (C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\build.js:267:23)
gyp ERR! stack     at ChildProcess.EventEmitter.emit (events.js:98:17)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (child_process.js:797:12)
gyp ERR! System Windows_NT 6.1.7601
gyp ERR! command "node" "C:\\Program Files\\nodejs\\node_modules\\npm\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild"
gyp ERR! cwd C:\Program Files\nodejs\node_modules\sinopia\node_modules\crypt3
gyp ERR! node -v v0.10.26
gyp ERR! node-gyp -v v1.0.2
gyp ERR! not ok
npm ERR! Windows_NT 6.1.7601
npm ERR! argv "C:\\Program Files\\nodejs\\\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install" "-g" "sinopia"
npm ERR! node v0.10.26
npm ERR! npm  v2.1.9
npm ERR! code ELIFECYCLE

npm ERR! crypt3@0.1.6 install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the crypt3@0.1.6 install script 'node-gyp rebuild'.
npm ERR! This is most likely a problem with the crypt3 package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-gyp rebuild
npm ERR! You can get their info via:
npm ERR!     npm owner ls crypt3
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     C:\Work\R-n-D\npm-debug.log

C:\...js\node_modules\npm\node_modules\node-gyp\lib>python
Python 2.7.5 (default, May 15 2013, 22:44:16) [MSC v.1500 64 bit (AMD64)] on win32

@othiym23
Copy link

Hey, everybody:

  1. @evil-shrike Your problem looks like either an issue with crypt3's gypfile or with the version of VS you're using to build it. It's not a Node or npm issue.
  2. Everybody, while Node packages npm, this issue tracker isn't a great place to get help with it. File issues with npm on npm/npm.

Thanks!

@ntbinh
Copy link

ntbinh commented Dec 23, 2014

@avinashega: you saved my live 👍

@hqxluoyang
Copy link

node-rebuild error

@ahgood
Copy link

ahgood commented Nov 9, 2015

Try to run cmd.exe as administrator role.

@hometlt
Copy link

hometlt commented Apr 6, 2016

this article helps me https://www.robertkehoe.com/2015/03/fix-node-gyp-rebuild-error-on-windows/

npm config set python /Python27/python.exe --global

gibfahn pushed a commit to ibmruntimes/node that referenced this issue Apr 26, 2016
The following significant (semver-major) changes have been made since the
previous Node v5.0.0 release.

* Buffer
  * New Buffer constructors have been added
    [nodejs#4682](nodejs/node#4682)
  * Previously deprecated Buffer APIs are removed
    [nodejs#5048](nodejs/node#5048),
    [nodejs#4594](nodejs/node#4594)
  * Improved error handling [nodejs#4514](nodejs/node#4514)
* Cluster
  * Worker emitted as first argument in 'message' event
    [nodejs#5361](nodejs/node#5361).
* Crypto
  * Improved error handling [nodejs#3100](nodejs/node#3100),
    [nodejs#5611](nodejs/node#5611)
  * Simplified Certificate class bindings
    [nodejs#5382](nodejs/node#5382)
  * Improved control over FIPS mode
    [nodejs#5181](nodejs/node#5181)
  * pbkdf2 digest overloading is deprecated
    [nodejs#4047](nodejs/node#4047)
* Dependencies
  * Reintroduce shared c-ares build support
    [nodejs#5775](nodejs/node#5775).
  * V8 updated to 5.0.71.31 [nodejs#6111](nodejs/node#6111).
* DNS
  * Add resolvePtr API to query plain DNS PTR records
    [nodejs#4921](nodejs/node#4921).
* Domains
  * Clear stack when no error handler
  [nodejs#4659](nodejs/node#4659).
* File System
  * The `fs.realpath()` and `fs.realpathSync()` methods have been updated
    to use a more efficient libuv implementation. This change includes the
    removal of the `cache` argument and the method can throw new errors
    [nodejs#3594](nodejs/node#3594)
  * FS apis can now accept and return paths as Buffers
    [nodejs#5616](nodejs/node#5616).
  * Error handling and type checking improvements
    [nodejs#5616](nodejs/node#5616),
    [nodejs#5590](nodejs/node#5590),
    [nodejs#4518](nodejs/node#4518),
    [nodejs#3917](nodejs/node#3917).
  * fs.read's string interface is deprecated
    [nodejs#4525](nodejs/node#4525)
* HTTP
  * 'clientError' can now be used to return custom errors from an
    HTTP server [nodejs#4557](nodejs/node#4557).
* Modules
  * Current directory is now prioritized for local lookups
    [nodejs#5689](nodejs/node#5689)
  * Symbolic links are preserved when requiring modules
    [nodejs#5950](nodejs/node#5950)
* Net
  * DNS hints no longer implicitly set
    [nodejs#6021](nodejs/node#6021).
  * Improved error handling and type checking
    [nodejs#5981](nodejs/node#5981),
    [nodejs#5733](nodejs/node#5733),
    [nodejs#2904](nodejs/node#2904)
* Path
  * Improved type checking [nodejs#5348](nodejs/node#5348).
* Process
  * Introduce process warnings API
    [nodejs#4782](nodejs/node#4782).
  * Throw exception when non-function passed to nextTick
    [nodejs#3860](nodejs/node#3860).
* Readline
  * Emit key info unconditionally
    [nodejs#6024](nodejs/node#6024)
* REPL
  * Assignment to `_` will emit a warning.
    [nodejs#5535](nodejs/node#5535)
* Timers
  * Fail early when callback is not a function
    [nodejs#4362](nodejs/node#4362)
* TLS
  * Rename 'clientError' to 'tlsClientError'
    [nodejs#4557](nodejs/node#4557)
  * SHA1 used for sessionIdContext
    [nodejs#3866](nodejs/node#3866)
* TTY
  * Previously deprecated setRawMode wrapper is removed
    [nodejs#2528](nodejs/node#2528).
* Util
  * Changes to Error object formatting
    [nodejs#4582](nodejs/node#4582).
* Windows
  * Windows XP and Vista are no longer supported
    [nodejs#5167](nodejs/node#5167),
    [nodejs#5167](nodejs/node#5167).
gibfahn pushed a commit to ibmruntimes/node that referenced this issue Apr 27, 2016
The following significant (semver-major) changes have been made since the
previous Node v5.0.0 release.

* Buffer
  * New Buffer constructors have been added
    [nodejs#4682](nodejs/node#4682)
  * Previously deprecated Buffer APIs are removed
    [nodejs#5048](nodejs/node#5048),
    [nodejs#4594](nodejs/node#4594)
  * Improved error handling [nodejs#4514](nodejs/node#4514)
* Cluster
  * Worker emitted as first argument in 'message' event
    [nodejs#5361](nodejs/node#5361).
* Crypto
  * Improved error handling [nodejs#3100](nodejs/node#3100),
    [nodejs#5611](nodejs/node#5611)
  * Simplified Certificate class bindings
    [nodejs#5382](nodejs/node#5382)
  * Improved control over FIPS mode
    [nodejs#5181](nodejs/node#5181)
  * pbkdf2 digest overloading is deprecated
    [nodejs#4047](nodejs/node#4047)
* Dependencies
  * Reintroduce shared c-ares build support
    [nodejs#5775](nodejs/node#5775).
  * V8 updated to 5.0.71.31 [nodejs#6111](nodejs/node#6111).
* DNS
  * Add resolvePtr API to query plain DNS PTR records
    [nodejs#4921](nodejs/node#4921).
* Domains
  * Clear stack when no error handler
  [nodejs#4659](nodejs/node#4659).
* File System
  * The `fs.realpath()` and `fs.realpathSync()` methods have been updated
    to use a more efficient libuv implementation. This change includes the
    removal of the `cache` argument and the method can throw new errors
    [nodejs#3594](nodejs/node#3594)
  * FS apis can now accept and return paths as Buffers
    [nodejs#5616](nodejs/node#5616).
  * Error handling and type checking improvements
    [nodejs#5616](nodejs/node#5616),
    [nodejs#5590](nodejs/node#5590),
    [nodejs#4518](nodejs/node#4518),
    [nodejs#3917](nodejs/node#3917).
  * fs.read's string interface is deprecated
    [nodejs#4525](nodejs/node#4525)
* HTTP
  * 'clientError' can now be used to return custom errors from an
    HTTP server [nodejs#4557](nodejs/node#4557).
* Modules
  * Current directory is now prioritized for local lookups
    [nodejs#5689](nodejs/node#5689)
  * Symbolic links are preserved when requiring modules
    [nodejs#5950](nodejs/node#5950)
* Net
  * DNS hints no longer implicitly set
    [nodejs#6021](nodejs/node#6021).
  * Improved error handling and type checking
    [nodejs#5981](nodejs/node#5981),
    [nodejs#5733](nodejs/node#5733),
    [nodejs#2904](nodejs/node#2904)
* OS X
  * MACOSX_DEPLOYMENT_TARGET has been bumped up to 10.7
    [nodejs#6402](nodejs/node#6402).
* Path
  * Improved type checking [nodejs#5348](nodejs/node#5348).
* Process
  * Introduce process warnings API
    [nodejs#4782](nodejs/node#4782).
  * Throw exception when non-function passed to nextTick
    [nodejs#3860](nodejs/node#3860).
* Readline
  * Emit key info unconditionally
    [nodejs#6024](nodejs/node#6024)
* REPL
  * Assignment to `_` will emit a warning.
    [nodejs#5535](nodejs/node#5535)
* Timers
  * Fail early when callback is not a function
    [nodejs#4362](nodejs/node#4362)
* TLS
  * Rename 'clientError' to 'tlsClientError'
    [nodejs#4557](nodejs/node#4557)
  * SHA1 used for sessionIdContext
    [nodejs#3866](nodejs/node#3866)
* TTY
  * Previously deprecated setRawMode wrapper is removed
    [nodejs#2528](nodejs/node#2528).
* Util
  * Changes to Error object formatting
    [nodejs#4582](nodejs/node#4582).
* Windows
  * Windows XP and Vista are no longer supported
    [nodejs#5167](nodejs/node#5167),
    [nodejs#5167](nodejs/node#5167).
gibfahn pushed a commit to ibmruntimes/node that referenced this issue May 6, 2016
The following significant (semver-major) changes have been made since the
previous Node v5.0.0 release.

* Buffer
  * New Buffer constructors have been added
    [nodejs#4682](nodejs/node#4682)
  * Previously deprecated Buffer APIs are removed
    [nodejs#5048](nodejs/node#5048),
    [nodejs#4594](nodejs/node#4594)
  * Improved error handling [nodejs#4514](nodejs/node#4514)
* Cluster
  * Worker emitted as first argument in 'message' event
    [nodejs#5361](nodejs/node#5361).
* Crypto
  * Improved error handling [nodejs#3100](nodejs/node#3100),
    [nodejs#5611](nodejs/node#5611)
  * Simplified Certificate class bindings
    [nodejs#5382](nodejs/node#5382)
  * Improved control over FIPS mode
    [nodejs#5181](nodejs/node#5181)
  * pbkdf2 digest overloading is deprecated
    [nodejs#4047](nodejs/node#4047)
* Dependencies
  * Reintroduce shared c-ares build support
    [nodejs#5775](nodejs/node#5775).
  * V8 updated to 5.0.71.31 [nodejs#6111](nodejs/node#6111).
* DNS
  * Add resolvePtr API to query plain DNS PTR records
    [nodejs#4921](nodejs/node#4921).
* Domains
  * Clear stack when no error handler
  [nodejs#4659](nodejs/node#4659).
* File System
  * The `fs.realpath()` and `fs.realpathSync()` methods have been updated
    to use a more efficient libuv implementation. This change includes the
    removal of the `cache` argument and the method can throw new errors
    [nodejs#3594](nodejs/node#3594)
  * FS apis can now accept and return paths as Buffers
    [nodejs#5616](nodejs/node#5616).
  * Error handling and type checking improvements
    [nodejs#5616](nodejs/node#5616),
    [nodejs#5590](nodejs/node#5590),
    [nodejs#4518](nodejs/node#4518),
    [nodejs#3917](nodejs/node#3917).
  * fs.read's string interface is deprecated
    [nodejs#4525](nodejs/node#4525)
* HTTP
  * 'clientError' can now be used to return custom errors from an
    HTTP server [nodejs#4557](nodejs/node#4557).
* Modules
  * Current directory is now prioritized for local lookups
    [nodejs#5689](nodejs/node#5689)
  * Symbolic links are preserved when requiring modules
    [nodejs#5950](nodejs/node#5950)
* Net
  * DNS hints no longer implicitly set
    [nodejs#6021](nodejs/node#6021).
  * Improved error handling and type checking
    [nodejs#5981](nodejs/node#5981),
    [nodejs#5733](nodejs/node#5733),
    [nodejs#2904](nodejs/node#2904)
* OS X
  * MACOSX_DEPLOYMENT_TARGET has been bumped up to 10.7
    [nodejs#6402](nodejs/node#6402).
* Path
  * Improved type checking [nodejs#5348](nodejs/node#5348).
* Process
  * Introduce process warnings API
    [nodejs#4782](nodejs/node#4782).
  * Throw exception when non-function passed to nextTick
    [nodejs#3860](nodejs/node#3860).
* Readline
  * Emit key info unconditionally
    [nodejs#6024](nodejs/node#6024)
* REPL
  * Assignment to `_` will emit a warning.
    [nodejs#5535](nodejs/node#5535)
* Timers
  * Fail early when callback is not a function
    [nodejs#4362](nodejs/node#4362)
* TLS
  * Rename 'clientError' to 'tlsClientError'
    [nodejs#4557](nodejs/node#4557)
  * SHA1 used for sessionIdContext
    [nodejs#3866](nodejs/node#3866)
* TTY
  * Previously deprecated setRawMode wrapper is removed
    [nodejs#2528](nodejs/node#2528).
* Util
  * Changes to Error object formatting
    [nodejs#4582](nodejs/node#4582).
* Windows
  * Windows XP and Vista are no longer supported
    [nodejs#5167](nodejs/node#5167),
    [nodejs#5167](nodejs/node#5167).
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests