David Bonnet

Feel free to give it a go. It's basically a copy of the `GENERATOR` with all spaces removed and no indentation support.

This could be handled through a custom `output` stream, that removes semicolons: ```js const output = { code: '', write(code) { switch (code) { case ';': break case ');': this.code...

Custom formatting is low-priority and won't be tackled soon. However, a pull request is welcome.

The fix could use optional chaining.

> I ended up just embedding the private keys for read-only deploy keys in the yml workflow files directly as ENV variables then following this advice with the hard coded...

Not yet, still planned though. Is this the right repository to contribute to? I noticed that you created variants with slightly different functionalities: - Escaya uses a custom AST instead...

Not yet, still planned though.

@loretoparisi In that case, I would link that varying folder to a fixed location: ```bash RUN ln -s $(pwd) $HOME/current-service ENV SERVICE_HOME $HOME/current-service ```

Thanks for raising that up @yxshv. Being able to generate TypeScript annotations is indeed a useful feature to add. Astring being ESTree-based, it should use an extension of it, such...

True, let's add that.