Skip to content

Conversation

@jurerotar
Copy link
Contributor

@jurerotar jurerotar commented Jan 24, 2026

This PR should resolve #141. The issue is that because sqlite3-opfs-async-proxy.js is marked as an entrypoint in tsdown config, it's converted to esm. Since there's no esm-specific code there originally, rolldown add a export {} to the end, which breaks initializing this worker without { type: 'module' }.

@tomayac, I hate to bother you again, but we'll need another release. I'll add latest commits from sqlite as well.

@jurerotar
Copy link
Contributor Author

#143 should get merged before new release as well 😄

jurerotar and others added 3 commits January 24, 2026 16:33
…e0990392a9380954992) (#20)

Co-authored-by: jurerotar <28565137+jurerotar@users.noreply.github.com>
# Conflicts:
#	src/bin/sqlite3-bundler-friendly.mjs
#	src/bin/sqlite3-node.mjs
#	src/bin/sqlite3.mjs
#	src/bin/sqlite3.wasm
Copy link
Collaborator

@tomayac tomayac left a comment

Choose a reason for hiding this comment

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

LGTM, thanks!

@tomayac tomayac merged commit eb77127 into sqlite:main Jan 26, 2026
8 checks passed
@jurerotar jurerotar deleted the fix/issue-141 branch January 26, 2026 08:55
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.

Vite tries to create ESM OPFS async proxy worker as type=classic

2 participants