-
Notifications
You must be signed in to change notification settings - Fork 634
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
blacklist completely ignored #58
Comments
For context, I'm trying to blacklist because of invertase/react-native-firebase#414 (comment). |
Ok, I think running with |
We are now considering the blacklist in the latest version of Metro. |
@cpojer You mean considering the blacklist for cache invalidation? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Do you want to request a feature or report a bug?
bug
What is the current behavior?
The file blacklist is ignored.
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
.With react-native v0.48.3
init
a new project and add arn-cli.config.js
file to the root directory:Now, run
react-native run-ios
the packager will open up print the message and still bundle everything!A cursory look through the source code did not uncover any places where the
blacklistRE
option was ever actually used in the code. I couldn't find any tests forblacklistRE
either.What is the expected behavior?
For the blacklist to work.
Please provide your exact metro-bundler configuration and mention your metro-bundler, node, yarn/npm version and operating system.
metro-bundler 0.11.0
react-native 0.48.3
yarn 0.17.2
macOS
The text was updated successfully, but these errors were encountered: