Show HN: Trunk – One linter to run them all
1–9 of 9 posts
Re: Show HN: Trunk – One linter to run them all
#2 Hi! I’m one of the co-founders of Trunk. Trunk Check is the first tool in the toolbox we're building to make scalable, productive repos possible out of the box. Modern repositories include many technologies, each with its own set of linters. With 30+ linters and counting, Trunk makes it dead-simple to identify, install, configure, and run the right linters, static analyzers, and formatters for all your repos. Use it on mac or linux from the command line, our vscode extension, or on CI. We’re on the thread so please ask any questions. We’d love to get feedback from the HN crowd. TYVM!
Re: Show HN: Trunk – One linter to run them all
#3This is so cool!
Re: Show HN: Trunk – One linter to run them all
#4Insanely cool product from a killer team of builders.
Re: Show HN: Trunk – One linter to run them all
#5Insanely cool product from a killer team of builders.
thanks semil!
Re: Show HN: Trunk – One linter to run them all
#6Hi! I’m one of the co-founders of Trunk. Trunk Check is the first tool in the toolbox we're building to make scalable, productive repos possible out of the box. Modern repositories include many technologies, each with its own set of linters. With 30+ linters and counting, Trunk makes it dead-simple to identify, install, configure, and run the right linters, static analyzers, and formatters for all your repos. Use it…
Cool idea. I tried to install the VSCode extension but not sure if its working because there was no feedback.
Re: Show HN: Trunk – One linter to run them all
#7Hi! I’m one of the co-founders of Trunk. Trunk Check is the first tool in the toolbox we're building to make scalable, productive repos possible out of the box. Modern repositories include many technologies, each with its own set of linters. With 30+ linters and counting, Trunk makes it dead-simple to identify, install, configure, and run the right linters, static analyzers, and formatters for all your repos. Use it…
Cool idea. I tried to install the VSCode extension but not sure if its working because there was no feedback.
Hey thanks - it should populate with issues for any files that you've modified, and as you browse files any file you have open. We don't have a way from vscode to run on the whole codebase yet, best run the cli for that, but it's coming!
Re: Show HN: Trunk – One linter to run them all
#8This seems kinda neat - especially for ecosystems which don’t have standard ways to pin tool dependencies (looking at you, go).
The pricing makes me concerned though, I have to email about the enterprise plan to try this out on a private repo, and it’s extremely unclear what sort of ballpark this is going to cost me.
I am also concerned that it’s hard to see a path from “install a bunch of linters” to “VC gets their exit”, which doesn’t give me a lot of confidence to incorporate this into important projects
Re: Show HN: Trunk – One linter to run them all
#9This seems kinda neat - especially for ecosystems which don’t have standard ways to pin tool dependencies (looking at you, go). The pricing makes me concerned though, I have to email about the enterprise plan to try this out on a private repo, and it’s extremely unclear what sort of ballpark this is going to cost me. I am also concerned that it’s hard to see a path from “install a bunch of linters” to “VC gets their…
Thanks for the comment! Go ahead and use it in private repos for personal use or on small teams for free - our pricing structure only targets private repo use by companies with eng teams > 10.
Even for ecosystems that do have tool dep pinning, folks are missing out because the linters/formatters you should be running aren't necessarily part of the language ecosystem you use. For example, you probably have shell scripts that should run shfmt and shellcheck, which aren't on npm, even if you otherwise use javascript.
Trunk is young, but we'll become the one stop shop for the full development experience of highly productive scalable repos: linting, formatting, code coverage, merge automation, test analytics, running/selecting tests, and more. What we've seen is companies & projects repeatedly recreating bad versions of this stuff in house - which leads to bad dev experience and is a waste of time & money.