Skip to content

build: publish built JavaScript so apps don't compile the specs - #457

Open
chrispader wants to merge 1 commit into
@chrispader/feat/nitro-v1from
nitro-v1/built-entry-points
Open

chrispader wants to merge 1 commit into
@chrispader/feat/nitro-v1from
nitro-v1/built-entry-points

Conversation

@chrispader

@chrispader chrispader commented Oct 22, 2026 •

Copy link
Copy Markdown
Member

The Nitro V1 specs use decorators, which React Native's default Babel preset can't parse. The package's react-native and source fields pointed at src, so every app would compile the specs with its own Babel config and fail. bob couldn't build the package for the same reason, so the next release would have failed to publish.

The entry points now point at the built output, and bob parses the specs through a small Babel config for each JavaScript target. main points at the CommonJS build that bob checks it against, and CI builds the package.

Reproduction

Run the package's build script in packages/react-native-nitro-sqlite. Before this change, bob stops with "Support for the experimental syntax 'decorators' isn't currently enabled".

🤖 Generated with Claude Code

@vercel

vercel Bot commented Oct 22, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
react-native-nitro-sqlite Ready Ready Preview Oct 23, 2026 12:19am UTC

Request Review

The package's react-native and source fields pointed at src, so apps
compiled the decorated .nitro.ts specs with their own Babel config,
which React Native's default preset can't parse. The entry points now
point at lib, and bob parses the specs through per-target Babel
configs. main points at the CommonJS build that bob validates it
against, and CI builds the package so a broken build shows up before
a release.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

This branch was successfully deployed

1 active deployment
Preview — 57bff2d0 Deployed Oct 23, 2026 by vercel[bot]
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