a version without polyfills?

[NullVoxPopuli]

Rationale

I was looking at using zenfs, but it seems it's too big! Too many kb.

I was going to use it for my REPL
NullVoxPopuli/limber#1995

The features that are polyfilled have been shipped for quite some time now.

Can they be removed?
Consumers of this library can polyfill what they need to, if they need to

API Proposal

No response

Additional context

No response

[james-pre]

Hey @NullVoxPopuli, thanks for reaching out.

The only polyfills implemented as part of ZenFS are src/polyfills.ts. Any other polyfills are done by dependencies. For example, I opened nodejs/readable-stream#552 to get a polyfill for AbortController removed. This is ironically the example polyfill used in your PR on Limber.

I am all for removing polyfills of APIs that have long been widely available, however many of these dependencies are either unmaintained or receive very little attention. You want want to consider putting some pressure on said dependencies to get unneeded polyfills removed.

[james-pre]

Something you can do is add an npm override that maps the AbortController polyfill package to an empty one or something. Then it won't be bundled or anything.

[NullVoxPopuli]

Sounds like a promising strategy! If all polyfills (including those from deps), how small do you suspect we can make the browser-mode fs?

[NullVoxPopuli]

Perhaps I configured bundlejs wrong -- I specified readable-stream and abort-controller as "external", and only went down by 4kb:

https://bundlejs.com/?q=%40zenfs%2Fcore%2C%40zenfs%2Fdom&treeshake=%5B%7B+configure+%7D%5D%2C%5B%7B+WebAccess+%7D%5D&config=%7B%22esbuild%22%3A%7B%22external%22%3A%5B%22abort-controller%22%2C%22readable-stream%22%5D%7D%7D

[james-pre]

ZenFS is not a small codebase. If I remember correctly, the source code and tests come out to over 20,000 lines (and the compiled JS is somewhat larger due to downleveling). The npm package is over 800KB (not including any dependencies), so getting it down to 51.5KB is already impressive.