-
-
Notifications
You must be signed in to change notification settings - Fork 148
Issues with [email protected] #337
Comments
Hi there @dignifiedquire - are you using Webpack 1, or 2? Something is freezing the exports of |
I am using "presets": [
[
"latest", {
"es2015": {
"modules": false
}
}
],
"stage-2",
"react"
], |
I know this isn't the most elegant solution, but can you try adding this alias? {
alias: {
'preact-compat': 'preact-compat/dist/preact-compat'
}
} I think it's something to do with the CommonJS proxy module re-exporting an ES Module - Webpack seems to be freezing something... somewhere (can't seem to find where). |
This works :) thank you |
Ok, that confirms it. Now I just need to figure out if it's Babel or Webpack doing the freezing. Other people will be running into this as libs switch over to shipping ES Modules. |
Had same issue, that fixed for me too
|
|
@developit sorry forget to mention its |
btw just realized with this hot reload is not working |
For sure - RHL is trying to patch a frozen exports object for some reason. Not sure what the best way to fix this would be, it's just a very odd behavior for RHL. |
@developit i'm having another issue with |
@garmjs might be a bubbling issue. If something up the DOM tree accidentally registered an |
So interesting enough, I have come back to trying and move my app to preact, but now I get an issue where the app is constantly rerendering if I use hot module reloading. If I remove |
Not sure, but RHL is on my list of things to figure out. I've never used it, all the apps I work on just use basic HMR, but I know people really want it. It's likely touching some internal stuff preact-compat doesn't emulate. |
This fix works except it then causes issues with using
|
@developit that suggestion works to fix that error, but then causes
|
I am trying to alias
react
topreact-compat
in my dev environment but running into the following issue:I am using the setup from https://github.com/preact-compat/react and aliasing with webpack.
The text was updated successfully, but these errors were encountered: