After update to latest vesion of Sublime and LaTeXTools, I get an error "Cannot find builder traditional".

[jeffgian]

After a recent update to Sublime Text 4192 (the latest version) and LaTexTools (v4.1.0), I now get an error message when trying to build a tex file:

Cannot find builder traditional.
Check your LaTeXTools Preferences

It is not just a problem with the traditional builder. I get a corresponding error message whichever builder I try to use.

In my settings, I have:
"builder_path": "User/builders"

In plugins/builder I see traditional_builder.py and all the others. I also have a copy in User/builders.

Running a Check System gives me this:

Program Location Status Version

---

latexmk /Library/TeX/texbin/latexmk available Latexmk, John Collins, 29 September 2020. Version 4.70b
pdflatex /Library/TeX/texbin/pdflatex available pdfTeX 3.141592653-2.6-1.40.22 (TeX Live 2021)
xelatex /Library/TeX/texbin/xelatex available XeTeX 3.141592653-2.6-0.999993 (TeX Live 2021)
lualatex /Library/TeX/texbin/lualatex available This is LuaHBTeX, Version 1.13.0 (TeX Live 2021)
biber /Library/TeX/texbin/biber available biber version: 2.16
bibtex /Library/TeX/texbin/bibtex available BibTeX 0.99d (TeX Live 2021)
bibtex8 /Library/TeX/texbin/bibtex8 available This is 8-bit Big BibTeX version 0.99d
kpsewhich /Library/TeX/texbin/kpsewhich available kpathsea version 6.3.3
magick missing unavailable
ghostscript /usr/local/bin/gs available GPL Ghostscript 9.53.3 (2020-10-01)

Packages for equation preview Status

---

standalone available
preview available
xcolor available
amsmath available
amssymb available
latexsym available
mathtools available

Builder Status

---

traditional missing

Builder Setting Value

---

display_log False
linux {}
osx {}
windows {}

[Honzaik]

try deleting temporary files/cache using commands "LatexTools: Clear cache" and "LatexTools: Delete temporary files".
This helped me.

[jeffgian]

Thanks for the suggestion, but unfortunately that didn't solve the problem.

…

On Thu, 30 Jan 2025 at 09:48, Jan Oupický ***@***.***> wrote: try deleting temporary files/cache using commands "LatexTools: Clear cache" and "LatexTools: Delete temporary files". This helped me. Its not the first time, this happened. This package is newly being maintained and it seems the new releases are a bit rushed with many bugs. — Reply to this email directly, view it on GitHub <#1603 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BKBSOCO3D4Z3A5LF46EYZT32NHYQNAVCNFSM6AAAAABWEVSFTGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMRUGAYDGNJWHA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[matthieugomez]

I am having the same issue.

[deathaxe]

That's an undesirable side effect of LaTeXTools internal plugin infrastructure, which happens after reloading modules. All should get back to normal when restarting ST.

[jeffgian]

Well, that's embarrassing. Restarting Sublime indeed fixed the problem, although after a couple of minutes of use the problem re-appeared and had to be fixed by another restart.

…

On Thu, 30 Jan 2025 at 15:39, deathaxe ***@***.***> wrote: That's an undesirable side effect of LaTeXTools internal plugin infrastructure, which happens after reloading modules. All should get back to normal when restarting ST. — Reply to this email directly, view it on GitHub <#1603 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BKBSOCIBJSJN7Q4RJ6AKEHL2NJBTPAVCNFSM6AAAAABWEVSFTGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMRUHA2DENJXGA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[deathaxe]

This kind of issue is triggered by modifying/saving plugin.py, which causes reloading all sub-modules.