News for hackers. Stuff that matters.
Re:Explaining React's license by WalterSear on Saturday August 19, 2017 @12:46AM (#15051732)
Could anyone with experience porting from one to the other let us know how it went?
Re:Explaining React's license by gedy on Saturday August 19, 2017 @02:58AM (#15052082)
For many codebases, Preact can be use simple as:

    npm i -S preact preact-compat
then add this to webpack config:

    {
      "resolve": {
        "alias": {
          "react": "preact-compat",
          "react-dom": "preact-compat"
        }
      }
    }
https://preactjs.com/guide/switching-to-preact
Re:Explaining React's license by bpicolo on Saturday August 19, 2017 @09:20AM (#15053194)
The tricky part is probably testing. I don't think e.g. jest (or maybe it was enzyme?) supports alternative implementations quite yet, though they were working on it...that was true months ago though.

If you're starting from scratch pretty easy though, sure. But that assumption is all too widespread in the JS ecosystem these days : (

Re:Explaining React's license by gedy on Saturday August 19, 2017 @01:33PM (#15054538)
We saw no problems with Mocha & Enzyme, can't comment on Jest.
Re:Explaining React's license by WalterSear on Saturday August 19, 2017 @03:10PM (#15055045)
woot.

brb :)