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

Publish to NPM #10

Open
mike183 opened this issue Oct 24, 2017 · 5 comments
Open

Publish to NPM #10

mike183 opened this issue Oct 24, 2017 · 5 comments

Comments

@mike183
Copy link
Contributor

mike183 commented Oct 24, 2017

Are there any updates on when this will be published to the NPM registry?

cc/ @rwjblue @trentmwillis

@trentmwillis
Copy link
Member

Does it need to be published? I thought the blueprint functionality from ember-cli could pull from the repo

@rwjblue
Copy link
Member

rwjblue commented Oct 25, 2017

Yep, it can, but it’s a bit nicer to say ember new my-engine -b @ember-engines/blueprint vs ember new my-engine -b [email protected]:ember-engines/engine-blueprint.git...

@mike183
Copy link
Contributor Author

mike183 commented Oct 25, 2017

As @rwjblue said, its easier to type ember new my-engine -b @ember-engines/blueprint.

In addition, I'd also say that it was easier to type from memory.

@trentmwillis
Copy link
Member

Ah, I assumed there would be a shorthand for GitHub lookups. Also, I think I’m lazy and just plan on copy-pasting no matter which route is chosen 😛

@mike183
Copy link
Contributor Author

mike183 commented Oct 25, 2017

Is there anything blocking it being published? Or is it just a case of whoever has permission publishing it?

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

3 participants