Many same js files after generating many pages with same Vue component about slinkity

[bholmesdev]

Hi @Gospodin! Thanks for discovering this, since it's definitely not intended behavior. We're overhauling all component and asset generation right now to pull from "official" _assets and _islands folders in your project. Once this work is done, duplicate JS chunks should be impossible.

I'll keep this issue open for now for tracking once the 1.0 canary is out!

[Gospodin]

Hi @Gospodin! Thanks for discovering this, since it's definitely not intended behavior. We're overhauling all component and asset generation right now to pull from "official" _assets and _islands folders in your project. Once this work is done, duplicate JS chunks should be impossible.

I'll keep this issue open for now for tracking once the 1.0 canary is out!

Thanks @bholmesdev , is it possible in some hacky way to overcome this problem because it makes huge problem with
anomaly memory consumption while Vite transforming process?

[bholmesdev]

@Gospodin well, there is a build caching improvement I've been planning on as well. Mind sending me a sample repo to test against?

[Gospodin]

Hi @bholmesdev , it looks like my mistake, I verified and saw that js files for components are generating only once, but there are many same files with component import in case of many pages with same component, so as option it would be nice to generate import files using some sort of caching not populating same files for many times, it also will allow better browser caching. Thanks.

[bholmesdev]

Glad we could chat about this feature request Gospodin. I am sorry to say that Slinkity is no longer maintained. To make this clear to new users, I have archived the repository, and I have updated the project README to reflect the current status.

If the community would like to fork and keep Slinkity alive, all code is open and MIT licensed. I apologize for the radio silence, but I hope this clarifies everything!