https://github.com/biomejs/biome

The output for error messages in the trunk cli seems to format multiple lines by filling in spaces to wrap to the end of the line. This is instead of just putting in a newline. In other words, a long list of messages in the ISSUES block is not actually multiple lines of text. Its one long line, and the end of each "line" has spaces filled in to the width that the CLI thinks the terminal is. This makes it impossible to cut and paste error messages into a text file. It also means if you resize your terminal the formatting goes crazy. It would be way simpler to just end lines with newlines.

It seems to correctly recognize that it needs the .ps1 script on Windows but then it doesn't call a full path and I think this is the issue. \Users\nwest\.cache\trunk\launcher\trunk.ps1 : The term '\Users\nwest\.cache\trunk\launcher\trunk.ps1' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again. At line:1 char:1 + \Users\nwest\.cache\trunk\launcher\trunk.ps1 init --vscode + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : ObjectNotFound: (\Users\nwest\.c...ncher\trunk.ps1:String) [], CommandNotFoundException + FullyQualifiedErrorId : CommandNotFoundException

Add trunk check integration in IntelliJ/WebStorm/GoLand/etc for code formatting and linter warnings

I propose to include https://github.com/cmhughes/latexindent.pl as a formatter for LaTeX-Documents. I integrate it in all my .trunk/trunk.yaml, because it is running fine. Please tell me, if there is a chance to integrate - I offer to help. Via Github?

I've been running trunk check cli inside of a terminal in Emacs, and something about the color codes trunk uses causes a lot of the text to be unrenderable. Specifically the line numbers for found issues, and the text for notices. There doesn't appear to be any way to turn off color coding. An option to do that, or even better to just limit colors to the standard xterm color set, would be great.

First off, very happy trunk user on M1 Pro MacOS w/ VS Code. Second - computer started to crawl, checked activity monitor, saw ~8 GB+ memory being used across 8 trunk processes, top 3 were 5 gb, 2 gb, 1 gb. At this point, probably a couple months in to using Trunk - first time I've noticed this issue though can't say for certain whether it's happened before. I don' restart my machine often, often have multiple VS code windows open concurrently, so not necessarily surprising I might have triggered something funky. I'm a DevOps coder, not deep into SWE or native app troubleshooting or debugging, though happy to share additional info if there is something specific you'd like me to share (e.g. log files, verbose output, etc.)

https://github.com/tweag/ormolu

https://github.com/ndmitchell/hlint

https://scalacenter.github.io/scalafix/