How do I setup Babel 6 with Node JS to use ES6 in my Server Side code?

1. This answer uses this simple directory structure

   project/server/src/index.js => your server file

   project/server/dist/ => where babel will put your transpiled file

2. Install babel dependencies

   npm install -g babel nodemon

   npm install --save-dev babel-core babel-preset-es2015

3. Add these npm scripts to your package.json file

   "scripts": { "compile": "babel server/src --out-dir server/dist", "server": "nodemon server/dist/index.js }

4. Create a .babelrc file in your project root directory

   { "presets": "es2015" }

5. Transpile your directory with

   npm run compile

6. Run your server with

   npm run server

1.a What Preset is needed?

You will need to install Babel firstly with npm install babel-core --save-dev in the root directory of your project using a Terminal window like Command Prompt.

Once installed, you will need to install the es2015 preset with npm install babel-preset-es2015 --save-dev. Babel-Core is Promises/A+ Compliant but not ideal for usage due to poor error handling so a library such as Bluebird should be used instead for this purpose. In order to transpile, babel-core will still need to be installed and es2015 enables ES6->ES5 transpiling so you can use fancy things like let and const etc.

1.b Where to put require("babel-core");?

instead, use require("babel-core/register"); and place it inside your Entry file typically called, "server.js". The server.js file will need to use CommonJS (ES5) exclusively.

By using the "require" statement it will apply all relevant transforms to all code being required into the Entry file and all files being required/included into those files.

You point to the Entry file inside package.json under the "main": section.

Package.json is created when you initialise the project with npm init at the root directory of your project inside the Terminal Window

One approach to this would be :

• Entry File - server.js
• server.js - requires {babel-core and the main ES6 file : config.js/jsx/es6/es}
• config.es6 - uses ES6 and has includes(requires) for all other project files that can also use ES6 as they get transpiled by being loaded into the "config" file which is being directly transpiled by babel-core.

2. What is .babelrc?

.babelrc is the filename and should be placed in the same folder as your package.json file (normally the root directory) and will automatically "load" when babel-core is required to determine which preset(s) or plugins are to be used.

Inside .babelrc , you will need to add the following code :

{
  "presets": ["es2015"]
}

3. pg-promise Testing Section

A direct quote from the developer recently answered this

You do not need to worry about steps in the Tests, use only the steps in the install. The one in tests relates to the dev dependency installation, in order to run tests. The pg-promise can work with any promise library compliant with Promises/A+ spec.

4. Standard File/Folder Structure for Server Side Projects?

There is no standard way to achieve this task as each project has unique demands. A good starting point would be to place the Entry file in the project root directory, the ES6 Config file in a "scripts" or "src" sub-folder and individual components in folders below that.

e.g.

• ROOT/server.js
• ROOT/src/config.es6
• ROOT/src/component1/files.es6
• ROOT/src/component2/files.es6

With this in place, Babel will successfully transpile all ES6 to ES5 and enable support of A+ compliant promises.

To begin using the node.js webserver This Guide provides a bit more insight and in the context of this answer the code shown would be placed into the ES6 config.es6 file and the following code would go into the Entry server.js file :

require("babel-core/register");
require("./src/config.es6");

The process for building Isomorphic web applications is different to this and would likely use things like grunt, gulp, webpack, babel-loader etc another example of which can be Found Here.

This answer is the combination of several key points provided by other answers to this question as well as contributions from experienced developers and my own personal research and testing. Thank you to all who assisted in the production of this answer.