NPM package install size too large

[pweisensee]

Recently updated my @electric-sql/pglite from version 0.2.13 to 0.2.15 and the install size difference was huge, I believe double the size. It put my deployments over their size limit and I had to revert and go back to using 0.2.13.

When looking at the diff between these 2 versions, there seems to be a lot of new code added, so I'm unclear what exactly makes up the new package size difference.

Is it possible to reduce the install size of future versions? This package has become the largest npm package in my entire project.

[samwillis]

Hey, thanks for the report. I'm ware it got a little larger, but we clearly need to address this.

the root cause what that the last version has some of the work required to make PostGIS possible, including much of its dependencies. These are in the package, but unused as the work is not complete. It's not loaded by the browser at all.

I think it's clear we need to roll this back, and move PostGIS to a separate package when we finally get it working.

[samwillis]

This is fixed in main by #496, the next release package will be much smaller.