Skip to content
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

0.36.0 not respecting blacklistRE in rn-cli.config.js #10673

Closed
rob-64 opened this issue Nov 1, 2016 · 2 comments
Closed

0.36.0 not respecting blacklistRE in rn-cli.config.js #10673

rob-64 opened this issue Nov 1, 2016 · 2 comments
Labels
Resolution: Locked This issue was locked by the bot.

Comments

@rob-64
Copy link

rob-64 commented Nov 1, 2016

Description

0.36.0 not respecting blacklistRE in rn-cli.config.js

I have a git submodule at named server, and the node_modules folder under it is ignored correctly with 0.35.0 with the following, but when i upgrade to 0.36.0 the package manager is now finding duplicate modules.

var blacklist = require('react-native/packager/blacklist');

var config = {
    getBlacklistRE(platform) {
        return blacklist(platform, [
            /server\/.*/
        ]);
    }
};

module.exports = config;

Additional Information

  • React Native version: 0.36.0
  • Platform: both
  • Operating System: el capitan and win10
@ide
Copy link
Contributor

ide commented Nov 1, 2016

The blacklist functions signature changed. Drop the platform argument.

@Venryx
Copy link
Contributor

Venryx commented Jun 5, 2017

An error should really be thrown when someone calls blacklist using the old signature.

This has caused problems, as it silently causes the blacklist system to fail in projects -- which is seemingly the only way to solve issues such as this: #9136

Because I didn't know this, and because using the wrong signature just failed silently, the build error in the thread above (well, one similar) has plagued me for weeks, wasting me a lot of time as I had to keep doing a workaround of deleting the entire build folder each time I ran "react-native run-android".

@facebook facebook locked as resolved and limited conversation to collaborators May 24, 2018
@react-native-bot react-native-bot added the Resolution: Locked This issue was locked by the bot. label Jul 19, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Resolution: Locked This issue was locked by the bot.
Projects
None yet
Development

No branches or pull requests

4 participants