-
Notifications
You must be signed in to change notification settings - Fork 205
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
Expose a rake task to npm install
#59
Conversation
Assumes that the `package.json` includes: ```json "tasks": { "postinstall": "bower install" } ``` So that we only depend on a global `npm` installation (not `npm` and `bower`)
@seanpdoyle This looks really promising. I'm going to test this today or tomorrow and talk to @rwz about it. /cc @rwz |
Great! I really dislike the fact that you need to depend on |
@@ -25,10 +25,18 @@ def non_production? | |||
!Rails.env.production? && Rails.configuration.consider_all_requests_local | |||
end | |||
|
|||
def inject_install_dependencies_task! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could we move the definition if this task into a separate file? Kind if like the way it's described here
Looks good to me! |
👍 |
* Extract task definition into `.rake` file according to http://blog.nathanhumbert.com/2010/02/rails-3-loading-rake-tasks-from-gem.html * invoke `npm` with `Helpers.which`
Expose a rake task to `npm install`
Yay! Now I guess we need to describe this process in README somehow. |
Thanks for PR @seanpdoyle |
@seanpdoyle Yeah, thanks! 🍻 |
Assumes either:
bower
is a globally accessible commandpackage.json
includes:Corresponds to #33