Upgrade dependencies

[tbranyen]

A lot has changed in a few years and now the ES Module specification has been fully realized by the standards body TC-39. The tool used at the time es6-module-loader now throws deprecation warnings like:

npm WARN deprecated es6-module-loader@0.15.0: This project has been deprecated for "npm install es-module-loader" based on the newer loader spec.

While this isn't a blocker, I would like to upgrade the dependencies to Babel and perhaps Webpack to future proof this project and make it nicer to work on.

[schilippe]

Webpack is awesome. We should consider converting the extension to TypeScript and just package the JS output.

…

On Feb 10, 2017 14:13, "Tim Branyen" ***@***.***> wrote: A lot has changed in a few years and now the ES Module specification has been fully realized by the standards body TC-39. The tool used at the time es6-module-loader now throws deprecation warnings like: npm WARN deprecated ***@***.***: This project has been deprecated for "npm install es-module-loader" based on the newer loader spec. While this isn't a blocker, I would like to upgrade the dependencies to Babel and perhaps Webpack to future proof this project and make it nicer to work on. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#97>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AD5VYK4h6_oQpkS0E9QvUSIOpOd9A4IKks5rbLbNgaJpZM4L9vuu> .

[karger]

Tim, Philippe, it's great having you both back! But I've created some potential races by getting you both back at *exactly the same time*. Hopefully you two can coordinate to avoid stepping on each others' pushes.

…

On 02/10/2017 02:16 PM, Philippe wrote: Webpack is awesome. We should consider converting the extension to TypeScript and just package the JS output. On Feb 10, 2017 14:13, "Tim Branyen" ***@***.***> wrote: > A lot has changed in a few years and now the ES Module specification has > been fully realized by the standards body TC-39. The tool used at the time > es6-module-loader now throws deprecation warnings like: > > npm WARN deprecated ***@***.***: This project has been deprecated for "npm install es-module-loader" based on the newer loader spec. > > While this isn't a blocker, I would like to upgrade the dependencies to > Babel and perhaps Webpack to future proof this project and make it nicer to > work on. > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > <#97>, or mute the thread > <https://github.com/notifications/unsubscribe-auth/AD5VYK4h6_oQpkS0E9QvUSIOpOd9A4IKks5rbLbNgaJpZM4L9vuu> > . > — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#97 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABFpXvK8Y-ZVYE_MVwRkCa3fkALLQ7-Wks5rbLd0gaJpZM4L9vuu>.

[tbranyen]

No worries, for now I'm re-acquainting myself with the code base and the open issues. I'm going to try and make PRs for low-hanging-fruit changes, but won't merge anything. Good to see ya both as well, looking forward to helping out again!