Skip to content

Conversation

@janicduplessis
Copy link
Contributor

Summary:

Some legacy apis were removed in the latest metro release. The only one that seem to be affecting here is createBlacklist. we import it from the metro-config package instead. See facebook/metro@871cafb#diff-82e93cde29a5080883ceae93070af8feL13

Test Plan:

Tested that running the metro server works with metro 0.58.0

@thymikee
Copy link
Member

We have a PR open currently that bumps Metro to 0.57, see #864. When updating it I remember I verified the default blacklist and there was no need for us to actually use it. Can you please have a look?

@janicduplessis
Copy link
Contributor Author

janicduplessis commented Jan 21, 2020

@thymikee This is only required for metro 0.58.0 that was released a few days ago. I think there is no harm in updating now since the blacklist file exists even in older metro versions.

EDIT: Sorry I didn't read that right. Checked the PR and it makes sense, this isn't needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants