I have a document that compiles with --feature html and doesn’t otherwise. How can I have tinymist pick up on this and not red-squiggle me? I’ve read the tinymist docs and tried the following to no avail.
"tinymist.typstExtraArgs": ["--features", "html"]"tinymist.typstExtraArgs": ["--features html"]"tinymist.exportTarget": "html"I have "tinymist.typstExtraArgs": ["--features", "html" ] in my config and it works. When previewing, I get the warning “elem was ignored during paged export” since preview is not based on HTML export, but I get autocomplete and not compilation errors.
Have you restarted VS Code after changing the config? Can you share more about your setup?
An alternative could be using Bullseye to prevent your document from using the real HTML functions while previewing.
Hmm, interesting. I hit, I think it was called typst: restart language server in the command pallet every change of settings. It probably worked to refresh tinymist, i saw syntax highlighting blink off and on at least. The settings were specified in the workspace json, which shpuldnt be an issue. I’m out and about right now, and would need to get to my laptop later. But is there any other diagnostic issues that would help?
Also, bullseye looks wonderful, I might pull in that either way just for semantic pedanticness :D
You could try look in the Tinymist output (in the command palette: Output: Show Output Channels… – TinyMist Typst). Easiest to check is directly after restarting VS Code and opening a Typst file, you should see something like
[2025-08-30T15:19:30Z INFO tinymist::config] ServerState: config update_by_map
{"colorTheme":"dark","compileStatus":"enable",...,"typstExtraArgs":["--features","html"]}
(linebreak added by me)
From quickly trying stuff out, it seems that using “Typst: Restart server” was not sufficient to make it recognize changes in that option, so maybe that really was the problem.