[Feature]: CI Enhancement: Integrate `npm run build` in Workflows

[SudiptaPaul-31]

🔍 Problem Statement

📖 Description

Add npm run build as part of the GitHub Actions workflow to ensure that every pull request is automatically checked for build success. This will help contributors and maintainers quickly identify build failures before merging.

Expected Behavior

• On every PR, GitHub Actions should run npm run build.
• If the build fails, the workflow should mark the PR as failing.
• Contributors and maintainers can immediately see build status in the PR checks.

🛠 Technical Notes

• Update existing workflow YAML file (e.g., .github/workflows/ci.yml).
• Add a step to run npm install, npm run lint, and npm run build.
• Ensure caching is configured for faster builds (e.g., actions/cache for node_modules).
• Keep workflow compatible with current Node.js version used in the project.

✅ Verification

• Opening a PR triggers the workflow and runs npm run build.
• Successful builds show ✅ in PR checks.
• Failed builds show ❌ in PR checks with error logs.
• Maintainers can block merging until build passes.

📈 Expected Impact

High — Would significantly improve user experience

[drips-wave]

This issue has been added to the Stellar Wave Program and is worth 100 Points.

🧑‍💻 Interested in contributing? Apply to work on this issue on Drips Wave, earn points, and receive rewards.

Warning

Only applications submitted via the apply link above will be considered. Please do not apply by commenting on the issue or opening a PR directly.

🤠 Repo maintainers: You can manage this issue's Points and Complexity on your Maintainer Dashboard here. Please keep an eye on applications and respond quickly 💙

ℹ️ Learn more about Drips Wave

[SamixYasuke]

@SamixYasuke has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

Hi, I'd like to handle this, I have experience with github workflows

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

[walterthesmart]

@walterthesmart has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

Hi @SudiptaPaul-31, I would like to work on this issue.

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

[Nacho1499]

@Nacho1499 has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

hello maintainer, am emmanuel. a full-stack developer. please assign this issue to me. i can handle it. thanks

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

[drips-wave]

Congratulations, @Nacho1499! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on February 26, 2026.

🧑‍💻 @Nacho1499: 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 issued 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 🌊

[drips-wave]

This issue has been completed by @Nacho1499 as part of the Stellar Wave Program's 2nd Wave 🥳

😎 @Nacho1499: You earned 100 Points for completing this issue! After the current Wave ends, 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.