You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Twoslash error: Errors were thrown in the sample, but not included in an errors tag
These errors were not marked as being expected: 2345.
Expected: // @errors: 2345
Compiler Errors:
index.ts
[2345] 155 - Argument of type 'brand<typeof ULID, "ULID">' is not assignable to parameter of type 'Schema<unknown, unknown, unknown>'.
[2345] 239 - Argument of type 'Effect<unknown, ParseError, unknown>' is not assignable to parameter of type 'Effect<unknown, ParseError, never>'.
This can also be reproduced using the twoslash CLI1 if the @paths compiler option is inlined in the code example like so:
It requires a small patch to @typescript/twoslash (also described in the reproduction repo's README) because the current version of twoslash CLI doesn't work with the inlined @paths compiler option ↩
The text was updated successfully, but these errors were encountered:
Disclaimer: I'm still new to twoslash. It may be that I'm doing something wrong.
I'm trying to render HTML for the following markdown code with shiki twoslash in a monorepo using TS path aliases:
This results in the following error:
This can also be reproduced using the twoslash CLI1 if the
@paths
compiler option is inlined in the code example like so:I'm not going to provide the whole context in this issue. I've created the following reproduction repo instead: https://github.com/vecerek/docusaurus-shiki-twoslash-example. You shall find all relevant information (including the precise reproduction steps) in its README.
I think this is a twoslash issue because the TS code compiles correctly outside the documentation, i.e.:
Footnotes
It requires a small patch to
@typescript/twoslash
(also described in the reproduction repo's README) because the current version of twoslash CLI doesn't work with the inlined@paths
compiler option ↩The text was updated successfully, but these errors were encountered: