search

jspm / registry

The jspm registry and package.json override service
https://jspm.io
229 stars 256 forks source link

dependency install skipped because it does not use overrides #953

Open nelisbijl opened 7 years ago

nelisbijl commented 7 years ago

I have package A that has dependency B for which an override has been defined and stored in A's package.json

Now when I install package A in application C, I get an error stating:

dependency installs skipped as it's a GitHub package with no registry property set. If the dependencies aren't needed ignore this message. Alternatively set a registry or dependencies override or use the npm registry version at jspm install npm:B@^0.0.1 instead.

Why are the overrides in A's package.json ignored?

guybedford commented 7 years ago

Because overrides are not read from packages being installed for the reason of compatibility. Try sending a PR to the jspm registry with your override or forking the jspm registry locally if this is a private package. The registry is the primary override sharing mechanism. On Thu, 11 Aug 2016 at 11:34, nelisbijl notifications@github.com wrote:

I have package A that has dependency B for which an override has been defined and stored in A's package.json

Now when I install package A in application C, I get an error stating:

dependency installs skipped as it's a GitHub package with no registry property set. If the dependencies aren't needed ignore this message. Alternatively set a registry or dependencies override or use the npm registry version at jspm install npm:B@^0.0.1 instead.

Why are the overrides in A's package.json ignored?

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/jspm/registry/issues/953, or mute the thread https://github.com/notifications/unsubscribe-auth/AAkiymQsJQ6qeZu3Wzh5NvHeGarsz-LJks5qeuykgaJpZM4Jh8kF .