Being able to `npm install` this for a frontend app would be very useful.
The JavaScript world is culturally so dependent on npm now that adoption of SQLite in that world would massively increase given the availability of a good "official" package.
And without an official one I imagine there will quickly emerge dozens of unofficial ones, many of which will end up poorly maintained in the future.
It seems like Chrome is paying them for the “deliverable” of a JS version, but the spec did not include “npm installable”.
None of us in the sqlite use npm in any way, shape, or form, so there's nothing at all unusual about us not publishing anything there.
> It seems like Chrome is paying them for the “deliverable” of a JS version, but the spec did not include “npm installable”.
Like all deliverables released via the sqlite project, this one was conceived and created as a deliverable which can be distributed through the existing project-level infrastructure. What other people do with it, through whatever infrastructure they like, is entirely up to them. Getting involved with such tooling is way out of scope for us.
Seeing as none of us in the sqlite project use NPM or node in any capacity whatsoever, nor do we have any interest in doing so, i'll opine that "unofficial" ones would be of much higher quality than any we would put out.
To repeat what i just said in another comment on this topic: Trying to support a tool one neither uses nor understands is like trying to wave away darkness with one's hand.