Richard Herrera
Richard Herrera
I've made another attempt at suppressing the error. Can you confirm that it's working?
It seems like Chrome has issues with resetting flex back to a zero value. Not sure what the workaround is, short of reloading the playground. I'll mark this as low...
I'm also seeing the same issue. Running OS X Mavericks, node 0.10.24. Rolling back to hardy 1.0.1 did not make a difference, the error persists.
Just wanted to chime in here, experiencing the same issue. ES6 was working just fine with `babel@
From my debugging, the problem comes from this line: https://github.com/jhnns/rewire-webpack/blob/master/lib/rewire.web.js#L10 In older versions of Babel, the value of `module` is the corresponding Webpack module id (i.e., if you import `jquery`,...
Babel doesn't touch `node_modules` or `rewire-webpack`. Not in my environment anyway.
@aybmab Interesting. Please open a ticket in react-helmet if you're still experiencing this leak.
@staxmanade Yeah we are in the process of switching TLDs.
Thanks. For the time being I chose the parser from Adobe's CSS Regions polyfill (See #15): https://github.com/adobe-webplatform/css-regions-polyfill/blob/master/src/cssparser.js @philipwalton This looks quite interesting and easier to manage than the current fix....
There's a huge amount of work that's been poured into reflexie, but there is a long way to go before it reaches even an alpha stage. I put out a...