v7.x: backport update to V8 5.5 by targos · Pull Request #11029 · nodejs/node
On Thu, Jan 26, 2017, 3:35 PM Michaël Zasso ***@***.***> wrote: This is a backport of the update to V8 5.5 for v7.x. Additions are: - Revert of the breaking UTF-8 decoder changes - Patches to recover ABI/API compatibility with V8 5.4 - Patches to keep compatibility with all platforms supported by v7.x /cc @nodejs/collaborators <https://github.com/orgs/nodejs/teams/collaborators> CI: https://ci.nod
GitHub - nodejs/version-management: Discussion Group for Version Management
This repo and discussion group is to facilitate collaboration amongst maintainers and stakeholders for Node version and runtime configuration managers. Its purpose is to arrive at recommendations and a roadmap for version management under the auspices of Node.js core and the Node.js Foundation, per request of the Node.js TSC in its Nov-3-2016 meeting. The TSC has asked for these at their next meet
GitHub - nodejs/citgm: Canary in the Gold Mine
Usage: citgm [options] <module> Options: -h, --help output usage information -V, --version output the version number --config Path to a JSON config file -v, --verbose, --loglevel [level], Verbose output (silly, verbose, info, warn, error) -q, --npm-loglevel [level] Verbose output (silent, error, warn, http, info, verbose, silly) -l, --lookup <path> Use the lookup table provided at <path> -d, --nod
Enable Node.js to run with Microsoft's ChakraCore engine by kunalspathak · Pull Request #4765 · nodejs/node
(Note from the CTC (Fishrock123): This thread is expected to garner a lot of attention. Comments that are not productive to discussing the technical aspects may be removed.) Enable Node.js to optionally build and run on Microsoft's ChakraCore JavaScript engine. We implemented a V8 API shim (aka chakrashim) which takes advantage of ChakraCore runtime hosting APIs (JSRT). This shim implements most e
NG Modules · Issue #5 · nodejs/NG · GitHub
As module subsystem API is locked in io.js this is a place to discuss possible non-backwards compatible improvements to it. As @brendanashworth wrote in nodejs/node#848 all modules have been brought down to "stable" status besides the timers and modules modules, which were locked because we can't risk a change that would end up breaking part of the massive userland system This issue was inspired b
TC39 representation for the Node.js Foundation · Issue #2153 · nodejs/node
I have nowhere else to post this and this is somewhere I can tag with tc-agenda. I'm proposing that we request of the newly formed board that one of the first orders of business should be to work towards membership of ECMA and formal representation by one or more individuals who's core concern is with server-side JavaScript. (Coming up with candidates is another process all together). So far we ha
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
buffer: discuss future direction of Buffer constructor API · Issue #9531 · nodejs/node
GitHub - nodejs/installer: Electron based installer for Node.js.
doc: add domain post mortem by trevnorris · Pull Request #6159 · nodejs/node
util: improve util.format performance by evanlucas · Pull Request #5360 · nodejs/node
node/CHANGELOG.md at v5.8.0 · nodejs/node
002: ES6 module interop by bmeck · Pull Request #3 · nodejs/node-eps
nodejs/promises
doc: use eslint by tflanagan · Pull Request #5053 · nodejs/node
Adding Core support for Promises by chrisdickinson · Pull Request #5020 · nodejs/node
Add initial TLP application for express by jasnell · Pull Request #39 · nodejs/TSC
GitHub - nodejs/inclusivity: Improving inclusivity in the node community
Potential Licensing issues with npm · Issue #3959 · nodejs/node
Isomorphism · Issue #17 · nodejs/NG
node/CHANGELOG.md at main · nodejs/node
