You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In my device model I use velocity model which use your PID controller. I use the device model on a website so the ES6 pid controller code runs there. It works on Chrome but not on Safari. I could build it myself but I thought it would be better if it was already built when I require it.
I've submitted a PR (#9) to accomplish this without duplicating files, either in the source or in the npm module. It's opinionated so you're 100% free to just disregard! For me though, I was just making a medium-sized browser-targeted demo that didn't really benefit at all from ES6, so it was just a bit unpleasant to babelify the whole project for one dependency (requires working browserify into the dev server and build step, which isn't that bad, but a slight pain). Either way though, thanks for the great module!
Activity
Philmod commentedon Aug 4, 2016
Hey Natanael,
Could you tell me more about the reason you need the ES5 version? In which environment are you using this package?
nattelog commentedon Aug 5, 2016
Hi,
In my device model I use velocity model which use your PID controller. I use the device model on a website so the ES6 pid controller code runs there. It works on Chrome but not on Safari. I could build it myself but I thought it would be better if it was already built when I require it.
Philmod commentedon Aug 5, 2016
If you use browserify, you should be able to compile it in the format you need. Would that help?
nattelog commentedon Aug 9, 2016
Well, my project use webpack. Perhaps it has a solution for it. Thanks for the help anyway! 😄
Philmod commentedon Aug 9, 2016
You have to use a compiler like Babel, that will work with webpack.
rreusser commentedon Aug 18, 2016
I've submitted a PR (#9) to accomplish this without duplicating files, either in the source or in the npm module. It's opinionated so you're 100% free to just disregard! For me though, I was just making a medium-sized browser-targeted demo that didn't really benefit at all from ES6, so it was just a bit unpleasant to babelify the whole project for one dependency (requires working browserify into the dev server and build step, which isn't that bad, but a slight pain). Either way though, thanks for the great module!