blocka

I am also having the same issue with a class that extends EventEmitter

As a workaround, I'm no longer extending EventEmitter, but including an event emitter as an instance property, and manually creating proxy methods to call that event emitter.

Most issues I can get around by using vue.esm and letting babel-jest go into node_modules/vue. I have one big deal breaker however. The problem is illustrated in this jest test:...

@foxbunny does it make sense to run the code through babel after TS? When everything is esm (jest is pointing to vue.esm, and typescript is generating es2015 modules), we wind...

1) 29.0.1547.76 2) 0.1.7 3) Yes 4) All The error was actually occurring from hgimnogjllphhhkhlmebbmlgjoejdpjl (XPath Helper), but only manifested itself after restarting the app in debug mode. When I...

Using vue-cli 3: this helped for me ```js config.module .rule('mjs') .test(/\.mjs$/) .type('javascript/auto') .end() ```

There are a few people approaches some people are trying (https://github.com/SmallComfort/react-vue and https://github.com/vueact/babel-plugin-transform-react-to-vue) I'm wondering if a very simple approach would work: simply call ReactDOM.render in mounted. Haven't tried it...

It seems without adding `--full-paths` to browserify, the indexes are numeric and thus there's no way (save for providing an `rmap`, possibly) or matching the input files to the modules....

I don't see anything like that being created. It's not in the bundle.js after I do this: ``` cd test/deps browserify x.js y.js > bundle.js ``` If I do `browser-unpack...

> Guys, any idea on that?! > > To be able to add my pages to Storybook I was thinking of having 2 components to compose a page like described...