Repository navigation
SnoutCode 1.0.6
Java now starts only for Java projects. SnoutCode used to start its Java engine, and could download a Java runtime for it, when it found a Gradle or Maven file anywhere near a project. Now the root of the project decides.
- A Node, Cypress, Python, Go or other project stays what it is, whatever build files or Java files are inside it. If you open a Java file of a build inside it, Java starts for that build alone.
- A
pom.xmlor Gradle file beside apackage.jsononly counts when the repository has Java, Kotlin, Scala or Groovy sources. - A stray build file above a repository no longer counts.
- A Node project with a build file at its root now shows its npm scripts.
Which file do I need?
| System | File |
|---|---|
| macOS on Apple silicon | SnoutCode-1.0.6-arm64.dmg |
| Windows, x64 | SnoutCode-1.0.6-windows-x64-setup.exe |
| Windows on Arm | SnoutCode-1.0.6-windows-arm64-setup.exe |
| Debian and Ubuntu | snout-code_1.0.6_amd64.deb or snout-code_1.0.6_arm64.deb |
| Arch Linux | snout-code-1.0.6-1-x86_64.pkg.tar.zst or -aarch64 |
SnoutCode updates itself to this version on macOS, and on Windows from 1.0.2. If you have 1.0.0 or 1.0.1 on Windows, install this one by hand: close SnoutCode first. The Windows installers are not code signed yet, so SmartScreen warns: click More info, then Run anyway.