Julian

i looked at it before and didnt find an answer

ok.. but is there a workaround?

if this PR going into core?

hey marshallswain, i don't think there is any benefit to upgrade stealJS. There are several alternatives like viteJS and rollup. Loading a website with stealJS in production takes a long...

here is a vite-stache-plugin https://github.com/pYr0x/vite-plugin-stache i created some other plugins for snowpack and rollup as well: https://github.com/pYr0x?tab=repositories

i not really understand what the expectation is? - loading the file foo.es6 and not foo.es6.js -> ok - but what should be happen after loading foo.es6? it has to...

> Would make steal.js a big bigger (maybe even a lot bigger). Might be ok for dev, but not acceptable for production, so would need a way to exclude it....

what is about this idea: - untouch the `steal.prduction.js` - on build create a `bundles.json` file that contain all the bundles that today will write into the bundled file ```...

@matthewp i want to work on this feature like i described in my comment. can you confirm that this is a way it could / should work?

i run into the same issue. i have this simple Vue Component ``` const foo = useState('foo', () => 1); {{foo}} ``` if i change foo, HMR will not update...