Sort of? I guess there are reasons; not sure if they are actually good reasons.
I'm lazy - Learning how to publish on NPM has never been high on my list.
Unsure about benefits - The tiny fraction of developers for whom it might be interesting or useful will probably find it. It seems easy enough to reference a package with a git link.
It's not stable - This is an experiment that is one month old. I haven't gotten around to incorporating it into my own web app yet. Right now it's more of a proof-of-concept than a component. Update: It's older than a month and has had some use. The library itself has been pretty stable, but examples (e.g. IndexedDbVFS) have not.
Low traffic is a happy place - I don't have any motivation to mess with that.
The library does not seem to be on NPM right now. Is that intentional?
The text was updated successfully, but these errors were encountered: