PR converts the Three.js codebase to ES2015 modules

Re:PR converts the Three.js codebase to ES2015 modules by erikpukinskis on Saturday July 23, 2016 @12:49PM (#12150057)

Why is this a good thing? Just seems like different syntax to do the same thing.

You can theoretically dynamically resolve the different exports asynhronously, but you could do that by exporting functions before.

ES6 makes me think I am going crazy. Everyone seems so excited to have new sugar and a ton of busywork upgrading code and resolving runtime incompatibilities. I have yet to see any feature that seems like an actual benefit to the conservative working programmer.

Maybe destructuring.

[ Parent | on HN ]

Re:PR converts the Three.js codebase to ES2015 modules by bsou on Saturday July 23, 2016 @01:02PM (#12150106)

eslint also provides static analysis for dependency resolution when using import statements instead of node require calls

[ Parent | on HN ]

Re:PR converts the Three.js codebase to ES2015 modules by jacobr on Saturday July 23, 2016 @04:03PM (#12150805)

eslint-plugin-import found several bugs for us when we enabled it. Can't recommend it enough. https://github.com/benmosher/eslint-plugin-import

[ Parent | on HN ]

Re:PR converts the Three.js codebase to ES2015 modules by smitherfield on Saturday July 23, 2016 @01:43PM (#12150263)

I'd say constants are pretty big.

[ Parent | on HN ]

Re:PR converts the Three.js codebase to ES2015 modules by lhnz on Saturday July 23, 2016 @12:54PM (#12150080)

Smaller file sizes.

[ Parent | on HN ]