Node v0.5.4

2011.08.12, Version 0.5.4 (unstable)

  • libuv/Windows compatibility improvements
  • Build on Microsoft Visual Studio via GYP. Use generate-projects.bat in the to build sln files. (Peter Bright, Igor Zinkovsky)
  • Make Mikeal’s HTTP agent client the default. Use old HTTP client with --use-http1
  • Fixes https host header default port handling. (Mikeal Rogers)
  • #1440 strip byte order marker when loading *.js and *.json files (Ben Noordhuis)
  • #1434 Improve util.format() compatibility with browser. (Koichi Kobayashi)
  • Provide unchecked uint entry points for integer Buffer.read/writeInt methods. (Robert Mustacchi)
  • CMake improvements (Tom Huges)
  • Upgrade V8 to 3.5.4.

Download: http://nodejs.org/dist/v0.5.4/node-v0.5.4.tar.gz

Windows Executable: http://nodejs.org/dist/v0.5.4/node.exe

Website: http://nodejs.org/dist/v0.5.4/docs

Documentation: http://nodejs.org/dist/v0.5.4/docs/api

This entry was posted in Uncategorized. Bookmark the permalink.

8 Responses to Node v0.5.4

  1. Doug Finke says:

    Hello, I am running Windows 7 x86, downloaded python 2.7, using VS 2010. I run gen proj bat and get the below. I can open the sln but the project does not build.

    What’s the best way to communicate the errors? Should I wait for the next drop?

    Thank you

    [‘-f’, ‘msvs’, ‘-G’, ‘msvs_version=2010’, ‘-D’, ‘msvs_multi_core_compile=true’, ‘.\\node.gyp’, ‘–depth=.’, ‘-Dtarget_ar
    ch=ia32’, ‘-Dcomponent=static_library’, ‘-Dlibrary=static_library’]
    {}
    Warning: unrecognized setting VCCLCompilerTool/MultiProcessorCompilation while converting to MSBuild.
    Warning: unrecognized setting VCCLCompilerTool/MultiProcessorCompilation while converting to MSBuild.
    Warning: Missing input file deps\v8\tools\gyp\..\..\src\codegen-inl.h
    Warning: unrecognized setting VCCLCompilerTool/MultiProcessorCompilation while converting to MSBuild.
    Warning: unrecognized setting VCCLCompilerTool/MultiProcessorCompilation while converting to MSBuild.

  2. Peter Bright says:

    Hi Doug,

    Those warnings are harmless; they’re on my list to fix but they won’t break anything.

    The fact that you can’t build is more significant; I fear a change must have been made since I last verified that a virginal checkout and project generation works properly. What’s happening? Compiler errors, linker errors, or something else entirely?

  3. Doug Finke says:

    Here is a copy/paste from my VS IDE
    http://pastebin.com/JSU1mxaY

  4. Peter Bright says:

    Ah yes, I see the problem. Updating the V8 version reverted a modification made to the V8 gyp files. I guess this is going to happen often, so perhaps we’ll have to find a more elegant way of calling the V8 gyp files.

  5. Peter Bright says:

    OK, the current master should now be working fine.

  6. Doug Finke says:

    Thanks Peter, downloaded the master branch and it all works.

  7. Doug Finke says:

    Hey Peter, I am looking to spin up PowerShell from nodejs. I was going to investigate the cmd.exe currently implemented. Any suggestions or warnings?

    Thanks
    Doug

    • Peter Bright says:

      I’m not sure. The two main functions I guess are child_process.spawn and child_process.exec; the latter calls the former with certain pre-defined arguments.

      If you don’t need to pass any arguments to it (and I don’t think you should, the standard Windows shortcut just invokes %SystemRoot%\system32\WindowsPowerShell\v1.0\powershell.exe) then simply spawning it should be the better option.

      If you do need to pass arguments to it, you might find that spawn acts a little more predictably. spawn does in effect a “cmd /c “.

      I’m also not sure how reliable I/O redirection will be between parent and child, so there may be some stumbling blocks there.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s