I gave gts a try in one of my projects for cloud functions and it was also rather complicated. gts still has some nasty bugs like wrong CRLF handling in files managed by Git and linting files in compiler output directory and also I had to manually install eslint with eslint-plugin to make 'npm run check' work.
Another funny observation is a commit history of the gts. There is no actively involved maintainer because issues and pull requests hang without answers for a long time and most active contributor is a bot. I hope devs from the Google Node.js team will not drop this project.
What can I say about alternatives? I experience warm feelings with XO linter. It has slightly complicated initial configuration but received results are worth it.
Thank you for your story sharing.
I gave gts a try in one of my projects for cloud functions and it was also rather complicated. gts still has some nasty bugs like wrong CRLF handling in files managed by Git and linting files in compiler output directory and also I had to manually install eslint with eslint-plugin to make 'npm run check' work.
Another funny observation is a commit history of the gts. There is no actively involved maintainer because issues and pull requests hang without answers for a long time and most active contributor is a bot. I hope devs from the Google Node.js team will not drop this project.
What can I say about alternatives? I experience warm feelings with XO linter. It has slightly complicated initial configuration but received results are worth it.
Thanks for the information. Glad you liked the article. Unfortunately, it was written a while ago and it seems things have changed.
I will definitely look into XO linter one of these days.