Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
[Discussion] Moving react-native-packager into a new repository. #13976
Here are some of the highlights from this half so far:
Next week we are planning to split react-native-packager off of React Native. We haven't been able to take enough care of open source requests around react-native-packager because of the sheer size of the react-native repository. We know there are a couple of long-standing issues and we'd like to finally address them in a smaller codebase that is easier to contribute to and easier to maintain:
What will change as a user of react-native?
What will change for maintainers of the react-native repo?
The new repository will require releases to be lined up with releases of react-native but we aim to make the publishing process simple.
What will change when sending Pull Requests to react-native?
Contributors will have to send pull requests to the new repository for react-native-packager.
What will change for engineers at Facebook?
We aren't changing our current workflow but we may change to use GitHub-first development for react-native-packager in the future.
Please let us know if you have any concerns. The team and I are happy to address them.
I want to start off by saying thanks to you and the rest of the React Native team for all your great work!
I had a quick question, where does the RN team stand with regards to packager alternatives like Haul?
I'm curious if there would be a benefit in there being 1 "blessed" packager that could cater to the community's needs (i.e., symbolic links, latest HMR, Webpack's ecosystem, etc.). Are there features currently in the packager that can't be implemented in Haul? Would it take too long for Haul to reach feature parity with the packager?
I'm curious as to what the RN team's thoughts are on these.
As for my own opinion, being working on packager, I'm happy there are alternatives such as Haul so that the community has more options depending on needs such as symlinks. I believe this is healthy for React Native to have alternative choices.
I think one of the main difference right now is performance, where Metro bundler/packager achieve higher incremental build performance. That makes sense as it's the reason we built it in the first place, but it also explains the limitations such as not supporting symlinks—we depend on
My wish is that anyone can break apart the code of packager and reassemble it in different ways so that there are never hard a constraint on what is or isn't possible.
EDIT: btw I stumbled on that old thread, linked from the
The impact on React Native users isn't quite zero — in fact, this is a breaking change.
The iOS pbxproj generated by
There's a lot of different PRs and commits supporting this switch, so perhaps I didn't see the Breaking Change announcement. Either way, I strongly recommend you include it in the release notes for 0.46.
tl;dr for other people in search of a solution:
If you're seeing this error during iOS builds...
...then you need to go into Xcode, click the root of your project, go to 'Build Phases', find the one that says 'React Native', then update the command to point to: