A number of changes in this look great.
I always found the extra <span> tags to be a bit frustrating.
Are we able to just run meteor npm install --save react react-dom to use this latest version?
I am not able to test this for a couple more hours - away from dev machine, keen to hear if its working with Meteor
We are now using document.createElement instead of setting innerHTML when mounting components. This allows us to get rid of the data-reactid attribute on every node and make the DOM lighter. Using document.createElement is also faster in modern browsers and fixes a number of edge cases related to SVG elements and running multiple copies of React on the same page.
Rejoice! \o/ Never did like all these extra attributes littering my DOM
While this isn’t directly related to the release, we understand that in order to receive more community contributions like Michael’s, we need to communicate our goals and priorities more openly, and review pull requests more decisively. As a first step towards this, we started publishing React core team weekly meeting notes again.
I just tried to do the update and it won’t update beyond 0.14.8, I am guessing that is because of the dependencies listed in my package.json file. I think they are limiting the updates because its gone from 0.14 to 15.0…
I’m not super familiar with how this all works with NPM, should I manually update the json file to request 15.0?
I am guessing if we move to use react komposer or something that doesn’t use mixins we are good?
I use the mixin currently but might just use this as an opp to migrate to the compose way of doing things.
When you say “bombs out”, do you just mean “displays this warning”? Because it does work with 15.0.0 AFAICT, but (sensibly IMO, when you consider things like mixins could have been deprecated / removed) only guarantees to work with 0.14.x, and thus warns you otherwise.
If there is an issue with it and React 15, please open an issue (and post it here too ).
I’ll release a new version of the react packages tomorrow that peer-depend on react-15.
Sorry, bad wording - not quite bombs out Just strange behavior. Though, thinking about it again, that could really be any package that’s suddenly not compatible with React v15. That’s odd though… I don’t think there were any breaking changes in this version. And I wasn’t using any deprecated stuff.
I’ll see if I can hone in on the issue, and I’ll post my findings here.
Ok, things are fine! Whew. The only thing is a couple warnings which I don’t understand.
Warning: Input elements must be either controlled or uncontrolled (specify either the checked prop, or the defaultChecked prop, but not both). Decide between using a controlled or uncontrolled input element and remove one of these props. More info: https://fb.me/react-controlled-components
Warning: ToggleCheckBoxOutlineBlank: key is not a prop. Trying to access it will result in undefined being returned. If you need to access the same value within the child component, you should pass it as a different prop. (https://fb.me/react-special-props)
The problem is that Meteor 1.3 has just been dumping out errors pointing to modules.js?hash=xxxxx and so it’s extremely difficult to trace these.
People should also take note that react-tap-event-plugin is broken under React v15. Dan Abramov made a pull request but it hasn’t been published yet. I may just incorporate these changes locally for now.
I’ve updated to v15.0.0 and all seems well… Granted I get a warning in my console much like @mordrax, but it all works fine.
The only thing that royally complains is NPM for the react-mounter package by @arunoda, as they have changed to semantic versioning, it doesn’t like the new version very much at all. But it too, still works.