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.

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

Pass-through to npmjs #403

Open
dandv opened this issue Aug 9, 2015 · 1 comment
Open

Pass-through to npmjs #403

dandv opened this issue Aug 9, 2015 · 1 comment

Comments

@dandv
Copy link

dandv commented Aug 9, 2015

Meteor 1.3 update

Now that Meteor can use npm packages directly, I'd like to resurrect the dialog on adding discoverability of non-Atmosphere packages through the Atmosphere interface.

If a developer searches for package X that hasn't been specifically wrapped for Meteor, they will find nothing, or even worse, false positives. Hopefully, the developer will think of re-doing their search on npmjs. What if Atmosphere displayed matching results from npmjs underneath regular results? The ranking would rely on the npmjs ratings and download metrics, and this would convey the fact that the Meteor ecosystems comprises the 250,000 packages from npm.

If Atmosphere doesn't include npm results, there is an additional risk: once legitimate wrappers are pulled now that they're no longer necessary, old unmaintained wrappers will remain on Atmosphere, adding to the clutter without any advantage to the developer.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant