Your Meteor forum post from 18 months ago in this thread Use ES2015 or CoffeeScript?
that couldn’t express better how I feel about CoffeeScript, seem to suggest that you were at the time using Meteor with CoffeeScript for some serious business (presumably with Blaze).
Are you still using this stack today though?
If you do, do you debug your code using consol.log and debugger statements that you comment in and out? I for one find this is unautomated, pre-IDE era approach to debugging frustratingly unproductive.
Yet, I have tried both Webstorm and VSCode, and to my frustration I have discovered that:
the Webstorm Meteor debugger does not work properly with CoffeeScript (not stopping on breakpoints) and the numerous open issues filed concerning these bugs seem to receive zero attention from Webstorm support (not enough votes to be addressed I guess)
the VSCode node debugger and the VSCode chrome debugger, in addition to be very hard to configure, are not made to work together to debug Meteor code and they both suffer from the same kind of CoffeeScript+Meteor source map leveraging bugs than Webstorm, making breakpoints in CoffeeScript code unusables.
So, how does you and your team overcome this lack of functionning IDE to productively code in CoffeeScript with Meteor?
Thank you very much in advance,