Michael

Explanation: https://github.com/gruntjs/grunt-contrib-requirejs/issues/41#issuecomment-52129662

Indeed it does as evidenced by this bug report, #5623 and #5854. I'm suggesting that this ordering issue between preset-env & preset-typescript be explicitly called out in the docs of...

I ended up fixing this by using the [React.ElementConfig](https://flow.org/en/docs/react/hoc/#toc-supporting-defaultprops-with-react-elementconfig) type introduced in 0.63 of flow (and fixed properly in 0.64).

@crisu83 I ended up just using React.ElementConfig itself without the HOC type from this project so my solution won't be relevant to this project. I just followed the docs on...

+1, doesn't work.

Well, the project is written in typescript and emits declaration files, so it is the recommended approach to expose these types directly for consumers, see https://www.typescriptlang.org/docs/handbook/declaration-files/publishing.html. I'm consuming yalc via...

> Ah, the documentation is worded poorly, but it's still correct. I disagree, the documentation is incorrect for a couple of reasons: 1. The option only mentions globs without slashes,...

`resolutions` dependencies not updating yarn.lock is making it harder for me to parse yarn.lock as I now need to also cross-reference the `resolutions` field to find missing ranges in yarn.lock....

Not sure why #363 wasn't landed to fix this issue.

One should not have to reattach the element to the DOM upon each render call. This needs to be documented, especially now that #363 has been landed.