(C:\Program Files\nodejs\node_modules\npm\lib\utils\lifecycle.js:233:16)ġ7933 verbose stack at emitTwo (events.js:87:13)ġ7933 verbose stack at EventEmitter.emit (events.js:172:7)ġ7933 verbose stack at ChildProcess.
#NODE JS WINDOWS XP INSTALL#
Whomever is still using Windows XP has more serious problems than not being able to run latest Node.js versions.Windows XP after update node.js to 5 version trying to install grunt-sassġ7931 warn EPACKAGEJSON No repository field.ġ7932 warn EPACKAGEJSON No license field.ġ7933 verbose stack Error: postinstall: node scripts/build.jsġ7933 verbose stack Exit status 3221225477ġ7933 verbose stack at EventEmitter.Currently, Windows XP (and Vista) support causes visible maintance burden, that's wasting developers time for no good reason.To my understanding, that would mean that any v8 updates (even the security-related ones) could break on Windows XP - they won't test it or care about it. Chrome will be dropping Windows XP and Vista support on April 2016.The platform itself is insecure, users should not be encouraged staying on it. By the Node.js v6 release that would make 2 years. Windows XP does not receive security updates for more than 1½ years now.I'm assuming that 6.0 target release date is around April 2016, based on this schedule.
0 kommentar(er)
