Skip to content

Conversation

@satazor
Copy link
Contributor

@satazor satazor commented Feb 22, 2022

My manually testing done in #12 was wrong for some reason. This is the correct setup for the package.json.

pre-commit only runs scripts declared in scripts @ package.json.

@Americas
Copy link
Contributor

Is this still a breaking change?

@satazor satazor force-pushed the fix-lint-staged-readme branch from 76cf4d3 to 7ef196c Compare February 26, 2022 02:15
@satazor satazor force-pushed the fix-lint-staged-readme branch from 7ef196c to 66d0e97 Compare February 26, 2022 02:16
@satazor
Copy link
Contributor Author

satazor commented Feb 26, 2022

Hey folks! I've updated the PR to be more inline with what we had. I think we can release this as a patch release. Consumers will just need to update the package.json, which was wrong anyway as pre-commit expects a key mapped directly to scripts.. and lint-staged -q isn't a script..

However, if we merge #55 we will release a major anyway (minor actually because we are still < v1).

@satazor
Copy link
Contributor Author

satazor commented Feb 26, 2022

Once you got the time @diogotorres97 give it a test and review! 🙏

@satazor satazor changed the title Fix README instructions for lint-staged Fix lint-staged not working correctly Feb 27, 2022
Copy link
Contributor

@diogotorres97 diogotorres97 left a comment

Choose a reason for hiding this comment

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

LGTM. It seems to be working :trollface:

@diogotorres97 diogotorres97 merged commit 0cb0ed0 into master Mar 2, 2022
@diogotorres97 diogotorres97 deleted the fix-lint-staged-readme branch March 2, 2022 18:58
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.

5 participants