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

Use correct react native packager require paths #26

Closed
wants to merge 1 commit into from

Conversation

nevir
Copy link

@nevir nevir commented Sep 29, 2015

This follows Facebook's internal pathing for their private modules - and allows other packagers (such as react-native-webpack-server) to properly resolve these guys.

See magus/react-native-facebook-login#25 and mjohnston/react-native-webpack-server#87 for some background

This follows Facebook's internal pathing for their private modules - and allows other packagers (such as [react-native-webpack-server](https://github.com/mjohnston/react-native-webpack-server)) to properly resolve these guys.

See magus/react-native-facebook-login#25 and mjohnston/react-native-webpack-server#87 for some background
@oblador
Copy link
Owner

oblador commented Sep 29, 2015

Not sure this is the way to go since it's been officially discouraged and will throw packager warnings. It works for the moment, but might not in the future. There's an issue about exposing more stuff publicly, let's see where that lands.

Actually I've had plans to refactor the styling part to be more explicit but it will be a breaking change so I'm a bit reluctant. But I guess RN devs are pretty used to that by now haha. Don't think I've had a RN release that didn't break my app.

@oblador
Copy link
Owner

oblador commented Oct 13, 2015

Fixed in 0.8.0.

@oblador oblador closed this Oct 13, 2015
@nevir nevir deleted the patch-1 branch October 14, 2015 17:25
@nevir
Copy link
Author

nevir commented Oct 14, 2015

Awesome! Thanks

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.

None yet

2 participants