koa-connect | Use connect and express middleware in koa | Application Framework library

All plugins are moved to @babel scope with Babel 7. To update your package.json, you need to rename all your plugins and presets accordingly, using the ^7.0.0 version.

You can find all the official plugins here.

If you open up a plugin that interests you, you will see that all of them are renamed to, for example: @babel/plugin-proposal-class-properties.

• babel-polyfill => @babel/polyfill
• babel-core => @babel/core
• babel-plugin-transform-class-properties => @babel/plugin-proposal-class-properties
• you get the idea. babel- is now @babel/ and some plugins are prefixed with proposal.

babel-plugin-emotion is of course not an official plugin so it stays the same, as well as babel-loader. For all other plugins make sure to compare the names with the new naming on the link provided above. Open each plugin's folder to see the new name beginning with @babel/.

The same naming now applies to .babelrc file (or babel config in general), and I suggest you do not use the shorthand naming but include the full package nam of plugins and presets in your babel config:

You can't set! There are only those 3 modes available. Those modes doesn't need to be used for different envieronments, they are just a way that webpack found to apply certain defaults to your build based on the env. If you think that your Q&A should behave (actually it should) like prod, just put it as prod.

TL;TR: mode has nothing to do with env, they are just a way to apply certain defaults to your build.

To have access to process.env.NODE_ENV on the frontend code, you have to use DefinePlugin:

If you still need to tweak a ubuntu:trusty image, this Dockerfile, inspired by offical docker hub node:latest has a functional yarn working.