Skip to content

Add publishConfig.access=public - #12

Merged
jnunemaker merged 1 commit into
mainfrom
barcelona-v3
Jun 8, 2026
Merged

Add publishConfig.access=public#12
jnunemaker merged 1 commit into
mainfrom
barcelona-v3

Conversation

@jnunemaker

Copy link
Copy Markdown
Contributor

What

Adds publishConfig: { access: "public" } to package.json.

Why

@flippercloud/expressions is a scoped package, and npm defaults scoped packages to restricted access on publish. That means every publish requires the --access public flag, and forgetting it produces a confusing 402/403 error. Setting publishConfig.access to public bakes the right default into the package so npm publish just works — no flag needed.

Test plan

  • npm publish (or npm publish --dry-run) no longer needs --access public.

🤖 Generated with Claude Code

Scoped packages (@flippercloud/*) default to restricted on publish,
requiring --access public on every npm publish. Setting publishConfig
makes public access the default so the flag is never needed again.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@jnunemaker
jnunemaker merged commit a126228 into main Jun 8, 2026
4 checks passed
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