-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
[Expo 49] Module not found: Can't resolve 'normalize-css-color' #5772
Comments
npm install normalize-css-color |
Same issue here after upgrading |
Same issue here trying to upgrade my repo from EXPO 48 to EXPO 49. |
Getting same error after upgrading Expo Sdk to 49. |
I did yarn add normalize-css-colors and it works Side note: there is a typo in native-base node_modules/native-base/lib/commonjs/utils/react-native-web-fucntions |
It could be meanwhile solution, but I think install "not-used" dependencies in a project could be a fine solution for anyone... |
-yarn add normalize-css-colors
+yarn add normalize-css-color A little adjust for me, the library must be is in singular instead of plural when running yarn. |
Regardless, the fix here should be for NativeBase to include a dependency on the package that it is using, instead of assuming that a peer dependency brings it in. In this case, my recommendation would be to add a dependency on In the meantime, for anyone upgrading RNW to 0.19.6 and beyond, you have two options:
// webpack.config.js
module.exports = {
resolve: {
alias: {
"react-native$": "react-native-web",
"normalize-css-color": "@react-native/normalize-color",
// ... any other aliases
}
// ... any other `resolve` config
},
// .. other config
}; |
Description
I started a simple project with Expo 49 and installed "nativebase" normally, but when trying to open the project on the web, this error Module not found: Can't resolve 'normalize-css-color' appeared
CodeSandbox/Snack link
Snack doesn't have Expo 49
Steps to reproduce
NativeBase Version
^3.4.28
Platform
Other Platform
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered: