Would be nice if node packages could be packed up in ZIP files so to avoid the security/metadata tax for small file access on Windows.
Node.js needs a virtual file system
11–20 of 275 posts
Re: Node.js needs a virtual file system
#12Would be nice if node packages could be packed up in ZIP files so to avoid the security/metadata tax for small file access on Windows.
https://web.archive.org/web/20161003115800/https://blog.mozi...
Re: Node.js needs a virtual file system
#13I like the idea of it mocking the file system for tests, but I feel like that should probably be part of the test suite, not Node.
The example towards the end that stores data in a sqlite provider and then saves it as a JSON file is mind-boggling to me. Especially for a system that's supposed to be about not saving to the disk. Perhaps it's just a bad example, but I'm really trying to figure out how this isn't just adding complexity.
Re: Node.js needs a virtual file system
#14Are people still building new projects on Node.js? I would have thought the ecosystem was moving to deno or bun now
I don't really understand what the value proposition of Bun and Deno is. And I see huge problems with their governance and long-term sustainability. Node.js on the other hand is not owned or controlled by one entity. It is not beholden to the whims of investors or a large corporation. I have contributed to Node.js in the past and I was really impressed by its rock-solid governance model and processes. I think this an…
Re: Node.js needs a virtual file system
#15Would be nice if node packages could be packed up in ZIP files so to avoid the security/metadata tax for small file access on Windows.
Re: Node.js needs a virtual file system
#16From https://github.com/jupyterlite/jupyterlite/issues/949#issuec... :
> Ideally, the virtual filesystem of JupyterLite would be shared with the one from the virtual terminal.
emscripten-core/emscripten > "New File System Implementation": https://github.com/emscripten-core/emscripten/issues/15041#i... :
> [ BrowserFS, isomorphic-git/lightningfs, ]
pyodide/pyodide: "Native file system API" #738: https://github.com/pyodide/pyodide/issues/738 re: [Chrome,] Filesystem API :
> jupyterlab-git [should work with the same VFS as Jupyter kernels and Terminals]
pyodide/pyodide: "ENH Add API for mounting native file system" #2987: https://github.com/pyodide/pyodide/pull/2987
Re: Node.js needs a virtual file system
#17I'm not convinced that allowing Node to import "code generated at runtime" is actually a good thing. I think it should have to go through the hoops to get loaded, for security reasons. I like the idea of it mocking the file system for tests, but I feel like that should probably be part of the test suite, not Node. The example towards the end that stores data in a sqlite provider and then saves it as a JSON file is mi…
Re: Node.js needs a virtual file system
#18Would be nice if node packages could be packed up in ZIP files so to avoid the security/metadata tax for small file access on Windows.
Re: Node.js needs a virtual file system
#19Are people still building new projects on Node.js? I would have thought the ecosystem was moving to deno or bun now
loud people on twitter are always switching to the new hotness. i personally can't see myself using bun until its reputation for segfaults goes away after a few more years of stabilizing. deno seems neat and has been around for longer, but its node compatibility story is still evolving; i'm also giving it another year before i try it.
Open 80, closed 492.
Re: Node.js needs a virtual file system
#20 You can’t import or require() a module
that only exists in memory.
You can convert it into a data url and import that, can't you?