Choosing Between dist and dist-custom-elements Output Targets for SSR Framework Integration
Goal Publish a Stencil component library that will be consumed inside a server-side rendering framework, where components must render on the server and hydrate on the client without duplicate custom element registration. Constraints and uncertainty The default dist output target code-splits each component into its own lazy-loaded chunk, loaded on demand when
stenciljs