Skip to content

chore(og): add the metadata this package needs to be publishable - #9

Merged
acamarata merged 1 commit into
mainfrom
feat/publish-og-package
Aug 20, 2026
Merged

chore(og): add the metadata this package needs to be publishable#9
acamarata merged 1 commit into
mainfrom
feat/publish-og-package

Conversation

@acamarata

Copy link
Copy Markdown
Contributor

Adds repository, homepage, description, and main/module/types fallbacks for resolvers that do not read the exports map. The package already carried MIT and publishConfig.access: public.

Verified with npm publish --dry-run: 5.4kB, 7 files, public access.

Publishing itself is blocked: the @nself-web npm organization does not exist, so publish returns 404 and org queries return 403. Once the org is created this package can go out unchanged.

Context: @nself-web/og is the one package ɳTask's /api/og Edge Function needs, and Vercel's function bundler cannot resolve a workspace package from a sibling checkout. Publishing is the only fix that works for all six consumers (base, clawde, cloud, nsentry, ntask, ntv) without duplicating code.

repository, homepage, description, and main/module/types fallbacks for
resolvers that do not read the exports map. It already carried MIT and
publishConfig.access=public.

Publishing is blocked on an npm organization for the @nself-web scope, which
does not exist yet — npm returns 404 on publish and 403 on org queries. Once
that org exists this package can go out as-is; verified with a dry run
(5.4kB, 7 files).
@acamarata
acamarata merged commit 8ce99aa into main Aug 20, 2026
3 checks passed
@acamarata
acamarata deleted the feat/publish-og-package branch August 20, 2026 15:52
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