Skip to content

chore: prepare package for npm publish#72

Merged
2witstudios merged 1 commit into
mainfrom
chore/npm-publish-ready
Jun 22, 2026
Merged

chore: prepare package for npm publish#72
2witstudios merged 1 commit into
mainfrom
chore/npm-publish-ready

Conversation

@2witstudios

Copy link
Copy Markdown
Owner

Summary

  • Remove "private": true — unblocks npm publish
  • Move tsx from devDependencies → dependencies (runtime dep: bin re-execs under tsx; not available on global install otherwise)
  • Add "postinstall": "npm run build" — builds vendored pi workspace packages after npm install -g
  • README quickstart updated to npm install -g pagespace-cli as the primary path; git clone flow moved to contributors section
  • Install & distribution section updated to reflect published state

Test plan

  • npm pack and inspect tarball contents include expected files
  • npm publish (user will run)
  • npm install -g pagespace-cli on a clean machine runs onboarding correctly

🤖 Generated with Claude Code

- Remove private:true so npm publish is unblocked
- Move tsx to dependencies (runtime dep: bin re-execs under tsx)
- Add postinstall script to build vendored pi workspace packages
- Update README quickstart to npm install -g as primary install path
- Update Install & distribution section to reflect published state

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Jun 22, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@2witstudios, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 33 minutes and 45 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 2bddd72d-41b1-4ca8-9eb3-18484ff6a9fe

📥 Commits

Reviewing files that changed from the base of the PR and between 8b247fb and 6bfd06e.

📒 Files selected for processing (2)
  • README.md
  • package.json
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/npm-publish-ready

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@2witstudios 2witstudios merged commit 18a274c into main Jun 22, 2026
2 checks passed
@2witstudios 2witstudios deleted the chore/npm-publish-ready branch June 22, 2026 17:40

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 6bfd06e3de

ℹ️ 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".

Comment thread package.json
"url": "https://github.com/2witstudios/pagespace-cli/issues"
},
"scripts": {
"postinstall": "npm run build",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Do not build workspaces in postinstall

On the documented npm install -g pagespace-cli path, this lifecycle script runs in the published package (checked npm install --help: global install is supported and scripts are only skipped with --ignore-scripts). The packed files omit tsconfig.base.json, but every workspace tsconfig.build.json extends ../../tsconfig.base.json, and the tsgo compiler is only in root devDependencies, which consumers do not get. This makes the new postinstall fail before the package finishes installing; ship prebuilt dist output or include the required build inputs/tools for runtime installs.

Useful? React with 👍 / 👎.

Comment thread package.json
Comment on lines +33 to +35
"dependencies": {
"tsx": "^4.19.2"
},

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Add the pi CLI as a runtime dependency

After installing the published tarball, npm leaves the included workspace folders under packages/ and does not link them into this package's node_modules (verified with a minimal packed workspace package); however bin/pagespace.mjs launches ../node_modules/@earendil-works/pi-coding-agent/dist/cli.js. This dependencies block installs only tsx, so even if the build step is bypassed or fixed, the pagespace bin exits with MODULE_NOT_FOUND for the pi CLI. Add the pi package as a real runtime dependency or launch from the vendored packages/pi-coding-agent path.

Useful? React with 👍 / 👎.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant