Using ES6 with npm today

Re:Using ES6 with npm today by usagimaru on Friday February 27, 2015 @09:26AM (#9118952)

The transpilers will compile the module into an object you can require normally. The default export is under { "default": ... } and the other exported properties are under their exported names.

The real fun part is going the other direction: using non-ES6 modules inside ES6 code. Using 6to5ify (now babelify), I had the issue that I couldn't access the `exports` variable, only properties on it.

[ Parent | on HN ]

Re:Using ES6 with npm today by jallardice on Friday February 27, 2015 @09:47AM (#9119069)

I've not had any problems with importing non-ES6 modules into ES6 code. To use Express for example you can simply do `import express from 'express'`. If you only need access to one or two properties of the exported object you can use the destructuring syntax to just get references to them: `import { hash, compare } from 'bcrypt'`

[ Parent | on HN ]