:fire: Quick setup for performance orientated, offline-first React.js applications featuring Redux, hot-reloading, PostCSS, react-router, ServiceWorker, AppCache, FontFaceObserver and Mocha.
Anyone, in combination with semantic ui in the react-boilerplate (https://react.semantic-ui.com/usage), I executed the yarn add semantic-ui-react in the root directory of the react-boilerplate
There was an error:
Error /home/atom/FormalProject/react-boilerplate/node_modules/pngquant-bin: Command failed.
Exit code: 1
Command: node lib/install.js
Arguments:
Directory: /home/atom/FormalProject/react-boilerplate/node_modules/pngquant-bin
Output:
⚠ The /home/atom/FormalProject/react-boilerplate/node_modules/pngquant-bin/vendor/pngquant binary doesn't seem to work correctly
Png pngquant pre-build test failed
i compiling from source
Png pngquant pre-build test passed successfully
✖ Error: pngquant failed to build, make sure that libpng-dev is installed
I would like to set NODE_ENV to stage so that my code can select a different api endpoint. I would like to test this with a production build. I thought I could do this in the package.json file:
"build:stg": "cross-env NODE_ENV=stage webpack --config internals/webpack/webpack.prod.babel.js --color -p --progress --hide-modules --display-optimization-bailout"
webpack would do a production build with the NODE_ENV set to stage. In my webpack.base.babel.js I have this
new webpack.DefinePlugin({
'process.env': {
NODE_ENV: JSON.stringify(process.env.NODE_ENV),
so when my webpack production configurations uses the base, I thought it would set process.env.NODE_ENV to stage. However, when I console.log(process.env.NODE_ENV) it in my app, I get production. Is this being set anywhere else in the webpack config files? I can't seem to find it.
