-
Notifications
You must be signed in to change notification settings - Fork 0
2015 04 24
Attendees:
- @amasad
- @graue
- @jsfb
- @pieterv
- @spicyj
- @tomocchino
- @zpao
Agenda
- On Call Debrief
- Week In Review / Project Updates
- 0.13.3
- React CLI
This is a new segment. The goal is to make sure we surface larger issues as they come up on GitHub, as well as to make sure everybody is in the loop.
This week's oncall: @spicyj
There were reports of incorrect context warnings in React Native. After investigating, it turned out that we were double initializing context. This only affects 0.13.x as master has switched to parent context completely. There is a PR with the fix, which we'll take in 0.13.3. See https://github.com/facebook/react/issues/3709 for more.
There's been some activity in server-side rendering performance explorations. Thanks to @mridgway for starting this and submitting pull requests.
There was a PR for namespaced attribute support that is much more complete than past attempts, we may be able to take this one.
- @zpao shipping jstransform @ v11 today, will cut over React repo soon after
- Some discussion around Babel, we can try switching over the React build process soon (@spicyj)
- @pieterv has already started that process for fixed-data-table
(no big updates on other projects)
There are a couple things that would be good to ship. We'll probably do that in the next week.
- Fix for double context initialization
- Fix for context in shallow testing
@amasad brought up that it's still really hard to start a new project using React. There are a lot of decisions to make and things to look up.
- module system
- what polyfills are needed
- source code transforms and sourcemaps
- how does data work
- where should files live in an app
- what does testing look like
- what should be used for CSS
- how do I route requests
- what does deployment look like
ember-cli does a really good job of helping people figure most of this out. React doesn't have anything like that.
A few things were discussed, we won't build the right tool for everybody on every server architecture but we can start making some best efforts. There are things to learn from that exist including React Native CLI, Ember CLI, and some React starter kits built by the community. @amasad & @pieterv to collaborate.
Somebody already owns the react-cli package on npm. We'll be deprecating react-tools soon so can perhaps just use that.