wordpress-playground
absurd-sql
wordpress-playground | absurd-sql | |
---|---|---|
22 | 24 | |
1,527 | 4,057 | |
1.4% | - | |
9.7 | 2.5 | |
2 days ago | 9 months ago | |
JavaScript | JavaScript | |
GNU General Public License v3.0 only | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
wordpress-playground
-
Things you forgot because of React
Sorry friend, WordPress already beat you to it: https://github.com/WordPress/wordpress-playground
- WordPress Playground: A WordPress that runs entirely in the browser
-
WordPress Playground: A WordPress that runs in the browser
> Is there a reason why using OPFS directly from SQLite doesn't work?
I'm guessing this means using SQLite WASM's built-in OPFS integration as described in these articles:
- sqlite3 WebAssembly documentation - Persistent Storage Options: OPFS - https://sqlite.org/wasm/doc/trunk/persistence.md#opfs
- SQLite Wasm in the browser backed by the Origin Private File System - https://developer.chrome.com/blog/sqlite-wasm-in-the-browser...
Within the Playground, SQLite interacts with the database file in MEMFS only, and the Playground coordinates the syncing from MEMFS to OPFS.
https://github.com/WordPress/wordpress-playground/tree/trunk...
The reason for this, I believe, is that the primary use case is/was to have the entire file system in memory, including SQLite's database file. This was the original implementation, and is still the default behavior. Persistence was later added as an optional feature.
The good news is that browser support for OPFS seems to be getting better. From the SQLite docs:
As of March 2023 the following browsers are known to have the necessary APIs:
-
WordPress Playground
One of the most exciting things at WordCamp Europe 2023 for me was discovering how far along the WordPress Playground project is. If you haven’t heard of the playground before, it’s a full version of WordPress, running directly in your browser!
-
WCGI: WebAssembly and CGI
WordPress has an official WebAssembly build for the browser and Node.js: https://developer.wordpress.org/playground https://github.com/WordPress/wordpress-playground
(Disclosure: I'm the creator)
-
WordPress testing official SQLite Support
I love the work going on there at WasmLabs, especially enjoying the articles with in-depth technical explorations.
After the article about running WordPress in the browser was published, there's a new project called WordPress Playground which is gradually preparing NPM or Composer packages to make it easier for people to run it.
https://github.com/WordPress/wordpress-playground/
They've been doing very detailed work, like making some patches to PHP and SQLite for improved compatibility with Emscripten, etc. It seems there's a lot of overlap with what WasmLabs has achieved and probably have continued to develop further. Perhaps there's an opportunity for collaboration.
- WordPress WASM
-
Hacker News top posts: Sep 25, 2022
WordPress WASM\ (28 comments)
absurd-sql
- Absurd-SQL: sqlite3 in ur indexeddb (hopefully a better back end soon)
- What If OpenDocument Used SQLite?
-
WASM SQL database recommendations wanted
Not really, but I'm aware of absurd-sql. Note that this requires IndexedDB and thus a browser environment.
-
Best local database that works on all platforms including web?
I don't need SQL capabilities, so I didn't look into those options (there's also absurd-sql, which ports sqlite to the browser on top of IndexedDB).
-
SQLite WASM in the Browser Backed by the Origin Private File System
Ironically I was just about to drop in absurd-sql [1] to a project, which uses indexeddb to back SQLite. This seems better.
[1] https://github.com/jlongster/absurd-sql
-
Irmin in the Browser (OCaml/MirageOS)
There is also absurd-sql that is sqlite3 in wasm using IndexDB as storage and it’s faster than IndexDB itself
[1]: https://github.com/jlongster/absurd-sql
-
Postgres WASM by Snaplet and Supabase
Offline data: running it in the browser for an offline cache, similar to sql.js or absurd-sql.
- WordPress WASM
-
Learn PWA
We are very close to having WASM SQLite with persistence in the web platform. Until now SQLite compiled to WASM was in memory and you had to write the whole database out as a binary array to save changes. There is absurd-sql (https://github.com/jlongster/absurd-sql), which builds a virtual file system on top of IndexedDB for sqlite, its incredible, but a bit of an ugly hack.
However, the new file-access apis (https://developer.mozilla.org/en-US/docs/Web/API/File_System...) that are landing in browsers will fix this. One of the things it does is enable very efficient block level read/write access to a privet sandboxed filesystem for the websites origin, perfect for persistent sqlite. There is more here: https://web.dev/file-system-access/#accessing-files-optimize...
- Learn Postgres at the Playground
What are some alternatives?
marmot - A distributed SQLite replicator built on top of NATS
lovefield - Lovefield is a relational database for web apps. Written in JavaScript, works cross-browser. Provides SQL-like APIs that are fast, safe, and easy to use.
dod - DOS on dope. The last MVC Web framework you'll ever need
crdt-example-app - A full implementation of CRDTs using hybrid logical clocks and a demo app that uses it
webrcade - Feed-driven gaming
dolt - Dolt – Git for Data
wapm-cli - 📦 WebAssembly Package Manager (CLI)
realtime - Broadcast, Presence, and Postgres Changes via WebSockets
wp-sqlite-db - A single file drop-in for using a SQLite database with WordPress. Based on the original SQLite Integration plugin.
donutdb - Store and query a sqlite db directly backed by DynamoDB.
Platform - Qbix Platform for powering Social Apps (http://qbix.com/platform)
localForage - 💾 Offline storage, improved. Wraps IndexedDB, WebSQL, or localStorage using a simple but powerful API.