Create-react-context v0.2.3 licence terms deny use on certain organizations.

[jkarttunen]

Is your feature request related to a problem? Please describe.
create-react-context v0.2.3 licence prohibits usage of CRC for certain organizations.
Even though the licence terms have been updated, the version has not been incremented and npm servers the old licence version.

Describe the solution you'd like
Can we use the latest commit of crc, instead of the npm published one?
Or update Reacti18next licence terms to match CRC licence.

Describe alternatives you've considered
Or fork crc and publish on npm.

[jamuhl]

jamiebuilds/create-react-context@f31c9ed#r31551322

hopefully we get a version 0.2.4 - would be prefer to just bump that instead of forking.

Alternative would be removing the polyfill and leave that to userland. Will give them some time to publish and if no response will consider that.

[rhinoceraptor]

Are there any plans to just require React 16.3 and use the new React context API?

[jamuhl]

@rhinoceraptor yes that is the fallback plan for v9

[jamuhl]

removed create-react-context in [email protected] -> upgrade of react to v16.3 needed (or polyfill in userland)