-
-
Notifications
You must be signed in to change notification settings - Fork 58
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Big increase in npm package size #108
Comments
Hi @mrchrisadams is that the main branch? I did try with running |
Alternatively, be explicit by using files property in package.json. |
ah, thanks @soulgalore - I was hunting around for the command to see the generated package, and Also, yikes:
Yeah, it was indeed the fixtures, but there are a few other culprits there:
This looks like it would indeed be an easy fix to change the |
@mrchrisadams I noticed you changed the
I also suggest we add the I've created #117 to resolve this. |
Merged in #117 and released in v0.11.2. |
We seem to have a muuuch bigger bundle size than before, and I am not sure what caused it.
It would be nice to not have this, and I suspect this is related to bundling some more data into the library by default.
It would be useful to see how people are using it, and which parts it might make sense to strip out to keep the npm bundle size reasonable.
The text was updated successfully, but these errors were encountered: