node-sqlite3
design
node-sqlite3 | design | |
---|---|---|
13 | 34 | |
6,066 | 11,350 | |
0.5% | 0.2% | |
7.4 | 3.9 | |
11 days ago | 12 days ago | |
PLpgSQL | ||
BSD 3-clause "New" or "Revised" License | Apache License 2.0 |
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.
node-sqlite3
-
SvelteKit error during build, presumably due to sqlite3
Probably wrong import: https://github.com/TryGhost/node-sqlite3/issues/1532
-
Is it possible to use c or c++ code in the electron backend?
A good example for showing a solution to those questions is the node-sqlite3 package. It's a native module written in C++ and made available as a Node package: https://github.com/TryGhost/node-sqlite3
-
How to call this function in Node.js sqlite?
sqlite3 appears to have this, but there may be some issues as to whether it works. https://github.com/TryGhost/node-sqlite3/issues/419
-
Ask HN: Do you contribute to open source projects?
When I worked as an employee I contributed mostly just with docs fixes or bug reports (and not that often). I think it's mostly a mindset of seeing an issue yourself and noticing that others probably also are confused or misled by something so you go and report it!
Now that I'm working full-time on open-source and my own company I can contribute more easily to projects like upgrading SQLite source in a few bindings libraries [0], [1], [2] when 3.38 came out.
If anyone is interested in contributing to open-source and wants a bit more guidance though I have a number of good "first timer" projects related to data tools. Only expectation is that you have some experience with Go. Join discord.multiprocess.io, go to the #dev channel and say hi!
[0] https://github.com/mattn/go-sqlite3/pull/1019
[1] https://github.com/mapbox/node-sqlite3/pull/1550
[2] https://github.com/JoshuaWise/better-sqlite3/pull/778
-
Embedded DB for ElectronJS?
I have had no problems using SQLite itself in Electron, for a desktop project that runs under both Windows and Linux. See https://github.com/mapbox/node-sqlite3
- Node Bindings untuk binding dari C++ pada Node.js
-
New to electron.
I like to set up a function in the main process with https://github.com/mapbox/node-sqlite3 handling my queries.
-
How would you create a simple database search-bar website?
Use SQLite to store the data and retrieve it using sqlite3
-
Edit SQL file stored on nextcloud
Hey I would like to use a nextcloud instance to host a sqlite database file, and connect directly to that file, with javascript/Electron and the sqlite3 library.
-
npm install --save sqlite3 error
This sub is for discordjs, not just general javascript and npm issues. Ask sqlite3 package devs about this. https://github.com/mapbox/node-sqlite3
design
-
Rust, WASM, and LOK
First of all, a quick rundown of what WASM is. It stands for Web Assembly. In essence, similar to how Java compiles down to a bytecode that is interpreted by a Java Virtual Machine, Web Assembly is a different bytecode interpreted by the browser. Many different languages can compile into WASM, and Javascript can interface with it like a module. In my case, I wrote a lot of the source code in Rust and compiled it down to a WASM module, then called into it from Javascript.
-
Surprisingly Powerful – Serverless WASM with Rust Article 1
WebAssembly (abbreviated Wasm) is a binary instruction format for a stack-based virtual machine. Wasm is designed as a portable compilation target for programming languages, enabling deployment on the web for client and server applications. - https://webassembly.org
-
Reaching and surpassing the limits of JavaScript BigData with WebAssembly
With WebAssembly we can compile our C++ codebase into a wasm module for the browser. So when you look at a SciChart.js chart you're actually seeing our C++ graphics engine wrapped for JavaScript.
-
WASM Instructions
I should add, however, that the unmentioned elephant in the room is V8 JIT (TurboFan), which simply doesn't handle irreducible control flow. While there are some valid theoretical arguments around the current arrangement in Wasm, looking at the history of the associated discussions makes it pretty obvious that having V8 support Wasm and generate fast code similar to what it can do for asm.js was an overriding concern in many cases. And Google straight up said that if Wasm has ICF, they will not bother supporting such cases, so it will be done by a much slower fallback:
https://github.com/WebAssembly/design/issues/796#issuecommen...
AFAIK no other Wasm implementation has the same constraint - the rest generally tend to desugar everything to jumps and then proceed from there. So this is, at least to some extent, yet another case of a large company effectively forcing an open standard to be more convenient for them specifically.
-
Supercharge Web AI Model Testing: WebGPU, WebGL, and Headless Chrome
https://github.com/WebAssembly/design/issues/1397
> Currently allocating more than ~300MB of memory is not reliable on Chrome on Android without resorting to Chrome-specific workarounds, nor in Safari on iOS.
That's about allocating CPU memory but the GPU memory situation is similar.
-
Build your own WebAssembly Compiler
As far as I can tell (5 minutes of internet research) this was to allow easier compilation to JavaScript as a fallback in the days when WASM wasn't widely supported.
"Please add goto" issue has been open since 2016:
https://github.com/WebAssembly/design/issues/796
Most interesting comment:
> The upcoming Go 1.11 release will have experimental support for WebAssembly. This will include full support for all of Go's features, including goroutines, channels, etc. However, the performance of the generated WebAssembly is currently not that good.
> This is mainly because of the missing goto instruction. Without the goto instruction we had to resort to using a toplevel loop and jump table in every function. Using the relooper algorithm is not an option for us, because when switching between goroutines we need to be able to resume execution at different points of a function. The relooper can not help with this, only a goto instruction can.
> It is awesome that WebAssembly got to the point where it can support a language like Go. But to be truly the assembly of the web, WebAssembly should be equally powerful as other assembly languages. Go has an advanced compiler which is able to emit very efficient assembly for a number of other platforms. This is why I would like to argue that it is mainly a limitation of WebAssembly and not of the Go compiler that it is not possible to also use this compiler to emit efficient assembly for the web.
^ https://github.com/WebAssembly/design/issues/796#issuecommen...
-
Flawless – Durable execution engine for Rust
When I implemented a WASM compiler, the only source of float-based non-determinism I found was in the exact byte representation of NaN. Floating point math is deterministic. See https://webassembly.org/docs/faq/#why-is-there-no-fast-math-... and https://github.com/WebAssembly/design/blob/main/Nondetermini....
-
Requiem for a Stringref
> To work with GC, you need some way to track if the GC'd object is accessible in WASM itself.
I've never heard of a GC with that kind of API. Usually any native code that holds a GC reference would either mark that reference as a root explicitly (eg. https://github.com/WebAssembly/design/issues/1459) or ensure that it can be traced from a parent object. Either way, this should prevent collection of the object. I agree that explicitly checking whether a GC'd object has been freed would not make any sense.
> The reason why you probably need a custom string type is so you can actually embed string literals without relying on interop with the environment.
WASM already has ways of embedding flat string data. This can be materialized into GC/heap objects at module startup. This must happen in some form anyway, as all GC-able objects must be registered with the GC upon creation, for them to be discoverable as candidates for collection.
Overall I still don't understand the issue. There is so much prior art for these patterns in native extensions for Python, PHP, Ruby, etc.
-
The Tug-of-War over Server-Side WebAssembly
Giving you a buffer that grows is the allocation approach I am talking about. This is not how your OS works. Your OS itself works with an allocator that does a pretty good job making sure that your memory ends up not fragmented. Because WASM is in between, the OS is not in control of the memory, and instead the browser is. The browser implementation of "bring your own allocator" is cute but realistically just a waste of time for everybody who wants to deploy a wasm app because whatever allocator you bring is crippled by the overarching allocator of the browser messing everything up.
It seems like the vendors are recognizing this though, with firefox now having a discard function aparently!
https://github.com/WebAssembly/design/issues/1397
- How do Rust WebAssembly apps free unused memory?
What are some alternatives?
NeDB - The JavaScript Database, for Node.js, nw.js, electron and the browser
content - The content behind MDN Web Docs
node-gyp - Node.js native addon build tool
wave - Realtime Web Apps and Dashboards for Python and R
better-sqlite3 - The fastest and simplest library for SQLite3 in Node.js.
interface-types
WASI - WebAssembly System Interface
Chevrotain - Parser Building Toolkit for JavaScript
neon - Rust bindings for writing safe and fast native Node.js modules.
Fuse - Lightweight fuzzy-search, in JavaScript
iswasmfast - Performance comparison of WebAssembly, C++ Addon, and native implementations of various algorithms in Node.js.