-
Notifications
You must be signed in to change notification settings - Fork 122
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
Issue #464: Replaces Grunt with NPM scripts #659
Conversation
wow @jakeclements this is an amazing work! Give us some time to review but I just wanted to start saying thank you for this! |
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.
This LGTM. We are in the process of merging a couple of urgent PRs, but let's merge this as soon as possible after those.
Thanks for the review @matteofigus, say the word once your PRs are in and I'll merge this. |
Wohoo, super excited for this. |
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.
👍
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.
@jakeclements I did a final review for merging but found just 2 little things. Can you have a look, if you can work on those it would be nice, if not I can still merge it and we can make the changes in subsequent PRs. Thanks and sorry for taking long for reviewing 😢
CONTRIBUTING.md
Outdated
@@ -24,11 +24,11 @@ You need to be enabled for doing this. | |||
* `master` should be all green. If not, make it green first. | |||
* git checkout master | |||
* git pull --tags | |||
* Run `grunt version:<versionType>` for new version. | |||
* Run `npm run version -- --type="<versionType>"` for new version. |
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.
I was thinking that for the sake of simplicity, we could simplify this by having npm run patch
, npm run minor
and npm run major
? What do you think
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.
I agree, the current script is unnecessarily verbose.
I'm happy to update this so we can keep it within a single PR.
package-lock.json
Outdated
@@ -0,0 +1,11339 @@ | |||
{ |
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.
We gitignored the package-lock in master, can you sync with that so we can remove this?
@matteofigus thanks for the review, no problem about the timeframe. |
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.
💣 💥 Thanks!!!
Welcome to the contributors! 👍 |
Fixes #464