-
Notifications
You must be signed in to change notification settings - Fork 625
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
Haste module overrides across packages #188
Comments
Related to facebook/react-native#19953 |
cc @rubennorte; how does the Haste implementation shipped by default works with |
All modules in |
I just saw |
Summary: We removed support for providesModule annotations and maintained support for Haste names in installed modules via `providesModuleNodeModules`, but our default `hasteImpl` doesn't take them into account. We need to find a better way to override core components from plugins but meanwhile this adds an exception for react-native-windows in the default `hasteImpl` to unblock their upgrade to the latest RC. Fixes facebook/metro#188 Reviewed By: mjesun Differential Revision: D8695207 fbshipit-source-id: a3a8303715820a156b2338438b7f9186e1f71396
Summary: We removed support for providesModule annotations and maintained support for Haste names in installed modules via `providesModuleNodeModules`, but our default `hasteImpl` doesn't take them into account. We need to find a better way to override core components from plugins but meanwhile this adds an exception for react-native-windows in the default `hasteImpl` to unblock their upgrade to the latest RC. Fixes facebook/metro#188 Reviewed By: mjesun Differential Revision: D8695207 fbshipit-source-id: 24119fe25257ec92504d0695b1b9056dfbee2774
…acebook#20007) Summary: Closes facebook#20007 We removed support for providesModule annotations and maintained support for Haste names in installed modules via `providesModuleNodeModules`, but our default `hasteImpl` doesn't take them into account. We need to find a better way to override core components from plugins but meanwhile this adds an exception for react-native-windows in the default `hasteImpl` to unblock their upgrade to the latest RC. Fixes facebook/metro#188 Reviewed By: mjesun Differential Revision: D8695207 fbshipit-source-id: e70c8649543ebfcba40f934451faf33548c3d20a
…20007) Summary: Closes #20007 We removed support for providesModule annotations and maintained support for Haste names in installed modules via `providesModuleNodeModules`, but our default `hasteImpl` doesn't take them into account. We need to find a better way to override core components from plugins but meanwhile this adds an exception for react-native-windows in the default `hasteImpl` to unblock their upgrade to the latest RC. Fixes facebook/metro#188 Reviewed By: mjesun Differential Revision: D8695207 fbshipit-source-id: 2ad6cb1e93e600880a148776ac45f6ebd7d205d3
Same problem, I'm not alone.
|
@Slexom Also same here. ` "devDependencies": { .babelrc { |
…20007) Summary: Closes facebook/react-native#20007 We removed support for providesModule annotations and maintained support for Haste names in installed modules via `providesModuleNodeModules`, but our default `hasteImpl` doesn't take them into account. We need to find a better way to override core components from plugins but meanwhile this adds an exception for react-native-windows in the default `hasteImpl` to unblock their upgrade to the latest RC. Fixes facebook/metro#188 Reviewed By: mjesun Differential Revision: D8695207 fbshipit-source-id: 2ad6cb1e93e600880a148776ac45f6ebd7d205d3
__ |
Do you want to request a feature or report a bug?
Bug
What is the current behavior?
react-native-windows
overrides haste modules inreact-native
, currently using the@providesModule
attribute. For example, theScrollView
module inreact-native
has behavior that limits it to iOS and Android, we we override the module inreact-native-windows
here.Prior to
react-native
0.56.0 RC (which moved tometro
0.38), this behavior worked as expected. Now, the haste module overrides for windows no longer seem to get resolved. Specifically, I get the following error:Please note - the
AccessibiltyInfo
module just happens to be the first module in the dependency graph that we provide a*.windows.js
override for, so it has nothing to do with that module specifically.If the current behavior is a bug, please provide the steps to reproduce and a minimal repository on GitHub that we can
yarn install
andyarn test
.A very simple test that repos (on both Windows and Mac):
What is the expected behavior?
The expected behavior is that a valid bundle will be generated for the windows platform moniker, with the correct module overrides being used from the
react-native-windows
package.Please provide your exact Metro configuration and mention your Metro, node, yarn/npm version and operating system.
The text was updated successfully, but these errors were encountered: