hazelcast-nodejs-client
memfs
| hazelcast-nodejs-client | memfs | |
|---|---|---|
| 2 | 3 | |
| 146 | 1,617 | |
| 0.0% | - | |
| 5.2 | 9.4 | |
| 14 days ago | 3 days ago | |
| TypeScript | TypeScript | |
| Apache License 2.0 | 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.
hazelcast-nodejs-client
-
Hazelcast Node.js Client 4.0 is Released
You can see the list of all changes in this version in the release notes.
memfs
-
CoWasm: An alternative to Emscripten, based on Zig (demo: Python in the browser)
I am using the Python ecosystem (with full support for dynamic loading of C extension modules) as an initial motivating project. Also, the Python test suite is extremely useful to root out problems. I certainly hope that this can provide a more complete alternative to Emscripten to the community eventually. That said, Emscripten is huge, and the problems involved in creating a more maintainable modular WASM build tool are subtle. For example, when implementing a custom module loader for Python-wasm last week, I discovered several bugs in the memfs and unionfs Javascript libraries (https://github.com/streamich/memfs/pulls?q=is%3Apr+author%3A... and https://github.com/streamich/unionfs/pulls?q=is%3Apr+author%...). I had to learn the code sufficiently to fix all these bugs, submit PR's, etc. Emscripten has its own analogue of memfs, which is optimized specifically for WebAssembly in the browser, where memfs is a more general widely used library (with 10M+ downloads/week).
CoWasm has no support for asyncify. Where I've run into setjmp/longjmp so far, I've been rewriting the code instead. E.g., the dash shell uses setjmp/longjmp, and I'm rewriting that to use return error codes instead (see, e.g., https://github.com/sagemathinc/dash/commit/7117e1f6496728af0...).
> how would I go about porting a simple C->WASM w/ Typescript library project to CoWasm?
That's a great question, which I'm not sure how to quickly answer, so I've created a discussion item here https://github.com/sagemathinc/cowasm/discussions/40
-
Encryption in PDF Specification and my attempt to do it in pdf-lib
Looks like this whole thing was motivated by the fact that, in order to get the encrypted PDF in a Buffer like they wanted, they had to save to disk and load it back. They could have instead used an in-memory filesystem such as https://github.com/streamich/memfs and just made the existing PDF library that was almost right use that.
-
I used emscripten to port a command line program to JS/web assembly, now what?
How do I populate the input files? The filesystem API in emscripten talks about MEMFS, is that the same as this? https://github.com/streamich/memfs
What are some alternatives?
FortJs - A feature-rich Node.js web framework designed for building powerful, scalable, and maintainable web applications.
react-native-file-access - Filesystem access for React Native
coherence - Oracle Coherence Community Edition
fs-jetpack - Better file system API for Node.js
hazelcast-go-client - Hazelcast Go Client
spacedrive - Spacedrive is an open source cross-platform file explorer, powered by a virtual distributed filesystem written in Rust.
js-markerclusterer - Create and manage clusters for large amounts of markers
react-cool-virtual - 😎 ♻️ A tiny React hook for rendering large datasets like a breeze.
mastak - NPM package for automated, in-memory API caching.
unionfs - Use multiple fs modules at once
hazelcast-csharp-client - Hazelcast .NET Client
cowasm - CoWasm: Collaborative WebAssembly for Servers and Browsers. Built using Zig. Supports Python with extension modules, including numpy.