File size too big

[muriloime]

Hello there, I am very interested in the project, however unpacked size seems to big IMHO ( >700kb, compared to 200kb of react for example).

Is this correct or am I missing something here ( maybe some tool similar to tailwind's common workflow like to purge unused css like postcss? )?

Thanks in advance

[KevinBatdorf]

How are you bundling it? This entire GitHub repo is only 287kb.
Straight from the CDN is 26kb

[muriloime]

Hey thanks @KevinBatdorf . I am taking npm "Unpacked size" for granted at alpinejs npm. it is currently showing 774 kB. I wonder why such a big difference with the numbers you gave

[ryangjchandler]

You might want to use this tool to find the true size of files on disk: https://arve0.github.io/npm-download-size/#alpinejs

It's worth noting that this includes all of the files NPM downloads when you run npm install alpinejs.

[muriloime]

These numbers look much better. I was finding contradictory the size with the name of the library 😆 . Will give it a try . Many thanks !

[HugoDF]

Here's another link for bundle size https://bundlephobia.com/result?p=alpinejs

I opened a PR once to reduce unpacked size (we're shipping a lot of stuff that's not necessary in the npm package)

[KevinBatdorf]

Does NPM calculate the entire repo plus all the dependencies?

It might be worth getting that to a realistic number as it could be turning people away from the project.

[HugoDF]

Does NPM calculate the entire repo plus all the dependencies?

Npm uses the packed/unpacked size of the package, which at the moment is the whole repository minus the node_modules folder. That means both dist builds, but also all the source, all the HTML files and all the tests/docs etc.

See this #244