Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

update npm #1456

Closed
wants to merge 4 commits into from
Closed

update npm #1456

wants to merge 4 commits into from

Commits on Apr 17, 2015

  1. deps: fix git case sensitivity issue in npm 

    Remove Readme.md, as the subsequent npm update commit creates a
README.md. Combining the create and delete operations into the
same commit leads to OSX machines running into issues – they
don't detect it as a rename, instead trying to create a new
README.md, which fails because Readme.md hasn't been deleted yet.
This causes the entire operation to fail spectacularly. Thus,
the delete operation is performed first, in this commit, then
the create operation follows in the npm update commit.
    @chrisdickinson
    chrisdickinson committed Apr 17, 2015
    Configuration menu
    Copy the full SHA
    c8e8038 View commit details
    Browse the repository at this point in the history

  2. deps: upgrade npm to 2.8.3

    @othiym23 @chrisdickinson
    othiym23 authored and chrisdickinson committed Apr 17, 2015
    Configuration menu
    Copy the full SHA
    ec50bd0 View commit details
    Browse the repository at this point in the history

  3. deps: make node-gyp work with io.js 

    Every npm version bump requires a few patches to be floated on
node-gyp for io.js compatibility. These patches are found in
03d1992,
5de334c, and
da730c7. This commit squashes
them into a single commit.

PR-URL: #990
Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
    @cjihrig @chrisdickinson
    cjihrig authored and chrisdickinson committed Apr 17, 2015
    Configuration menu
    Copy the full SHA
    5c30354 View commit details
    Browse the repository at this point in the history

  4. win,node-gyp: optionally allow node.exe/iojs.exe to be renamed 

    On Windows, when node or io.js attempts to dynamically load a compiled
addon, the compiled addon tries to load node.exe or iojs.exe again -
depending on which import library the module used when it was linked.
This causes many compiled addons to break when node.exe or iojs.exe are
renamed, because when the binary has been renamed the addon DLL can't
find the (right) .exe file to load its imports from.

This patch gives compiled addon developers an option to overcome this
restriction by compiling a delay-load hook into their binary. The
delay-load hook ensures that whenever a module tries to load imports
from node.exe/iojs.exe, it'll just look at the process image, thereby
making the addon work regardless of what name the node/iojs binary has.

To enable this feature, the addon developer must set the
'win_delay_load_hook' option to 'true' in their binding.gyp file, like
this:

```
{
  'targets': [
    {
      'target_name': 'ernie',
      'win_delay_load_hook': 'true',
      ...
```

Bug: #751
Bug: #965
Upstream PR: nodejs/node-gyp#599

PR-URL: #1251
Reviewed-By: Rod Vagg <rod@vagg.org>

PR-URL: #1266
Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
    @piscisaureus @chrisdickinson
    piscisaureus authored and chrisdickinson committed Apr 17, 2015
    Configuration menu
    Copy the full SHA
    76fdec7 View commit details
    Browse the repository at this point in the history