Closed pietgk closed 6 months ago
Based on the information you've provided, we're not exactly sure why it's not working for you, but the .quokka
configuration certainly looks problematic.
Quokka has its own integration with tsconfig-paths
and loading setting this using env.params.runner
will definitely cause problems. You shouldn't have to do anything for Quokka to pick up your tsconfig-paths
if your TypeScript configuration(s) are correctly configured.
The first thing I would try is to remove the env
setting from your .quokka
configuration but I expect you've already tried this and that's why you added it in the first place?
We have created a sample repo based on the configuration that you provided, and test.ts
in the project root is working for us.
Could you please update the sample repo to break in the same way that you're seeing as your project?
@smcenlly Thx for the starter repo. I created a forked version of the repo with a readme with a description of the reproduced issue and a working ts-node example.
you where also correct on the assumption regarding .quokka conf being added to try to solve the issue. the example repo is without any specific quokka config.
Thanks for providing the sample. This has been fixed in the latest version of Quokka for VS Code (v1.0.640
).
I can confirm that it now works.
tsconfig compilerOptions paths not working
in Quokka in vscode on import from @dal/db in below code gives
Is this issue related to Quokka not outputting the expected results of your code?: Yes
in ts-node with cwd ~/dev/monorepo-3.0/services/mindlerapi it can import @dal/db
Sample code
I did add quokka.json in the root of the monorepo containing:
services/mindlerapi/tsconfig.json:
Sample repository link
See this example repo for a full reproduction of the issue.
Code editor version
Visual Studio Code v1.89.0
OS name and version
OSX