John Jenkins

hey @mikkelrom - I took the liberty of taking your reproduction repo for a spin, but could not recreate the issue using the steps described: "Hello world!"  "Hello...

It's not clear to me how https://bundlers.tooling.report/hashing/asset-cascade/ is relevant because in this instance it's the actual 'core' file who's source is changing, not an imported asset. And I also don't...

to be clear, @bzolotukhyn @cjorasch @janarvaez is the issue primarily with the `.system.js` modules (i.e. the es5 build)? Or do you see it other places too?

just chiming in to say, I've found for vite, if you remove your stencil lib from vite's optimisation, things should work as expected - dev or otherwise. e.g. ``` import...

Just chiming in to add a '+1' to some kind of caching for server components; we've recently had our first foray into using them and whilst in-isolation 'lighthouse number go...

are `@Prop` getters / setters a good compromise here? https://github.com/ionic-team/stencil/pull/2899

The ‘project name’ doesn’t really relate to the package name. It’s just used to name folders and some entry files

thanks - need this too. Also the current implementation loses any error context from the storyblok fetch and doesn't throw any errors too

> @danilowoz I don't know if you're still going for this, but I ended up copying the pattern in https://github.com/storyblok/storyblok/blob/master/src/tasks/pull-components.js and using a storyblok client initialized with an oauth token....

Hi! just to make it known this feature is definitely used by the community https://dev.to/sanderand/running-multiple-versions-of-a-stencil-design-system-without-conflicts-2f46 :)