Vadims Daleckis

Lets go! I think `id` will probably not going to be useful, but `numChildren` is very handy, so indeed the forks/indices can be allocated in one pass.

Minor todos: - [x] Do not include block text in first inline element. - [ ] Tests - [ ] Readme - [ ] Remove empty leading inlines - [...

You could export a `spyfs` object that allows to mock, intercept and listen to file system operations. ```js import fs, {spyfs} from 'jest-plugin-fs'; jest.mock('fs', () => require('jest-plugin-fs/mock')); describe('FileWriter', () =>...

You can, but it is not just about listening for mock being called. You can also implement a mock or fail some method. Also if you mock a method it...

I like the idea of custom matchers. Is *custom matchers* something supported by Jest? Or we can just bolt them on `expect` method? I'm thinking it might have to be...

Does this RFC suggest that React would move around the actual DOM nodes? Is it technically possible? For example, if one of the child node was a playing `` element,...

> ...if you reparented a video with a controlled `Playing` attribute then even if the browser stopped it the controlled nature would make it resume after it is reparented... I...

I guess, for React just re-parenting and leaving it up to the user to deal with consequence is fine as long as it is opt-in. Here is a short list...

Example: ```js const className = rule({ background: { color: 'green', image: 'url(image.jpg)', position: [0, 0], repeat: 'no-repeat' }, }); ```

Yeah, currently `cssom` and `vcssom` addons are completely separate. But, I guess, it does make sense to integrate them with the rest of the addons. [This line](https://github.com/streamich/nano-css/blob/master/addon/vcssom.js#L28) should be changed...