News for hackers. Stuff that matters.
Re:Node v4.0.0 by codecurve on Tuesday September 08, 2015 @04:01PM (#10187887)
You'll be able to achieve that behaviour when node also supports destructuring.

    import { readFile, writeFile } from 'fs';
    import { clone } from 'lodash';
Re:Node v4.0.0 by awalGarg on Wednesday September 09, 2015 @09:37AM (#10191319)
Not really. The destructuring syntax used in the imports is not the same as the standard array and object destructuring.

Section 15.2.1.16 of the current stable ES6 specification specifies how the import syntax is resolved, and it doesn't use destructuring.

P.S. Sorry too lazy to get a clickable link from the spec :P see http://awal.js.org/especser/#15.2.1.16 if you really wanna read it

Re:Node v4.0.0 by WalterSear on Wednesday September 09, 2015 @01:05AM (#10189786)
As I understand it, that still involves importing the whole file, rather than just the part you need. If that is an issue, lodash is parted out by method, so you can do this instead:

  import clone from 'lodash/lang/clone'
Re:Node v4.0.0 by loganfsmyth on Tuesday September 08, 2015 @08:40PM (#10189024)
Just a nit, but that isn't destructuring. Named import syntax has several differences, since name aliasing uses a different format and you cannot nest or provide default values.
Re:Node v4.0.0 by msoad on Tuesday September 08, 2015 @04:07PM (#10187928)
oops I forgot the braces! ok then, it's cool. I'm happy it does resolving to node_modules and all that automatically.
Re:Node v4.0.0 by pluma on Thursday September 10, 2015 @05:37AM (#10197025)
It's just syntactic sugar for `require`, mostly. The import mechanism should behave the same.