Release 0.9.0

[frontsideair]

Can we have a release before 0.9.0? #1309 is pretty important to me but I see there are a lot of issues within the 0.9.0 tag. Or can we postpone them after 0.9.0?

[gaearon]

Yea, the plan is to move the more complex issues until 0.10.
I plan to cut 0.9 some time this or the next week.

[joaosoares]

Is there an estimate on the release of 0.9.0? My team is using flow extensively and the tests integration would be very helpful for us.

[gaearon]

We'll delay Flow integration until 0.10 alpha which would be out very soon after 0.9.0.

I'm busy with React right now but I know @Timer offered help cutting 0.9.0. So I'm happy to take him up on that offer :-) There's a few things we need to discuss regarding it, happy to do it here or in a separate issue.

[joaosoares]

Thank you for the answer!

[frontsideair]

You can do this @Timer!

By the way, is there a way to use my fork or a commit of react-scripts I'd like in my project? npm allows using a git repo as a package but in this case, I think it won't work due to the monorepo setup. If there's a way I'm missing, please let me know.

[gaearon]

create-react-app myapp --scripts-version my-react-scripts

This?

[frontsideair]

Like that, but I guess I should either publish my form on npm or provide a .tgz which feels a bit overkill since my patch is already merged.

[gaearon]

Sorry, I don't have a better solution—we're hitting the limits of what npm can do.

[frontsideair]

No problem; I guess the main problem is that the npm package and the repo don't mean the same thing. One reason is the monorepo setup; there isn't a one-to-one relationship with the repo and generated npm packages. Another other reason would be prepublish hooks, but as far as I can see react-scripts doesn't use it.

Maybe creating a multi-repo fork would work for me, but I don't see how I could keep it synchronized. I previously suggested having a @next npm tag (or having different release stages) but that'd just make error reporting harder. :/

[Timer]

Let's try to cut it today!

I'll be working on this shortly -- anyone's review would be appreciated:

• Build exit codes
• Make ./ an official solution
  • Document it
• Doc improvements
• PUBLIC_URL support via Add support for PUBLIC_URL env variable #937
  • polish
• Make all vars accessiable in index.html #1440
• Document all environment variables in an advanced section

[Timer]

Hey guys, sorry to disappoint but I don't think it's going to happen today.

Build exit codes and PUBLIC_URL support have some pending changes, and ./ is blocked by PUBLIC_URL.

[Timer]

0.9.0 has been released. Please let me know if you encounter any bugs.

[existentialism]

Nice work @Timer!

[Timer]

Thank you, @existentialism!

[frontsideair]

Works like a charm, thanks @Timer!

[Timer]

That's reassuring! Thanks @frontsideair.