-
Notifications
You must be signed in to change notification settings - Fork 186
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
AliasFieldPlugin.apply + lodash: resolving the wrong toString #118
Comments
I have the same error using sjcl in a ReactJS app (webpack). Works fine in React Native (Babel) though. |
Solved it by replacing sjcl with jwt-decode because I only need to deal with JWT Tokens |
Send a PR. Object.prototype.hasOwnProperty.call(someObject, someProperty) |
@sokra Sorry, I didn't understand what you meant. What am I supposed to do with |
Could this be causing jupyterlab/jupyter-renderers#91? |
@domoritz Almost. In your case |
Has any progress been made? |
Need reproducible test repo, thanks! |
The only workaround I found for this issue is adding: "browser": {
"crypto": true
} to my |
Is @sentenza workaround working for everyone ? Didnt solve it for me.. |
@ArThoX I think you may just need to pass some path string instead of a boolean |
I think here the problem with |
I think we need to check hasOwnProperty to avoid receiving Object prototype methods |
Yep, just want to find broken example |
I think this will break reliably - a couple helpers in {
"dependencies": {
"@pmmmwh/react-refresh-webpack-plugin": "0.5.x",
"expo": "*"
},
"scripts": {
"start": "expo web"
}
} The issue creeps in via |
yeah, this should be fixed.. |
When resolving
"./toString"
fromlodash
, data2 on AliasFieldPlugin.js is removing the./
from"./toString"
oflodash
, causingfieldData
to get the default functiontoString()
of every object.Resulting in:
Something I couldn't find is: Who is calling the
AliasFieldPlugin
?A simple and easy fix was to do something like this:
OBS: I'm also using Haul, which uses an older version of
webpack
, but still the latest version ofenhanced-resolve
The text was updated successfully, but these errors were encountered: