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

Mystery: why do we publish to NPM? #1079

Closed
chancancode opened this issue Nov 13, 2019 · 2 comments
Closed

Mystery: why do we publish to NPM? #1079

chancancode opened this issue Nov 13, 2019 · 2 comments

Comments

@chancancode
Copy link
Member

We currently publish an ember-inspector package on NPM: https://www.npmjs.com/package/ember-inspector

It has all the source files in this repository, as well as the built output in dist.

Does anyone know why we publish this? Do you rely on this build in your team? Please let me know!

@RobbieTheWagner
Copy link
Member

@chancancode according to npm, the dependents are ember-electron and ember-remote-inspector. I suppose the use case is less for apps and more for installing into complex addons. For instance, ember-electron uses it to inject inspector into the DevTools in electron.

@chancancode
Copy link
Member Author

Aha! Thank you! I’ll check those to make sure any tweaks I make to the build won’t break them!

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

2 participants