Who it is forA contributor or coding agent who has changed loader code in the public repo and needs to confirm it passes before review.
The problemA change can break tests, lint rules, or the published package contents, and reviewers will reject it without these checks.
The outcomeThe contributor gets a clean test run, lint result, and package dry-run output ready to attach to a pull request.
What you need first
- Node.js and npm to install the package
- A React app using React 18 or newer
- A streaming or pending response source, such as a fetch endpoint, for the text and status cases
Steps
- Run
npm installin the cloned repository. - Run
npm testand fix any failing tests. - Run
npm run lintand fix any reported issues. - Run
npm pack --workspace generative-loaders --dry-runto check the package contents. - Read CONTRIBUTING.md in the repo for the full workflow, then open the pull request.
Prompt for your agent
In the kasturibuilds/generative-loaders repository, run npm install, npm test, npm run lint, and npm pack --workspace generative-loaders --dry-run after my change to <file-or-component>. Expected output: a pass or fail summary for each command with any error messages. Verify that all three commands exit with no errors before suggesting a pull request.
Caveat. The README says the live website is maintained separately, so the checks cover only the public npm package source in this repository.
Use this in your AI agent
Ask your agent
Using the Deduped MCP, get the setup steps for kasturibuilds/generative-loaders and "Run the package checks before opening a pull request"
Add Deduped to Claude Code once
claude mcp add --transport http deduped https://dedupedai.com/mcp
Every Monday: the 5 hottest repos and exactly how to use them. Free, one email a week, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer