Skip to content
This repository has been archived by the owner on Aug 11, 2021. It is now read-only.

feat: install addon from URL rather than npm module #21

Merged
merged 4 commits into from
May 12, 2016
Merged

Conversation

bcoe
Copy link
Contributor

@bcoe bcoe commented May 12, 2016

  1. this makes it easier for other on-prem products to integrate with npm Enteprise (since they can generate meta-information specific to their addon).
  2. I received feedback that forcing people to publish a module for their addon feels weird.
  3. It cuts off the discussion about what scopes should be used for addons at the pass.

@coveralls
Copy link

Coverage Status

Changes Unknown when pulling f84f1df on on-prem-addons into * on master*.

@bcoe bcoe merged commit 54e959e into master May 12, 2016
}, function (err, res, meta) {
if (err) return deferred.reject(err)
if (res.statusCode >= 400) {
var msg = figures.cross + ' could not find addon "' + argv.addon + '" in registry ' + argv.registry
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This error message seems a little off since we're not using a registry here.

@nexdrew nexdrew deleted the on-prem-addons branch May 12, 2016 14:04
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants