Make loopback-datasource-juggler a peer dep

[raymondfeng]

/to @ritch

[ritch]

lgtm

[slnode]

Test FAILed. To trigger a build add comment - ".test\W+please"
Refer to this link for build results: http://ci.strongloop.com/job/loopback/465/

[bajtos]

@raymondfeng @ritch do you remember why was this change made?

Quoting from strongloop/loopback-workspace#28:

peerDependencies are meant to control versions of peer dependencies more than control that they are actually installed.

In other words, we are sort of saying "you can depend on loopback only if you depend directly on loopback-datasource-juggler too".

[rmg]

Installation does seem to be part of the deal according to the peerDependecies announcement blog post, but there doesn't seem to be any docs for it.

Another thing to consider is that loopback does require() loopback-datasource-juggler directly, which makes me question if it this is close enough to the plugin style of relationship that peerDependencies is meant to address.

This also breaks npm-link, if I recall correctly.

[raymondfeng]

Here is the user experience leads to the peerDependencies:

1. You create a loopback project using 'slc lb project' command. The package.json declares 'loopback' as the dependency.
2. Run 'npm install loopback-connector-mongodb --save' to add mongo support. (Connectors are plugins).

Before peerDependency is adopted, we end up with the following tree:

myapp --> loopback --> loopback-datasource-juggler
--> loopback-connector-mongodb --> loopback-datasource-juggler

With peerDependency, now we have:

myapp --> loopback
myapp --> loopback-datasource-juggler ('npm install' adds this peer at the same level as loopback)
myapp --> loopback-connector-mongodb

[rmg]

Ah, and it was added as a devDependency to get around the fact that loopback-datasource-juggler won't be installed within loopback if you run npm install from a checkout.

In that case it makes sense to use the same technique in loopback-workspace.

[raymondfeng]

Yes, exactly.

[innerdaze]

I don't know if this is new information for you, but running npm install loopback on the latest version fails unless you have explicitly npm installed loopback-datasource-juggler.

Adding loopback-datasource-juggler as a devDependency to loopback currently isn't forcing npm to download loopback-datasource-juggler so the install fails.

Are we convinced the peerDependencies are a stable npm feature?

[raymondfeng]

Thank you for bringing it to our attention.

1. The loopback module is typically used as a dependency to your application. In that case, npm install should work.
2. npm install -g will install the peer dependencies.

If you just run ‘npm install loopback’ in a directory that doesn’t have package.json with loopback as a dependency, it will fail.

Raymond

On Feb 14, 2014, at 1:48 AM, lsdriscoll [email protected] wrote:

I don't know if this is new information for you, but running npm install loopback on the latest version fails unless you have explicitly npm installed loopback-datasource-juggler.

Adding loopback-datasource-juggler as a devDependency to loopback currently isn't forcing npm to download loopback-datasource-juggler so the install fails.

Are we convinced the peerDependencies are a stable npm feature?

—
Reply to this email directly or view it on GitHub.

[rmg]

Interesting.

I just did npm install loopback in a clean directory with a fresh package.json (npm init, all defaults) and it installed both loopback and loopback-datasource-juggler without complaint. Running npm ls warns that [email protected] is extraneous.

If I do the same thing, but do npm install --save loopback, both loopback and loopback-datasource-juggler are added to dependencies.

I cleared the cache with npm cache clean both times and I'm using [email protected] and [email protected].

[ritch]

@lsdriscoll - what version of npm / node are you using?

Hint:

npm -v
node -v

[innerdaze]

@ritch - Apologies for the late reply, left my phone at work all weekend -_-
npm: 1.3.14
node: 0.10.22