The feature is very useful to a wide range of client-based applications, one core use case for sql.js.
The size increase seems reasonable considering the new capabilities, being only 744K for the wasm file (638K before this PR).
Using a custom sql.js build should be last resort, as it means it'll be harder for users to upgrade.

Closes#199, which included additional unrelated changes and didn't have tests.

Enables FTS5 by default

2b45bfe

Copy link

P-de-Jong commentedOct 31, 2024

This would be great. It would mean we wouldn't need a custom build anymore.

Copy link

Member

lovasoa commentedNov 3, 2024

Hi ! Asset sizes are often a limiting factor when integrating large libraries like sql.js.

I agree we should include a FTS5 build in our build process, include it in tests, and distribute pre-compiled wasm files for easy access. But it should not be part of the default build.

Ideally, we could make it so that switching to fts5 would be as easy as

constSQL=awaitinitSqlJs({locateFile:file=>`/dist/fts5.${file}`});

lovasoa requested changes

Nov 3, 2024

View reviewed changes

Copy link

Member

lovasoa left a comment•
edited
Loading

Choose a reason for hiding this comment

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

I'd rather not increase the default asset size for all existing users, none of whom use fts5.

Copy link

lsb commentedAug 13, 2025

fts5 seems to be supported in the official buildhttps://www.npmjs.com/package/sqlite-wasm-http

Labels

None yet

4 participants

Movatterモバイル変換

Navigation Menu

Search code, repositories, users, issues, pull requests...

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Enables FTS5 by default#594

Are you sure you want to change the base?

Enables FTS5 by default#594

Uh oh!

Conversation

arcanis commentedSep 18, 2024•
edited
Loading

Uh oh!