Julian

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...

since one year. why is this PR not accepted?

@matthewp any idea when the second bug will be fixed?

hey @frank-dspeed, it would be nice if you can share your rollup config in a github gist.

i dont understand. the `@loader` is defined as ``` [ 3, function(stealRequire, stealExports, stealModule) { stealModule.exports = { logLevel: 3, meta: {}, main: "main", envs: { "window-production": { serviceBaseURL: "/api/production"...

@m-mujica thanks for clarification. maybe we can change the naming of `global.steal` because i think people gets confused because in normal steal, `steal.System` is the loader and contains mappings and...

in normal steal, `steal` gets published to `window.steal` you can access steal without require it with `@steal`. if people do that with slim, they get back the slim loader what...

if that is possible @m-mujica ? i am ok with that...

As I said, for me it is confusing that steal is not the same on normal steal and slim-loader I prefer to rename the config of the slim loader configs....

unfortunately it doesn't work. in "d3-color" some code like this: ```js define(Color, color, { displayable: function() { return this.rgb().displayable(); }, toString: function() { return this.rgb() + ""; } }); ```...