_Kerman

I think this is not related to the Vue language tools. In plain TypeScript you can also get this error: 

This could be hard to implement, because each slide project may has its own rules on how to automatically split slides. As a workaround, you can use a preparser (https://sli.dev/custom/config-parser)...

It seems that the Netlify deployment is broken for this PR. I have to close this and open another one.

I think the best way to do this is to extract the components into an addon (or simply a directory like `X/components/*`), and then use it as an addon in...

I think this is a TypeScript limitation. We can't fix this on Vue's side. See [this code](https://www.typescriptlang.org/play/?#code/GYVwdgxgLglg9mABMAPAFUQUwB5U2AEwGdEBvRAbQGlEYkBrTATzmETQF0Aud6jxAL6IAZGVoEeABQBOcAA6ZpUJlWaCAfAAoAlGQBQiQ4mULEAYTgAbEAFswAEUyo06xAF59Rr4jmyFSph5GFjYMUSIoaToAcwBuAyMBeITDCAQIxCJLOCgiHgAlTABDAgRLJhRyaloGZlZ2RCKSAAM06zsAWgASUhpwyJiBZu5ETQB9HipdN1cisCZYjXdEMBBLS0aSOYWUxDSwDLbbMB4LdocndFcPXa9yX3lFZR4AchgCF4AaYxgoS0xXgBJewvQSfXYcZJeLI5IgUVpWY7dUhHOxwgAMHAAdA9-Mohhw9AI9EA) - `f1` errors but `f2` is ok.

I am not sure about the usage of the options in your code. The options seem to be Monaco Editor options, but the code block is a normal code block....

Let's keep the issue open to keep track of the problem of `}` inside the option. Thank you for letting us know this.

This can now be done by customizing the `slidev.dev-command` configuration of the VSCode extension. Also, if VSCode's `env.remoteName != null`, now the `--remote` flag will be automatically added.

Closing this issue as it has been a long time, and the new [browser exporter](https://sli.dev/guide/exporting#browser) feature may have addressed this. Feel free to reopen the issue if the problem still...

try: ```yaml routerMode: hash ``` in headmatter?