[GH-ISSUE #546] Add a lint staged task for package.json changes #143

Closed
opened 2026-02-26 18:45:33 +03:00 by kerem · 4 comments
Owner

Originally created by @Mythie on GitHub (Oct 9, 2023).
Original GitHub issue: https://github.com/documenso/documenso/issues/546

Originally assigned to: @adityadeshlahre on GitHub.

Improvement Description

Add a lint-staged task that identifies if any package.json files have been modified and then runs npm install to ensure we always have the latest package.json file.

Rationale

Whenever I encounter an issue I like to try and solve it for good so we don't have to worry about it again. As per #523 we accidentally forgot to commit the package-lock file and thus caused CI failures, could have happened to anyone so we should try and alleviate the burden of remembering such a mundane thing.

Proposed Solution

Create the lint staged task as per above

Alternatives (optional)

N/A

Additional Context

N/A

Checklist

  • I have searched the existing issues and improvement suggestions to avoid duplication.
  • I have provided a clear description of the improvement being suggested.
  • I have explained the rationale behind this improvement.
  • I have included any relevant technical details or design suggestions.
  • I understand that this is a suggestion and that there is no guarantee of implementation.
Originally created by @Mythie on GitHub (Oct 9, 2023). Original GitHub issue: https://github.com/documenso/documenso/issues/546 Originally assigned to: @adityadeshlahre on GitHub. ## Improvement Description Add a lint-staged task that identifies if any `package.json` files have been modified and then runs `npm install` to ensure we always have the latest package.json file. ## Rationale Whenever I encounter an issue I like to try and solve it for good so we don't have to worry about it again. As per #523 we accidentally forgot to commit the package-lock file and thus caused CI failures, could have happened to anyone so we should try and alleviate the burden of remembering such a mundane thing. ## Proposed Solution Create the lint staged task as per above ## Alternatives (optional) N/A ## Additional Context N/A ## Checklist - [x] I have searched the existing issues and improvement suggestions to avoid duplication. - [x] I have provided a clear description of the improvement being suggested. - [x] I have explained the rationale behind this improvement. - [x] I have included any relevant technical details or design suggestions. - [x] I understand that this is a suggestion and that there is no guarantee of implementation.
Author
Owner

@adityadeshlahre commented on GitHub (Oct 9, 2023):

i would love to work on this issue! 😄
if its going to get public tag !

<!-- gh-comment-id:1752621018 --> @adityadeshlahre commented on GitHub (Oct 9, 2023): i would love to work on this issue! :smile: if its going to get public tag !
Author
Owner

@Mythie commented on GitHub (Oct 9, 2023):

Sounds great!

<!-- gh-comment-id:1752796001 --> @Mythie commented on GitHub (Oct 9, 2023): Sounds great!
Author
Owner

@github-actions[bot] commented on GitHub (Dec 8, 2023):

This issue has not seen activity for a while. It will be closed in 30 days unless further activity is detected

<!-- gh-comment-id:1847447842 --> @github-actions[bot] commented on GitHub (Dec 8, 2023): This issue has not seen activity for a while. It will be closed in 30 days unless further activity is detected
Author
Owner

@github-actions[bot] commented on GitHub (Dec 16, 2023):

This issue has been closed because of inactivity.

<!-- gh-comment-id:1858625032 --> @github-actions[bot] commented on GitHub (Dec 16, 2023): This issue has been closed because of inactivity.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/documenso#143
No description provided.