GoKawiilWhy?
The NPM ecosystem has a dependency problem. If you look at the most popular libraries in the registry, many carry immense legacy baggage that all developers have to pay the cost for.
e18e.dev is a movement that aims to cleanup and modernize the ecosystem. Huge dependency trees slow down applications, degrade install times, and drastically increase the surface area for supply chain attacks.
As part of my contribution to the community, I wrote modern-tar to demonstrate that we can build a faster, leaner, standards-compliant TAR parser using zero dependencies and modern primitives that is also browser friendly.
The Architecture
Most historical TAR libraries in the JS ecosystem were tightly coupled to Node.js streams. While powerful, it is a heavy abstraction that also ties your business logic to a single runtime.
The Core Engine
To support both browsers and alternative runtimes that interact with the filesystem, I decoupled the parsing logic from the I/O layer entirely.
The core engine is a pure, synchronous state machine. It has no concept of I/O or runtimes. It simply consumes raw Uint8Array chunks and manages the internal parsing states of various TAR implementations.
Wrappers Core Engine + Pure State Machine + No I/O Knowledge Node.js Streams + fs.ReadStream Web Streams API + ReadableStream Uint8Array Uint8Array
... continue reading