chore(sdk): prepare package for npm publishing#36
Conversation
Abdulmuiz44
commented
May 31, 2026
Abdulmuiz44
commented
- Prepares @cliploop/sdk package metadata, build output, exports, and npm files.
- Adds publish-readiness scripts and dry-run packaging checks.
- Does not publish the package.
- Does not change backend/API behavior.
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 1b1b2f7730
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| "scripts": { | ||
| "build": "tsc -p tsconfig.json", | ||
| "typecheck": "tsc -p tsconfig.json --noEmit", | ||
| "prepack": "npm run build", |
There was a problem hiding this comment.
When this package is actually published via the new prepack packaging path, package.json still has "private": true on line 4; npm's package-json docs state that this makes npm refuse to publish the package. That leaves the SDK buildable for packaging checks but blocks a real npm publish, so the package should drop the private flag or otherwise be made intentionally publishable before this is considered npm-ready.
Useful? React with 👍 / 👎.
1 participant
