Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

It would be nice if twoslash-cli parses defaultCompilerOptions #182

Open
vilicvane opened this issue May 8, 2023 · 1 comment · May be fixed by #183
Open

It would be nice if twoslash-cli parses defaultCompilerOptions #182

vilicvane opened this issue May 8, 2023 · 1 comment · May be fixed by #183
Labels
Enhancement New feature or request You can do this The idea is well specified and good for a PR

Comments

@vilicvane
Copy link

Took me some time to realize that I have to specify the actual enum value to make the defaultCompilerOptions work:

<!-- twoslash: {
  defaultCompilerOptions: {
    moduleResolution: 99 // NodeNext
  }
} -->

Search terms:

  • Cannot find module or its corresponding type declarations.
  • Unexpected moduleResolution: NodeNext
@orta orta added Enhancement New feature or request You can do this The idea is well specified and good for a PR labels May 8, 2023
@orta
Copy link
Contributor

orta commented May 8, 2023

Yeah, that makes sense 👍🏻

@vilicvane vilicvane linked a pull request May 9, 2023 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Enhancement New feature or request You can do this The idea is well specified and good for a PR
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Parse defaultCompilerOptions provided to cli vilicvane/twoslash
2 participants
@orta @vilicvane