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

Prepare for publishing. #2247

Closed
wants to merge 1 commit into from
Closed

Conversation

rwjblue
Copy link
Member

@rwjblue rwjblue commented Sep 7, 2014

  • Move bower install into prepublish. This prevents consumers of the new published ember-data package from having bower installed globally. Also, nothing changes as far as setup requirements: running npm install in the root of the repo runs the prepublish script.
  • Only publish the specific files that we want (leaves ability in the future to publish other types of things).

* Move `bower install` into `prepublish`.  This prevents consumers of
  the new published `ember-data` package from having `bower` installed
  globally. Also, nothing changes as far as setup requirements: running
  `npm install` in the root of the repo runs the `prepublish` script.
* Only publish the specific files that we want (leaves ability in the
  future to publish other types of things).
"scripts": {
"postinstall": "bower install",
"prepublish": "ember build --output-path=dist/ember-data/ --environment production",
"prepublish": "bower install && rm -rf dist/ && ember build --output-path=dist/ember-data/ --environment production && rm -rf dist/ember-data/bower_components dist/ember-data/docs",
Copy link
Contributor

Choose a reason for hiding this comment

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

@rwjblue I goofed and forgot an equals sign on that --environment=production. Can you fix?

Copy link
Contributor

Choose a reason for hiding this comment

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

Looks like it was like that before.

"dist": "rm -rf dist && ember build --environment production",

Guess it doesn't matter..

Copy link
Member Author

Choose a reason for hiding this comment

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

Yup, our options parsing doesn't care if it has an equals or not, both are perfectly valid.

@jayphelps jayphelps mentioned this pull request Sep 7, 2014
2 tasks
@rwjblue
Copy link
Member Author

rwjblue commented Sep 8, 2014

Superseded by #2249

@rwjblue rwjblue closed this Sep 8, 2014
@rwjblue rwjblue deleted the package-json-updates branch May 1, 2019 20:29
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

Successfully merging this pull request may close these issues.

2 participants