use enderDependencies instead of dependencies if exists

[coolaj86]

In the case where ender's dependencies are not the same as node's dependencies (node has events built-in, node doesn't. The browser has localStorage built in, node doesn't) there should be alternate dependency list.

https://groups.google.com/d/msg/npm-/0Z5hE-41Rpc/iOKJ9x4jzJ8J

Also, there should be a way to provide one package AS another. I.E. it should be possible to provide events.node AS events, etc.

[fat]

you could do the latter i believe by just doing:

provide("events", events.node);

[fat]

We've been planning on extending the current ender key to an object (rather than just a path to the ender bridge)... so in a given package.json you would see something like this (optionally):

{
  "name": "foo"
  ...
  "ender": {
    "bridge": "./path/to/bridge",
    "dependencies": {
      "future": ">= 2.1.0"
    }
  }
}

[coolaj86]

Second: I think that will work well if { ender: dependencies: {}} overrides the regular dependencies entirely.

First: I think you're right, but I'd rather be able to specific the name the module should provide in the package.json since that seems to be a generally better place for it.

Thanks for your responses. :-D

[fat]

I agree that if an ender specific dependency definition was present, it should be used entirely instead of a regular dependency mapping... hopefully we'll start working on this next, because i think we could do lots of cool stuff here and it shouldn't hopefully be too hard to add.

To the alternate name thing -- i see what you mean -- i suppose we could add that to the ender key as well? Do you see any problem with that? It could get sort of confusing perhaps because you wouldn't be able to reference it by that name when actually building with the Ender cli.

[coolaj86]

As per the CommonJS 1.1 spec, there's a formal way to handle this:

package.json.overlay.ender.dependencies

http://wiki.commonjs.org/wiki/Packages/1.1

[ded]

@coolaj86 ah! that's a good find

[ded]

not that we haven't seen that page before... but it's an easy thing to miss or gloss over

[coolaj86]

I don't think that npm or node honor overlays though - despite that they're in the examples on the wiki.

I've got at least one comment from Isaac on the mailing list saying that he used to, but dropped it due to confusion that it caused, so an extension may still be in order.

[coolaj86]

This is fixed in http://github.com/coolaj86/node-pakman and http://github.com/coolaj86/node-pakmanager I decided to use browserDependencies

[coolaj86]

Also, dependencies are added and removed by editing package.json

[vic]

Well, it seems a lot of the ender issues are related to taking dependencies from a json file. I've sent the following pull request:

#125

[rvagg]

ref #131