[codex] Add mojidata-api bundler-safe entrypoints#39
Merged
Conversation
This was referenced May 3, 2026
Closed
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
@mandel59/mojidata-apifacade entrypoints for browser, worker protocol, SQL.js Node,better-sqlite3, andnode:sqlitetargets.mojidata-web-appdoes not need privatelib/*imports.idsfind.dbschemas as FTS5 and document the@mandel59/idsdb-fts5requirement.Validation
corepack yarn node --import tsx --test ./tests/*.test.tsinpackages/mojidata-apicorepack yarn node --import tsx --test ./tests/*.test.tsinpackages/mojidata-api-sqlite-wasmcorepack yarn install --immutableRelated Issues
Related: #29
Related: #32
Related: #34
Notes
This branch is based on
cloudflarebecause the local work was built on top of the current D1/API deployment branch.