Eirik L. Vullum

I just wanted to chime in on this; We already use `"engines": { "node": "x.x.x" }` to make heroku install the correct node version for all our apps. If platforms...

Other than that - love this - great work! :)

@ljharb isn't that a good thing? :-)

My point is - when this works really well on Heroku - why shouldn't it work great anywhere else..?

Is the issue here shortcomings of the tool (that it only supports a specific version)?

My main point here is - why add another (duplicate) reference to the node version when you already specify it in `"engines"`. I don't want to have to keep things...

The optimal solution would be that avn would tell n or nvm to install/use the latest available version in the specified semver range Edit: And thus behaving the same way...

This thing comes to mind as well - http://tolmasky.com/2016/03/24/generalizing-jsx/ - https://github.com/tolmasky/generic-jsx

+1 on this. Having this issue when using time on one axis (2.33.0)

I guess I have to get super familiar with the internals - because it's not clear to me what changed here to break it: https://github.com/plotly/plotly.js/compare/v2.25.2...v2.26.0