Add support for creating a preact-compat build

[insin]

@developit's preact-compat is a drop-in way to try preact with a React app - if it's compatible with your app, having support for it in react-specific build commands would be an easy way to shave size off your production build.

The actual change here should be making the following tweaks to build-react-app.js and build-react.js:

• If a --preact flag is present, add this resolve.alias config to the base Webpack config
• If a --preact flag is present, don't configure React inline and constant element transforms for production builds

[developit]

You are a gentleman and a scholar.

[insin]

@developit is there anything in the code in the Gist below which would specifically be incompatible with preact-compat?

https://gist.github.com/insin/45b7f66e01628601c0cc6b79767b0e4f#file-app-js

Trying the --preact flag in the next branch with it and am getting this:

[developit]

@insin Sorry for the delay - use preact@beta (currently 5.x), this is fixed there.

[insin]

👍 got it working, but I had to fiddle with preact-compat's package.json in node_modules/ and delete its own installed version of preact to make it use my app's preact@beta, and for that not to be peer invalid (with npm2):

  "peerDependencies": {
    "preact": "* || ^5.1.0-beta.20",
    "proptypes": "*"
  },
  "dependencies": {
    "preact-render-to-string": "^2.6.1",
    "preact-svg": "^1.6.0"
  },

A dependency should usually be in either peerDependencies or dependencies/optionalDependencies, but not both as the latter will make it install its own version and the * version not matching prerelease versions makes it a pain when you need to be on the bleeding edge 😸

[developit]

Ah totally yeah, I need to remove it from optionalDependencies. Will try to tonight. Though I'm likely release preact 5 as the new mainline this week so the problem should go away.

[developit]

@insin Removed optionalDependencies from preact-compat and released as 1.10.0.