React v0.14 Beta 1 released
facebook.github.io
React v0.14 Beta 1 released
1–10 of 62 posts
Re: React v0.14 Beta 1 released
#2I think this is the crux -
> We think the true foundations of React are simply ideas of components and elements: being able to describe what you want to render in a declarative way. These are the pieces shared by all of these different packages (react-native, react-art, react-canvas, react-three). The parts of React specific to certain rendering targets aren't usually what we think of when we think of React.
I've not played with React-native yet (waiting for Android) but I feel this is a positive step towards their vision of "learn once, write anywhere". From the twitter updates it seems, Sebestian Markbage, gave a pretty cool talk on the same topic at ReactEurope yesterday. Can't wait to check that out. https://twitter.com/chantastic/status/616679794479112193
> To make this more clear and to make it easier to build more environments that React can render to, we're splitting the main react package into two: react and react-dom.
Great to see the react team responding positively to the developments in community and not being afraid to take hard decisions (like this one)
Lastly, if you're a web developer and deciding between going the 'web components' route or the React route, this announcement gives you, IMHO, an even more impetus to pick up React.
Re: React v0.14 Beta 1 released
#3I am using React and am very happy with it, however I worry about upgrading because of the interdependencies as well as how fast everything is moving in this space... Does anyone know when we'll be able to have a 1.0 release that we can assume stable for a few months and that react-xxx authors can make sure their modules are stable against.
Presumably the react/react-dom breaks all current third party packages for now?
Re: React v0.14 Beta 1 released
#4I am using React and am very happy with it, however I worry about upgrading because of the interdependencies as well as how fast everything is moving in this space... Does anyone know when we'll be able to have a 1.0 release that we can assume stable for a few months and that react-xxx authors can make sure their modules are stable against. Presumably the react/react-dom breaks all current third party packages for no…
Shouldn't do:
This release includes the old methods in the react package with a deprecation warning, but they'll be removed completely in 0.15
Re: React v0.14 Beta 1 released
#5tl;dr React (core) is evolving into a kind of component spec.
Sounds good!
If not already, react-dom will probably be easily replaceable by modules like virtual-dom?
Re: React v0.14 Beta 1 released
#6We're considering trying react for a new project, and just read about the adoption of Babel [1] instead of the internal transpiler previously used for JSX. One question: does this mean that JSX will be able to use ES6 syntax supported by Babel out of the box? If so, will this be the default for this new version of React?
I ask the questions also because we would really like to be able to use React with CoffeeScript, but, even if there are many solutions to do so, no one is supported by Facebook and we're worried about future compatibility. Is adopting Babel going to influence the ability to use React with CS?
[1] https://facebook.github.io/react/blog/2015/06/12/deprecating...
Re: React v0.14 Beta 1 released
#7We're considering trying react for a new project, and just read about the adoption of Babel [1] instead of the internal transpiler previously used for JSX. One question: does this mean that JSX will be able to use ES6 syntax supported by Babel out of the box? If so, will this be the default for this new version of React? I ask the questions also because we would really like to be able to use React with CoffeeScript,…
React's deprecation of JSTransform means that you will (whenever they completely remove it) need to actually use Babel to build your React JavaScript.
Re: React v0.14 Beta 1 released
#8We're considering trying react for a new project, and just read about the adoption of Babel [1] instead of the internal transpiler previously used for JSX. One question: does this mean that JSX will be able to use ES6 syntax supported by Babel out of the box? If so, will this be the default for this new version of React? I ask the questions also because we would really like to be able to use React with CoffeeScript,…
I've been using babel instead of the internal transpiler and yes you can use all the ES6 syntax out of the box.
I think the JSX transpiler was deprecated some time ago and pretty much all the react starter templates and examples have been using Babel.
I don't think adopting babel is going to compromise your use of coffeescript, in then babel is just transpiling down to old style javascript.
Re: React v0.14 Beta 1 released
#9We're considering trying react for a new project, and just read about the adoption of Babel [1] instead of the internal transpiler previously used for JSX. One question: does this mean that JSX will be able to use ES6 syntax supported by Babel out of the box? If so, will this be the default for this new version of React? I ask the questions also because we would really like to be able to use React with CoffeeScript,…
You don't need to use Babel, though we do recommend it. We're just no longer going to maintain our own JSX transformer since there's no point. (If you want just Babel's JSX transformation without any other features, that's possible too.)
There's a CoffeeScript JSX transformer here if you're interested:
https://github.com/jsdf/coffee-react
and we'll continue to support using React without JSX, and though we use Babel now internally, we compile React itself to ES5 before putting it on npm so you don't need to use Babel if you don't want to.
Re: React v0.14 Beta 1 released
#10I am using React and am very happy with it, however I worry about upgrading because of the interdependencies as well as how fast everything is moving in this space... Does anyone know when we'll be able to have a 1.0 release that we can assume stable for a few months and that react-xxx authors can make sure their modules are stable against. Presumably the react/react-dom breaks all current third party packages for no…
a 1.0 release that we can assume stable for a few months
Am i the only one getting a bit cynical that we're now hoping that a 1.0 is stable enough 'for a few months'?