Heavy .cache folder in npm package

[mattleonowicz]

Hi @aholachek

I've noticed there is this heavy .cache folder distributed in the npm package for 'flip-toolkit'.
I think this might be a mistake and it should be ignored when distributing

[aholachek]

Thank you for the heads up! I'll take a look at this today.

[F3n67u]

@aholachek could you help solve this problem? flip-toolkit takes 56mb of my disk. I think it's very unreasonable.

https://packagephobia.com/result?p=flip-toolkit

[jwindmuller]

This large package is timing out some builds in GitHub actions intermitently, seems like 7.0.11 didn't suffer from this problem:

https://registry.yarnpkg.com/flip-toolkit/-/flip-toolkit-7.0.13.tgz
https://registry.yarnpkg.com/flip-toolkit/-/flip-toolkit-7.0.11.tgz

[mattleonowicz]

@aholachek Can you take a look? I believe there is no way we can make a PR for this, right?
Files that decide what is published to npm are not commited, right? I have no experience with publishing. Ignoring this .cache during publishing is required.

[aholachek]

Apologies for the delay in response, and thanks for the pings.
I just released v7.0.14 which should fix this issue.