News for hackers. Stuff that matters.
Re:The state of JavaScript modules by sim0n on Monday May 29, 2017 @03:17AM (#14437851)
You don't have to use the hottest new framework or language feature. The JavaScript you're writing now will still be supported while the language evolves and improves.
Re:The state of JavaScript modules by kuschku on Monday May 29, 2017 @03:44AM (#14437937)
Nice idea, but false. Your code depends on libraries and frameworks, which constantly change and adapt to the the mood of the time.
Re:The state of JavaScript modules by octalmage on Monday May 29, 2017 @04:06AM (#14437997)
Many libraries that use ES6 features distribute the transpiled version through npm or GitHub. If they don't, you can just transpile the library using Webpack then use that.

Or you could use codemods to update your code base in an automated way. See: https://github.com/cpojer/js-codemod

Re:The state of JavaScript modules by tlrobinson on Monday May 29, 2017 @03:55AM (#14437963)
So transpile the library. Webpack and others can do it.
Re:The state of JavaScript modules by zmmmmm on Monday May 29, 2017 @08:19PM (#14442252)
If it was just about transpiling, that would be fine. The problem is that some frameworks (eg: React) add on a whole lot more assumptions about how how your app works. Just look at the plethora of blog posts, tutorials and even whole mini-frameworks just to get d3 to work with React.