[nodejs] Re: Private registry without full replication

This is the easiest to use thing I've found: https://github.com/terinjokes/docker-npmjs On Friday, October 11, 2013 4:31:21 PM UTC+2, Timothy Rupe wrote: > > I've been searching all over for a solution for this but always come > across unanswered questions, half-truths, and misinformation. I'm

[nodejs] Re: How do you send data with child_process in a "use strict" mode

The docs are broken; they are missing a `new` before `broadcast(i, message)`. Right now it just puts an `i` on the global scope in sloppy mode; strict mode prevents this error. On Thursday, October 10, 2013 2:15:16 PM UTC+2, Ket wrote: > > Hello, > > I try to send data with the child_process fu

[nodejs] Re: Async read handling for streams2

I don't see what the problem is? You don't have to call read() immediately; the bytes will still be there after your async processing is done. On Monday, July 1, 2013 9:23:44 AM UTC-4, Gil Pedersen wrote: > > Hi, > > I have a case where I want to consume a Readable, by: > > 1. Read n bytes. >

RE: [nodejs] Re: trying to wrap my head around "promises" - async vs Q

That's overstating it a bit. It's very easy to convert to promise-based code, e.g.: var fs = require('fs'); var Q = require('q'); var readFile = Q.denodeify(fs.readFile); var writeFile = Q.denodeify(fs.writeFile); readFile('src.txt').then(function (result) { writeFile('dest.txt', result); }).d

[nodejs] Re: Best practices for token-based authentication in REST API

OAuth 2 is definitely what you're looking for. In particular it looks like you want the Resource Owner Password Credentialsflow. If by chance you are using Restify, I made a thing that will automatically handle this for you: Restify–OAuth2

Re: [nodejs] Node.js documentation about domains: what makes "throw" special in JS compared to Python/Ruby?

On Thursday, April 4, 2013 11:40:54 PM UTC-4, Forrest L Norvell wrote: > > However, putting everything in try/catch/finally clauses is expensive > (i.e. they can't be fully optimized by V8). This is slightly misleading. In the following code: ```js try { doStuff(); } catch (e) { // handle

Re: [nodejs] Javascript Class Specification for the next generation of JS class system, hope to discuss with you.

This link reflects a no-longer-accepted proposal. The current thinking is more along these lines: http://wiki.ecmascript.org/doku.php?id=strawman:maximally_minimal_classes but even then, that is not fully accurate. You should check the specification drafts for actually-accurate information: ht

Re: [nodejs] convention for publishing modules requiring --harmony?

On Sunday, December 30, 2012 4:40:19 PM UTC-5, Rick Waldron wrote: > > On Sunday, December 30, 2012, Tristan Slominski wrote: > >> RE: "No one should use --harmony today anyway.." >> >> I didn't see block-scoped "let" in es6-shim (pretty sure that's >> impossible to shim without compilation, righ

[nodejs] Re: require() MODULE_NOT_FOUND - yet it does exist

I don't believe `require` works with absolute paths, like those generated by path.resolve. (Could be wrong.) If I'm correct, then you may find path.relative to be a useful method. Also note that of course path.resolve without a second argument will resolve relative to process.cwd(), not relativ

[nodejs] Re: Checking node_modules into git

For me checking in a npm-shrinkwrap.json gives all of the advantages of checking node_modules into git, with none of the drawbacks. That's my preferred solution. On Wednesday, December 26, 2012 7:05:45 PM UTC-5, José F. Romaniello wrote: > > Hi all, I have read few times that is better to checki

RE: [nodejs] Re: trying to wrap my head around "promises" - async vs Q

An interesting alternative is to use Q’s new “nodeify” function: function returnsPromiseOrCallsback(callback) { return Q.resolve(5).nodeify(callback); } If callback is a function, it will call callback(null, 5); otherwise it will return the promise for 5. Similarly it will pass rejection reaso

[nodejs] Re: [ANN] native html parser

you have > some tests / html examples that are tripping up the existing parser.. > > > On Friday, October 26, 2012 10:57:06 PM UTC+7, Domenic Denicola wrote: >> >> Very nice. As maintainer of jsdom, I've been looking for a replacement >> default HTML parser that could

[nodejs] Re: [ANN] native html parser

Very nice. As maintainer of jsdom, I've been looking for a replacement default HTML parser that could solve many of the parsing issues we've encountered. I'll put you on the shortlist. Thanks for announcing. On Friday, October 26, 2012 6:07:48 AM UTC-4, Dean Mao wrote: > > Hi All, > > I created

[nodejs] Re: node dev on windows

I summed up my experiences with writing and dealing with cross-platform Node code in this blog post: http://nodeblog.azurewebsites.net/how-to-write-portable-nodejs-code Mainly it deals with gotchas I encountered and has lots of links to pull requests I submitted to take care of them. On Friday

Re: [nodejs] Re: [ANN]: Deferred - Maintainable asynchronous JavaScript with promises

On Thursday, October 4, 2012 10:07:31 AM UTC+2, Mikeal Rogers wrote: > > I totally understand what you're saying but I think there are a few things > you're missing. > > The problem we had with errors in the node implementation of promises, > which was not great, was that errors were often unha

Re: [nodejs] Re: [ANN]: Deferred - Maintainable asynchronous JavaScript with promises

On Thursday, October 4, 2012 9:47:08 AM UTC+2, Mariusz Nowak wrote: > > > On Thursday, October 4, 2012 9:39:43 AM UTC+2, Domenic Denicola wrote: >> >> >> I would love to play nicely with domains, but I'm not sure it's as >> straightforward as this

Re: [nodejs] Re: [ANN]: Deferred - Maintainable asynchronous JavaScript with promises

On Thursday, October 4, 2012 7:55:50 AM UTC+2, Mikeal Rogers wrote: > > Domains work OOTB on all event emitters but have some complications with > callbacks and streams. > > Streams that are long running (like the redis client) don't get scoped to > the right domain since they are created early

Re: [nodejs] Re: [ANN]: Deferred - Maintainable asynchronous JavaScript with promises

On Tuesday, October 2, 2012 11:44:23 PM UTC-4, Raynos wrote: > > domains have a parallel to sync code. Use event emitters for your sync > flow. promises only have a parallel to sync code if you use promises for > sync & async code. > By "sync code" I meant code with functions that return values

[nodejs] Re: [ANN]: Deferred - Maintainable asynchronous JavaScript with promises

x27;t translate exceptions into rejections, this entire benefit is lost and you're back in traditional callback land, where an exception inside a callback jumps all the way back up to window.onerror. On Tuesday, October 2, 2012 10:18:42 PM UTC-4, Domenic Denicola wrote: > > j

[nodejs] Re: [ANN]: Deferred - Maintainable asynchronous JavaScript with promises

jQuery promises also aren't interoperable with other promise-consuming libraries, because they do not transform errors thrown in callbacks into rejection reasons, violating Promises/A. So e.g. function doOperationAndDontGiveUp(operation) { return operation().then(null, function (error) {

[nodejs] Re: [ANN]: Deferred - Maintainable asynchronous JavaScript with promises

; > > On Tuesday, October 2, 2012 3:32:13 PM UTC+2, Domenic Denicola wrote: >> >> >> >> On Monday, October 1, 2012 3:46:19 PM UTC-4, Mariusz Nowak wrote: >>> >>> >>> In Deferred I solved it by making end function with same signature as

[nodejs] Re: [ANN]: Deferred - Maintainable asynchronous JavaScript with promises

On Monday, October 1, 2012 3:46:19 PM UTC-4, Mariusz Nowak wrote: > > > In Deferred I solved it by making end function with same signature as then: > > promise.end(function (value) { >// do something with value > }); > > If onerror callback is not provided, eventual error will just throw. So

[nodejs] Re: Copy/Paste in node

Very cool; I'm a big fan of these kind of utilities. See e.g. https://github.com/domenic/opener A few points of constructive criticism: * Putting "node-" in the package name is generally bad practice. As a GitHub repo name it's fine, but in package.json it should be just "copy-paste" * Exposing

[nodejs] Re: Node x64 on Windows -- any advantages?

On Monday, August 6, 2012 6:03:59 AM UTC-4, mscdex wrote: > > On Aug 6, 5:30 am, Domenic Denicola > wrote: > > Sorry to necromance this thread, but any ideas on how to get VC++2010 > > Express to do x64 things? I think the Express version only works on x

Re: [nodejs] Re: Node x64 on Windows -- any advantages?

On Saturday, July 7, 2012 12:05:05 PM UTC-4, Nathan Rajlich wrote: > > The trick with native addons on Windows 64-bit node is that you have to > invoke npm/node-gyp from inside a 64-bit MSVC command prompt. There's a > shortcut to in in the start menu, but it's different than both the 32-bit > M

[nodejs] Re: Robust Error Handling

Promises are designed to be an exact async parallel of synchronous return values and exceptions, and so might be along the line of what you're looking for. See http://www.slideshare.net/domenicdenicola/callbacks-promises-and-coroutines-oh-my-the-evolution-of-asynchronicity-in-javascript (espec

Re: [nodejs] Re: How to count concurrent requests to my server?

Thank you! This is perfect. Still not sure exactly which events would be most accurate (maybe "connection" and the resulting socket's "close"?), but with this in hand I can just check the number of connections in a setInterval, which is good enough. On Wednesday, July 11, 2012 10:19:59 AM UTC-4

[nodejs] Re: How to count concurrent requests to my server?

. * HttpServerResponses emit "close" events to indicate "that the underlaying connection was terminated before response.end() was called or able to flush," which is not the case. That's as far as documentation goes. On Tuesday, July 10, 2012 6:48:00 PM UTC-4, mscde

[nodejs] How to count concurrent requests to my server?

I am trying to create a mini dashboard for my server that shows number of "unfinished requests." (BTW if there's a better term for that let me know.) Here is what I have, but I don't think it's catching all the response finishes: server.server.on("request", function (request, response) { up

[nodejs] Re: Version 0.8.2 (stable)

Could someone expand on the busy loop fixes? Are they "OMG I'd better deploy this" or are they very rare edge cases? On Monday, July 9, 2012 1:25:58 PM UTC-4, Isaac Schlueter wrote: > > 2012.07.09, Version 0.8.2 (Stable) > > * npm: Upgrade to 1.1.36 > > * readline: don't use Function#call() (Na

[nodejs] Re: Node x64 on Windows -- any advantages?

FWIW All the native modules I've tried fail to compile when using x64, so there's that as a *dis*advantage. On Saturday, July 7, 2012 12:53:49 AM UTC-4, Glenn Scott wrote: > > I see there's an x64 Node executable built for Windows: > http://nodejs.org/dist/v0.8.1/x64/node-v0.8.1-x64.msi > > A

[nodejs] Re: Doing asynchronous processing before piping HTTP requests

On Friday, June 29, 2012 5:23:47 AM UTC-4, mscdex wrote: > > > Your reference for calling req.pause() "useless" is a set of mailing > list posts from early last year and things have improved at least > somewhat since then. Since node 0.7.x (specifically [1]), there > shouldn't be any 'data' ev

[nodejs] Re: trying to wrap my head around "promises" - async vs Q

I'd like to submit my promises talk for consideration as well :). I agree with Mariusz that once you get it you will never go back. http://www.slideshare.net/domenicdenicola/callbacks-promises-and-coroutines-oh-my-the-evolution-of-asynchronicity-in-javascript On Sunday, July 1, 2012 2:55:05 PM U

[nodejs] Doing asynchronous processing before piping HTTP requests

The scenario I'm trying to solve is: * Get an incoming HTTP request stream * Look at the headers and use them to do some authorization logic, asynchronously * When that logic returns successfully, pipe the request stream to another stream * When that logic returns a failure, discard the incom

[nodejs] Re: ender vs. browserify?

On Friday, June 1, 2012 2:32:50 AM UTC-4, Diego Varese wrote: > > I have a question regarding these requirement bundlers above mentioned. Is > there one of these that will allow me to include the separate modules > during development while using require(), and then just concat-minify all > of

[nodejs] Tips for writing portable Node.js code

I have compiled a Gist detailing what I've learned, as a Windows developer, about writing cross-platform portable Node.js code: https://gist.github.com/2790533 Hopefully this is educational. I'd love any feedback you have to give. -- Job Board: http://jobs.nodejs.org/ Posting guidelines: http