ALL the registered bloks are loaded on the client even when not used on the current page

[Dav3rs]

Describe the issue you're facing

I notice that my page was crashing due to scripts being executed that have nothing to do with the current page content.

It looks that ALL the storyblok components registered in the project are sent to client even when they are not needed in the current page consumed stories.

For example

1- I create a component that is not used on the page

2- With the next content

3- It it loaded :face_with_diagonal_mouth:

Reproduction

https://stackblitz.com/~/github.com/Dav3rs/astro-storyblok

Steps to reproduce

No response

System Info

Linux, astro latest, node lts.

Used Package Manager

npm

Error logs (Optional)

No response

Validations

• [X] Follow our Code of Conduct

[mediabeastnz]

I'm seeing the same thing, even on deployed sites astro build.

I'd put this high on the priority list as it could definitely effect performance and cause had to debug issues.

[mediabeastnz]

After looking into this more it looks like this is expected behaviour from Astro. any script tags are automatically hoisted and loaded as JS modules.

A workaround if this causes issues I guess is to have the script inline or add attributes to the script tag.

[Dav3rs]

@manuelschroederdev This is a huge flaw of the astro integration, it should be prioritized don't you think so?

[dipankarmaikap]

@Dav3rs , Thank you for bringing this issue to our attention. We're actively investigating it and will keep you updated with our findings. If we identify any workarounds or solutions, we’ll share them with you here and document them for other users as well.

[markpinero]

There’s no way to integrate dynamic components without a change in how Astro changes their build process. Related discussion: https://github.com/withastro/astro/issues/4863