CI Enhancement: Integrate `npm run build` in Workflows

[SudiptaPaul-31]

📖 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.

[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

[mikevill20]

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

please maintainer, allow me work on this issue. thanks.

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

[drips-wave]

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

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

[mikevill20]

@SudiptaPaul-31 please can you close the issue since you have merged the PR so i can earn my point.

[Nacho1499]

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

hello. am emmanuel. a full-stack developer.

I would love to take on this task because automating build verification in CI/CD ensures code quality, reduces broken merges, and improves developer confidence—something I prioritize in every project I contribute to.

For this task, I’ll update the existing GitHub Actions workflow YAML (e.g., .github/workflows/ci.yml) to include a step that runs npm install, npm run lint, and npm run build. I’ll also configure caching with actions/cache for node_modules to speed up subsequent runs and ensure the workflow remains compatible with the project’s Node.js version.

This setup will automatically check that the project builds successfully on every pull request. If the build fails, the PR will be marked as failing, providing clear feedback to contributors and maintainers before merging.

If given the opportunity, I’ll deliver a robust CI workflow that catches build issues early, improves maintainability, and ensures consistent, production-ready code across all contributions.

thanks.

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