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

reletavise requires in compiled .flow files #118

Closed
zpao opened this issue Feb 25, 2016 · 10 comments
Closed

reletavise requires in compiled .flow files #118

zpao opened this issue Feb 25, 2016 · 10 comments

Comments

@zpao
Copy link
Member

zpao commented Feb 25, 2016

There's an issue right now where the result is that we basically force all indirect consumers of fbjs (eg using Relay) to use the haste system in their package or ignore things specifically. @mroch said we should be able to make this work with our projects and others by rewriting the requires in our generated flow files so they are relative while keeping the @providesModule headers.

@samwgoldman
Copy link
Member

mine

@zpao
Copy link
Member Author

zpao commented Feb 27, 2016

👍 we might need to upgrade Babel for this to work, at least the plan I had
was to just run through Babel with only the existing requires pouring we
use for js. But that's not possible right now to run through and only do
that with Babel 5 (at least in the 2 minutes I tried)

On Friday, February 26, 2016, Sam Goldman <notifications@github.com
javascript:_e(%7B%7D,'cvml','notifications@github.com');> wrote:

mine


Reply to this email directly or view it on GitHub
#118 (comment).

@samwgoldman
Copy link
Member

Thanks—pretty eager to get this fix out. Does a Babel upgrade have any blockers to landing, other than just getting it to work locally?

@zpao
Copy link
Member Author

zpao commented Feb 27, 2016

I think the only thing I'd check is diff the JS files before and after to make sure we don't slip anything in there we don't expect. We have all the plugins ported already. And actually we're just about to do the upgrade for React in facebook/react#6113

@sebmck
Copy link
Contributor

sebmck commented Feb 27, 2016

Do we have anything else that uses Babel 5? I want to kill it with fire.

@samwgoldman
Copy link
Member

@kittens If you're on a tear and want to take this one, go for it. I think you'll be able to turn it around faster than me. :)

@zpao
Copy link
Member Author

zpao commented Feb 27, 2016

Literally everything else besides React Native still uses 5.

@sebmck
Copy link
Contributor

sebmck commented Feb 27, 2016

Like what? React Native, Relay, www, and now React all use Babel 6.

@zpao
Copy link
Member Author

zpao commented Feb 27, 2016

Relay doesn't use Babel 6, nor does flux nor draft. Nothing using
fbjs-scripts did until today (all need the dev plugin you just wrote)

On Friday, February 26, 2016, Sebastian McKenzie notifications@github.com
wrote:

Like what? React Native, Relay, www, and now React all use Babel 6.


Reply to this email directly or view it on GitHub
#118 (comment).

@sebmck
Copy link
Contributor

sebmck commented Feb 27, 2016

Thanks for the list, I'll upgrade all of those next week..

On Saturday, 27 February 2016, Paul O’Shannessy notifications@github.com
wrote:

Relay doesn't use Babel 6, nor does flux nor draft. Nothing using
fbjs-scripts did until today (all need the dev plugin you just wrote)

On Friday, February 26, 2016, Sebastian McKenzie <notifications@github.com
javascript:_e(%7B%7D,'cvml','notifications@github.com');>
wrote:

Like what? React Native, Relay, www, and now React all use Babel 6.


Reply to this email directly or view it on GitHub
#118 (comment).


Reply to this email directly or view it on GitHub
#118 (comment).

Sebastian McKenzie

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

No branches or pull requests

3 participants