はてなブックマーク

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert

tl;dr This issue proposes: Change new Buffer(number) to return safe, zeroed-out memory Create a new API for creating uninitialized Buffers, Buffer.alloc(number) Update: Jan 15, 2016 Upon further consideration, I think that returning zeroed out memory is a separate issue. The core issue is: unsafe buffer allocation should be in a different API. I now support adding two APIs: Buffer.from(value) - co

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

It all started with this conversation. As I said, I'm pretty much a newbie and I don't even know what node-gyp does, but what I DO know is that it's a pain to run Windows and install a project with node-gyp as a dependency. Some numbers: 403 questions on stackoverflow (node-gyp windows) 224 issues mentioning "windows" It's bizarre that a nodejs developer needs to install visual studio (even the ex

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert

Ok, here's the deal :) The foundation is considering an iteration on the official logo. This is not a re-design. The community loves hexagons, hexagons aren't going anywhere, but some people wouldn't mind a re-fresh of some of the assets. We'd also like more assets that we can use under certain size restrictions, for example twitter requires squared images while G+ rounds off an image and we have

Originally posted @ https://groups.google.com/forum/#!topic/nodejs-sec/fSNEQiuof6I Description and CVSS Score A bug exists in Node.js versions 4.0.0 to 4.1.1 whereby an external attacker can cause a denial of service. The severity of this issue is high (see CVSS scoring below) and users of the affected versions should plan to upgrade when a fix is made available. Versions 0.10 and 0.12 of Node.js

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert

Hi, One of the popular npm modules is node-ffi. We are using it in our code for several different calls, but one of them leads to assertion error in node 3.x or later. As the same code of the node-ffi is working fine with iojs 2.x, node 0.12.x and node 0.10.x and after discussion with node-ffi owners, I came to opening this issue. In our code we are trying to call methods from CoreFoundation.dll,

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert

This is ultimately up to @nodejs/tsc but for the sake of just getting it done I'm going to propose the way forward and will both tag this as tsc-agenda and ask that @nodejs/tsc members comment on this thread, particularly if they'd like to -1 anything I'm suggesting—otherwise let's roll with this. Our original aim was to get v4 out by the "end of August" so that we had a good 2 months of real-worl

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

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert

All the documentation for the Node Foundation is ready: TSC Charter (Basic Governance) Development Policy Convergence Plan Project Lifecyle (Working Groups Definition) WG Merger (List of working groups and how they will be merged) The gist of it is, the foundation's governance structure is nearly identical to io.js'. In fact, during the process of writing all this down we improved the documentatio

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert

Background There had been brief mention during a TC meeting some time back about the possibility of having a js HTTP parser for io.js core. I was looking for a new and interesting project to work on in my free time, and I'm a protocol enthusiast, so for the past week or so I've been working on writing a js HTTP parser. This parser uses regular expressions for most of the parsing. Others have expre