Node v0.6.3 (stable)
Bert Belder
* #2083 Land NPM in Node. It is included in packages/installers and
installed on `make install`.
* #2076 Add logos to windows installer.
* #1711 Correctly handle http requests without headers. (Ben
Noordhuis, Felix Geisendörfer)
* TLS: expose more openssl SSL context options and constants. (Ben
Noordhuis)
* #2177 Windows: don't kill UDP socket when a packet fails to reach
its destination. (Bert Belder)
* Windows: support paths longer than 260 characters. (Igor Zinkovsky)
* Windows: correctly resolve drive-relative paths. (Bert Belder)
* #2166 Don't leave file descriptor open after lchmod. (Isaac
Schlueter)
* #2084 Add OS X .pkg build script to make file.
* #2160 Documentation improvements. (Ben Noordhuis)
Source Code: http://nodejs.org/dist/v0.6.3/node-v0.6.3.tar.gz
Windows Installer: http://nodejs.org/dist/v0.6.3/node-v0.6.3.msi
Macintosh Installer: http://nodejs.org/dist/v0.6.3/node-v0.6.3.pkg
Website: http://nodejs.org/docs/v0.6.3/
Documentation: http://nodejs.org/docs/v0.6.3/api/
Diogo Resende
> 2011.11.25, Version 0.6.3 (stable)
>
> * #2083 Land NPM in Node. It is included in packages/installers and
> installed on `make install`.
OS-X? Linux? Windows? All?
---
Diogo R.
Ben Hughes
it often errors out:
npm ERR! System Windows_NT 6.1.7601
npm ERR! command "C:\\Program Files (x86)\\nodejs\\\\node.exe"
"C:\\Program Files (x86)\\nodejs\\node_modules\\npm\\bin\\npm-cli.js"
"help"
npm ERR! cwd C:\Program Files\Console2
npm ERR! node -v v0.6.3
npm ERR! npm -v 1.1.0-alpha-2
npm ERR! path C:\Program Files (x86)\nodejs\node_modules\npm\man\man1
npm ERR! code ENOENT
npm ERR! message ENOENT, no such file or directory 'C:\Program Files
(x86)\nodejs\node_modules\npm\man\man1'
However, npm install seems to work :D
Ben
> --
> Job Board: http://jobs.nodejs.org/
> Posting guidelines:
> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
> You received this message because you are subscribed to the Google
> Groups "nodejs" group.
> To post to this group, send email to nod...@googlegroups.com
> To unsubscribe from this group, send email to
> nodejs+un...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/nodejs?hl=en?hl=en
>
Egor Egorov
Bert Belder
That's not good. It seems we'll have to do a 0.6.4 soon.
Hyacinthus Chu
--
Job Board: http://jobs.nodejs.org/
Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to nod...@googlegroups.com
To unsubscribe from this group, send email to
Nicolas Chambrier
Diogo Resende
---
Diogo R.
On Fri, 25 Nov 2011 04:56:53 -0800 (PST), Egor Egorov wrote:
> $ ./configure
> $ make; sudo make install
> $ npm
> npm ERR! Error: ENOENT, no such file or directory
> '/usr/local/lib/node_modules/npm/man/man1/'
>
> npm ERR! Report this *entire* log at:
> npm ERR!
> npm ERR! or email it to:
> npm ERR!
> npm ERR!
> npm ERR! System Linux 3.0.0-12-virtual
> npm ERR! command "node" "/usr/local/bin/npm"
> npm ERR! cwd /home/egor/node-v0.6.3
> npm ERR! node -v v0.6.3
> npm ERR! npm -v 1.1.0-alpha-2
> npm ERR! path /usr/local/lib/node_modules/npm/man/man1/
> npm ERR! code ENOENT
> npm ERR! message ENOENT, no such file or directory
> '/usr/local/lib/node_modules/npm/man/man1/'
> npm ERR!
> npm ERR! Additional logging details can be found in:
> npm ERR! /home/egor/node-v0.6.3/npm-debug.log
> npm not ok
>
> Just a fresh ubuntu 11.04. npm was carefully removed before
> installing
> 0.6.3.
>
> --
> Job Board: http://jobs.nodejs.org/ [1]
> Posting guidelines:
> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
> [2]
> You received this message because you are subscribed to the Google
> Groups "nodejs" group.
> To post to this group, send email to nod...@googlegroups.com
> To unsubscribe from this group, send email to
> nodejs+un...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/nodejs?hl=en?hl=en [3]
>
>
> Links:
> ------
> [1] http://jobs.nodejs.org/
> [2]
> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
> [3] http://groups.google.com/group/nodejs?hl=en?hl=en
Sérgio Ramos
billywhizz
i happen not to like npm and am a bit bemused by it's inclusion in
core...
Diogo Resende
> if i don't want to use npm do i have the option of not installing it.
> i happen not to like npm and am a bit bemused by it's inclusion in
> core...
For me it's a blessing having npm included, although is really easy to
install (not sure on Windows). But I agree with you. For people
fetching
the source and compiling, a "make npm-install" might be a good idea.
---
Diogo R.
mscdex
> For me it's a blessing having npm included, although is really easy to
> install (not sure on Windows). But I agree with you. For people
> fetching
> the source and compiling, a "make npm-install" might be a good idea.
+1
billywhizz
Philipp Klose
install npm!
Liam
using it but haven't really had a need for it.
However I'm surprised this idea wasn't floated on the list first, and
was landed in a bug-fix update. Were there compelling reasons to do it
right this minute?
Marco Rogers
On Friday, November 25, 2011 1:11:00 PM UTC-8, Liam wrote:
I think I'm glad of being "forced" to try npm, as I gather I should be
using it but haven't really had a need for it.However I'm surprised this idea wasn't floated on the list first, and
was landed in a bug-fix update. Were there compelling reasons to do it
right this minute?
Ryan Breen
footprint if you opt not to use it.
Jake Verbaten
NPM will now be on all servers running node by default.
Martin Cooper
> Why would anyone have a problem with including npm? It's completely
> decoupled from node and doesn't change it at all. It's a tool that's
> available that you can use or not. Most people use and like it. There's no
> reason not to include it in a bug fix release because it doesn't introduce
> any meaningful change in node itself. npm is the defacto standard and
> recommended package manager for node. It makes sense to include it with
> node's "everything you need" install. Maybe it's a good idea to add a
> "without-npm" flag or something for people compiling from source who really
> don't want it.
For those of us who have a customised version of npm in use
internally, there is some additional risk of confusion when a version
comes built into Node, and that version doesn't have the same
functionality as the customised one. One more troubleshooting /
support step that I'd rather do without. I don't expect it will be a
big issue, but you did ask why. :-)
--
Martin Cooper
> :Marco
> On Friday, November 25, 2011 1:11:00 PM UTC-8, Liam wrote:
>>
>> I think I'm glad of being "forced" to try npm, as I gather I should be
>> using it but haven't really had a need for it.
>>
>> However I'm surprised this idea wasn't floated on the list first, and
>> was landed in a bug-fix update. Were there compelling reasons to do it
>> right this minute?
>>
>> On Nov 25, 8:51 am, billywhizz <apjo...@gmail.com> wrote:
>> > if i don't want to use npm do i have the option of not installing it.
>> > i happen not to like npm and am a bit bemused by it's inclusion in
>> > core...
>
> --
> Job Board: http://jobs.nodejs.org/
> Posting guidelines:
> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
Ryan Schmidt
On Nov 25, 2011, at 19:26, Marco Rogers wrote:
> Why would anyone have a problem with including npm?
I assume npm has its own release schedule, and that new versions of npm might be released independently of new versions of node. Speaking on behalf of the MacPorts package management system (and perhaps maintainers of other package management systems will have similar feelings), we have separate ports for node and npm, and if my independent release schedule theory is correct, then we should probably keep it that way. That means we need the node port to install only node, not also npm. We've patched the source for 0.6.3 to not install npm and would appreciate a flag or target we can use in the future to avoid having to do that.
Liam
On Nov 25, 5:26 pm, Marco Rogers <marco.rog...@gmail.com> wrote:
> There's no reason not to include it in a bug fix release
It's widely expected that significant new functionality in the package
will be announced before it lands, and that's good policy. The only
announcement I saw was a tweet referencing a commit, which I assumed
was to 0.7pre.
Ben Noordhuis
I can see why a 'no npm' install target is important to package
maintainers. We'll add it in the next release.
billywhizz
On Nov 26, 3:17 pm, Ben Noordhuis <i...@bnoordhuis.nl> wrote:
Brandon Benvie
On Friday, November 25, 2011 8:26:57 PM UTC-5, Marco Rogers wrote:
npm is the defacto standard and recommended package manager for node.