[TODO] evaluate if babel-traverse can be updated

[mirabilos]

Dependabot filed https://github.com/danvk/dygraphs/security/dependabot/2 (which I don’t think is truly critical for Dygraphs right now as the code is not untrusted, AIUI), but we’ll want that to go away of course.

However, we had issues with 7.21.4 and up, so we will have to see whether these are fixed now.

Someone else opened babel/babel#15579 which was closed in the meantime, but I’m not sure how much of that even applies here. This needs investigation, so opening this “ticket” so I can do that later and have the info here.

[danvk]

I wonder if we even need babel? dygraphs doesn't use many ES2015 features, and 2015 was a long time ago. Browser support for let/const/arrow functions is pretty solid these days.

[mirabilos]

Dan Vanderkam dixit:

I wonder if we even need babel? dygraphs doesn't use many ES2015 features, and 2015 was a long time ago. Browser support for

… is nōnexistent in PhantomJS though, with which the automated tests run. tbh I’d not mind converting it to normal (nōn-ES*) JavaScript, it doesn’t seem “much”, it needs someone to do the work though of course (or run Babel once and integrate the diff suitably, which is probably less effort), but I don’t have the tuits to do so currently. Maybe later. If you think that’s also a good idea I’ll consider it when I work on this issue. bye, //mirabilos