Cyril Silverman

This is still an issue for me with `1.3.2`, I also tried `1.3.1` and `1.3.0` but comments are always stripped. All installed using npm.

Ah, actually this is my mistake, it's not precisely the same pattern. It appears lebab strips comments in this variation: ``` javascript function Thing() { this.a(); } Thing.prototype = {...

Even weirder behavior... if I put a comment above the prototype like this: ``` javascript function Thing() { this.a(); } // wat Thing.prototype = { // a a: function() {...

There's a definitely a list of "basic" MIDI trasnformers that are pretty common in most sequencers: - Arpeggiator - Chord Expansion - Note Length - Pitch (transpose) - Scale (ie:...

In the context of typegen, the lack of this support for this leads to type errors. lt would be preferable to even generate `any` or `unknown` until it's properly supported.

Yeah I don't use an auto-formatter at all (except for eslint which is pretty limited), but I see the problems here. Perhaps what feels most problematic is that the machine...

Good to know, makes sense why I got nowhere with this 😅 Feels like this is a use-case that should be pretty streamlined-- I'd definitely be willing to help get...

For what it's worth, I was having extreme slowness on TS 4.8, updating to TS 5.1 has drastically sped up type checking.

@gristow How are you storing these snippets? Is the notation "hardcoded" VexFlow, or are you generating VexFlow objects dynamically based on some sort of data?

@gristow thanks for the details, that's helpful @mturley Sorry but I haven't worked on the project in years! Just wanted to bring it up in context :)