Skip to content

[Backend] Add a non-mutating lint:check script (npm run lint uses --fix) #1401

Closed

Description

@BigBen-7

Found in a repository audit of main (b472e6b). The facts below were checked against that commit.

Problem

Backend/package.json defines lint as eslint "{src,apps,libs,test}/**/*.ts" --fix. It rewrites files, which makes it unsuitable as a CI gate and surprising in hooks.

Fix

Add lint:check (same glob, no --fix) and keep lint for local fixing. Document both in the README scripts table.

Acceptance criteria

  • npm run lint:check exits non-zero on lint errors without modifying files
  • README scripts table lists it

Notes

Scope: Light (about half a day or less). Location: Backend/package.json.

Activity

  1. ranjeet150 commented on Oct 14, 2026

    @ranjeet150

    Hello,

    I am interested in taking up "[Backend] Add a non-mutating lint:check script (npm run lint uses --fix)" and implementing a production-grade solution.

    Technical Implementation Outline:

    1. Inspect package manifest (package.json), peer dependency declarations, and module resolution.
    2. Configure explicit peer/optional dependencies and alignment to prevent missing runtime modules.
    3. Verify package lockfile generation and run isolated installation with zero manual steps.
    4. Validate full package build, typecheck, and runtime initialization succeed without errors.

    Please assign this issue to me. I will submit a clean, well-tested, and production-ready PR promptly!

  2. Glittersup commented on Oct 15, 2026

    @Glittersup

    @Glittersup has applied to work on this issue as part of the Stellar Wave Program's 10th wave.

    Hello! I’d be glad to work on this. The issue presents a good opportunity to improve the project, and I’m confident I can deliver the requested functionality while keeping the existing behavior intact. I’ll validate everything before opening the PR.

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @Glittersup to this issue.

  3. GiftedGiftB commented on Oct 15, 2026

    @GiftedGiftB

    @GiftedGiftB has applied to work on this issue as part of the Stellar Wave Program's 10th wave.

    I can get this work done in less than 24 hours.

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @GiftedGiftB to this issue.

  4. victrexfx commented on Oct 15, 2026

    @victrexfx

    @victrexfx has applied to work on this issue as part of the Stellar Wave Program's 10th wave.

    Hello team! I've already mapped out the fastest route to resolving this issue without cutting corners. Let me know if I can start. Thank you

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @victrexfx to this issue.

  5. Niffy03 commented on Oct 15, 2026

    @Niffy03

    @Niffy03 has applied to work on this issue as part of the Stellar Wave Program's 10th wave.

    Hi there, I'd like to work on this.

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @Niffy03 to this issue.

  6. NteinPrecious commented on Oct 15, 2026

    @NteinPrecious
    Contributor

    @NteinPrecious has applied to work on this issue as part of the Stellar Wave Program's 10th wave.

    Hello, I'm interested in taking this issue on.

    I'm a software engineer with strong experience in JavaScript and building scalable web applications. I'm comfortable working across the stack, writing clean, maintainable code, and collaborating in open source environments.

    I've reviewed the issue and I'm confident I can implement a solid solution while following the project's conventions.

    I'd appreciate being assigned to this issue and look forward to contributing.

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @NteinPrecious to this issue.

  7. Phunkey12 commented on Oct 15, 2026

    @Phunkey12

    @Phunkey12 has applied to work on this issue as part of the Stellar Wave Program's 10th wave.

    Hello Maintainer,

    I've carefully reviewed the issue and would like to take the initiative to work on it. My goal is to identify the root cause and implement a robust, maintainable solution that follows the project's existing architecture and coding standards.

    I’ll ensure the implementation is well-structured, handle relevant edge cases, and run the necessary tests to verify that the changes work as expected without affecting existing functionality.

    I'm committed to delivering a high-quality contribution and maintaining clear communication throughout the process. I'd appreciate the opportunity to work on this issue and submit a thoroughly tested pull request for review.

    Thank you for your time and consideration. I look forward to contributing to the project.

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @Phunkey12 to this issue.

  8. drips-wave commented on Oct 15, 2026

    @drips-wave

    Congratulations, @NteinPrecious! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on October 22, 2026.

    🧑‍💻 @NteinPrecious: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

    Warning

    When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

    🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

    🌊 Happy Wave 🌊

  9. grantfox-oss commented on Oct 15, 2026

    @grantfox-oss

    🎉 This issue has been marked as completed on GrantFox!

    @NteinPrecious's PR #1515 was approved and merged by @BigBen-7.

    🏆 @NteinPrecious: You earned 40 FoxPoints for this contribution! Your current tier: Builder (2,268 total points). Track your full progress on GrantFox.

    👏 Great work, @NteinPrecious! Keep contributing to PinSpace-Org.

  10. drips-wave commented on Oct 15, 2026

    @drips-wave

    This issue has been completed by @NteinPrecious as part of the Stellar Wave Program's 10th Wave 🥳

    😎 @NteinPrecious: You earned 200 Points for completing this issue! Once the Wave's rewards are finalized, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

    🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

BackendBackend issuesStellar WaveIssues in the Stellar wave programci-cdCI/CD pipelinesgood first issueGood for newcomers

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions