ES6 code on Nodejs 4.x : Is V8 4.5 a native JS engine that runs ES6 directly?

Question

I'm trying to upgrade a micro service that's on Nodejs 1.0.x to Nodejs 4.x. The purpose is to enhance the functionality of this service & take advantage of ES6 features, especially avoid prototype clutter in new code segment. While going through few blogs, I've come across a statement that ES6's module pattern is standardised and it's Asynchronous unlike require().

If the module loading is Asynchronous(with import of module syntax), I'm trying to understand how the code in that file take advantage of this feature? All the code that have dependency on this asynchronously imported module will also become asynchronous? If yes, instead of combination of require (synchronous) and import/module (asynchronous), I would like to change every thing to import/module assuming the performance gain.

I need some help in correcting or fine-tuning my thought process.

Following is the reference: http://stackoverflow.com/questions/31354559/using-node-js-require-vs-es6-import-export — FullMoon, Nov 24 '15 at 06:25

score 1 · Accepted Answer · answered Nov 24 '15 at 03:57

1

ES6 modules are loaded synchronously in Node.js (server). They are loaded asynchronously only in the browser. The advantage of import is that it's the same keyword for both use cases.

answered Nov 24 '15 at 03:57

monkbroc

808
9
13

No browser supports ES6 module loading right now. There are implementations of module loaders - some are asynchronous, some are not. – CodingIntrigue Nov 24 '15 at 08:26

ES6 code on Nodejs 4.x : Is V8 4.5 a native JS engine that runs ES6 directly?

1 Answers1