Closed almoraleslopez closed 9 years ago
From the errors this seems like an error with the dependency object.assign; and then a transitive dependency on object-keys. There are no open issues or reported issues for these libraries that reference these errors or webpack. However, this library is using an old version of object.assign so I'll bump that and see if it helps you. I'm using browserify and am not seeing these issues.
Updated all deps and bumped lib a minor version: 4.2.0 Not sure it will fix this issue but it may help.
Thanks @jurassix - Update applied but warnings still appearing
Which version of Joi are you using? Have you read through #17 to see if this is a webpack/Joi issue?
Latest stable version.
I got those errors and found a workaround for that issue in webpack config file.
// Added this workaround for missing module using Joi with React: See https://github.com/hapijs/joi/issues/528 and https://github.com/ReFiManager/ReFiManager/commit/36ee0576e27552a88d6622aaa00d9a41567bdce7
node: {
dns: "empty",
net: "empty"
}
Anyway, I've gone with a manual validation workaround for my requirement. But your module looks great and will try it.
Ok closing this issue as a webpack/joi issue. Please reopen if more investigation is needed.
Hi,
im using browserify and i also get the warning messages. any thoughts?
i have joi 6.5 installed. thanks.
Hello.
I have 2 warnings in the console (client side).
I use webpack and gulp-webpack. Updated both of them to last stable versions.
Following the warning I have this file index.js