-
Notifications
You must be signed in to change notification settings - Fork 68
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ReferenceError: isPlainObject is not defined #31
Comments
I'm not really sure as I use browserify instead of webpack. Could you provide a gist of the relevant post-webpack code? "this" should be undefined (or the global object) in any IIFE, which all commonJS modules are wrapped in, so I wouldn't expect to, nor accept, using "this" anywhere. |
@jonaswindey hey, I'm having exactly the same issue here. Did you find any workaround or solution? |
@danderu no, I finally used react-intl which doesn't rely on counterpart. Let me know if you find a workaround though. |
I had the same problem (using React, mobersvable-react & extend). I finally found out that it was my version of extend that was not up to date. I used 2.0 instead of 3.0. Hope it can help others |
I'm going to close this unless a reproducible test case can be provided. |
I have a very strange bug on Chrome which throws this error when my development tools aren't open.
I'm using webpack + react + counterpart (which requires this module).
The weird thing is that when I open my development tools, the method isPlainObject is clearly defined, but not when it's closed.
On Safari/FF everything works. It seems like a scope issue when requiring this module via webpack that isPlainObject should be called like _this.isPlainObject and exposing this as _this in the top of the index.js.
Any suggestions?
The text was updated successfully, but these errors were encountered: