-
-
Notifications
You must be signed in to change notification settings - Fork 318
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
Run npm install
in post-merge hook
#1445
Conversation
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.
You may also want to run mix
then: https://laravel.com/docs/8.x/mix#running-mix
But don't we include the compiled JS file already in the Git repo? |
But then what is the point of |
It updates the JS dependencies in |
In that case, I'd suggest both or neither. I'd lean towards neither, especially as we're not really using livewire yet. |
The more I think of it, the more unsure I am as we commit the JS and css files. As a result we do not need to compile them each times. |
Total agreement. I don't like adding development dependencies to the main line. But it is up to you, @ildyria, you approved this PR. If you are getting second thoughts, then you should revoke the approval. I am not a big fan of this PR. I have already asked in #1440 (comment) why we need NPM at all, because I have never needed it before. |
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.
Make this "optional" in other words, do not fail if npm
is not available.
@ildyria it now only runs if npm is available. |
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.
LGTM
To update JS dependencies just like Composer dependencies. Only runs in dev mode.