New URL Parser • new URL Parser is same to Browser URL API const URL = require('url').URL; // Create URL Object const u = new URL('https://www.example.com/path/ foo/bar'); // Stringify URL Object u.toString();
New URL Parser • new URL Parser is same to Browser URL API const URL = require('url').URL; // Create URL Object const u = new URL('https://www.example.com/path/ foo/bar'); // Stringify URL Object u.toString(); 8)"58(63-
HTTP/2 Implementation Status • Strongly Work In Progress • Some missing APIs • We have not supported HTTP/2 feature like Server Push/Prioritization yet • We need help!!! • https://github.com/nodejs/http2
ES Modules interoperability is…? • Node.js uses own CommonJS-like module load system. • However JavaScript defines new module system in ES2015. import/export • We need to show users to options to choose both CommonJS and ES Modules style.
ES Modules Goal • new Declarative Grammar (Tool/Engines friendly) • easy to detect errors • easy to optimize • new Strict Rules • Module is new Script.
Tools/Engines Friendly, Easy to detect errors // export.js export function foo() {} // import.js import { bar } from './export.js'; // Syntax Error, bar is not found.
Tools Friendly, Easy to optimize • webpack2 can reduce the bundled JavaScript size using `tree-shaking`. • tree-shaking detects `export module but not used one`.
Tools Friendly, Easy to optimize • webpack2 can reduce the bundled JavaScript size using `tree-shaking`. • tree-shaking detects `export module but not used one`.
ES Modules: new Script • Module is new Script • Module has some differences with current Script • implicit Strict Mode • Different Scope (top level this : undefined) • reserved keywords ( await )
ES Modules // Syntax Error under strict mode, you cannot use with. with (obj) {} // undefined, top level this is undefined not window console.log(this); // it is not window.foo, just module local scope var foo = 1; // Syntax Error, await is reserved in ES Modules var await = 'foo';
ES Modules Current Status • Safari TP is enabled under flag • Firefox Nightly is enabled under flag • Edge is enabled but it does not completed yet • Chrome is starting to development
Discussion, Discusssion, Discussion… • Loader Spec is under discussion • ES Modules new spec is also under discussion • Node Interop is also under discussion…
new extension?: .mjs • Current Node Proposals looks at file extension • `.js` is Script • `.mjs` is Module • this is still discussing on Node-EPS repository. • https://github.com/nodejs/node-eps/
Features are based on Standard • Past Node.js • Intl built-in Object • Present Node.js • ES 2016+ support • new URL Support • Future Node.js • HTTP/2 • ES Modules &$." &$." 8)"58( *&5' &$."
Why Node needs web standard? James Snell @ NodeFest 2016 Node.js is, and has been, primarily a platform for Web Application Development While Node.js presumes a "small core" philosophy for most things, it includes support for the most basic and critical internet standards
Why Node needs standard? • We are focusing on keep node ecosystems better. • ECMAScript and other internet Standard will be next community standard. • Node.js would be better to follow those standardization
References • You Don’t Know ES Modules by Teppei Sato • Node And Web Standard by James Snell • The Journey to ES Modules by Bradley Ferias • High Performance Browser Networking by Ilya Grigorik • https://github.com/nodejs/node-eps
yosuke_furukawa
hschwentner
antonicg
ogiwarat
hiranabe
stewemetal
manfredsteyer
kizuku_miyagi
kojipole
mot_techtalk
youtalk
jxmtst
shimabox
nonsquared
morganepeng
lynnandtonic
garrettdimon
samlambert
cherdarchuk
philhawksworth
geoffreycrofte
lara
trishagee
keathley
gr2m