-
Notifications
You must be signed in to change notification settings - Fork 385
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
Uncaught (in promise) TypeError: object is not a function #407
Comments
@akim-mcmath I assume you're using Chrome Canary? This is a trivial console warning that you can absolutely ignore and won't affect your program in any way. That said, it should have been resolved by v0.34.3 (and was present in v0.34.2). If you could somehow narrow it down to a line in fwiw, I can't reproduce this in Chrome or Chrome Canary with v0.34.3. |
@ljharb Thanks for your reply. I'm using Chrome 48.0.2564 on OSX actually. I also neglected to mention that the program seemed to be working fine otherwise. If it's trivial, then you don't need to worry about it for my sake. However, I seem to have found the source of the warning on line 2562 of v0.34.3. I don't know why it's not reproducible. Could it be specific to OSX? In any case, I believe I've found a fix, which I can submit if you would like. |
Thanks, merged! |
You're welcome. Thank you for your work on this project and your quick resolution of this issue. |
np! released as v0.34.4. |
I'm getting this unhelpful error message in Chrome after upgrading to [email protected].
I'm using this as part of an Angular 2 application, bundled with Webpack. When I downgrade to [email protected] the error goes away. And I'm not getting any errors in Firefox.
The text was updated successfully, but these errors were encountered: