101arrowz

`fflate` isn't looking at the Zip64 end-of-central-directory record so it can only use the number of files given in the standard 16-bit EOCD record. This should be fixable, I'll look...

This actually brings up a bigger question; since Typegoose is targeted solely towards TypeScript users, why not remove the build step entirely and export the raw `.ts` files to NPM?...

> like i said earlier, this is how far i also got, but i got problems providing both at the same time, which is what i would like to do...

Docs in general are a major issue for Parcel v2. > what importing methods are supported (manifest keys, `_locales` folder, etc) Every import method from `manifest.json` is supported. Methods from...

Currently, no browsers truly implement ES Modules, so a transpiler like Babel converts ESM exports to CommonJS before bundling. Therefore there is no difference between the `uzip` NPM package and...

In response to the open questions: 1. From the [TS compiler API docs](https://github.com/Microsoft/TypeScript/wiki/Using-the-Compiler-API#customizing-module-resolution), it's possible to use a custom `ModuleResolutionHost` that implements `fileExists` and `readFile`. With this, it should be...

I was not aware of the existence of TS language service plugins, which would likely be the best solution for custom Parcel imports. I'd be willing to help with the...

An alternative to creating a Parcel resolver for TypeScript syntax is to create a TypeScript resolver for Parcel syntax, that way you can use any Parcel import with `"module": "node16"`....

Alternatively consider [`fflate`](https://github.com/101arrowz/fflate) for better performance and synchronous APIs.

See #349. If you want tree shaking, check out [fflate](https://github.com/101arrowz/fflate), which is faster, supports ES modules, and smaller.