Replies: 2 comments 1 reply
-
Because WXT strips out all types during the build process without checking them. This is very standard for build frameworks, because typescript is really slow.
You should be able to override it in your root tsconfig, the one that extends the one generated by WXT. If that doesn't work, you could use the |
Beta Was this translation helpful? Give feedback.
-
I had other problems with the |
Beta Was this translation helpful? Give feedback.
-
Running
wxt build
works fine in a TypeScript 4 monorepo, but runningtsc --noEmit
(which is present in the init project scripts by the name ofcompile
) throws an error. How canbuild
produce a result even thoughcompile
fails?My issue is probably caused by TypeScript not having the bundler option for module resolution, which is set in wxt's generated tsconfig. Some comments I found on the repo also reference TypeScript 5 feature (like extending multiple configs: #572 (reply in thread), #868 (comment)).
Does this package supprt TypeScript, is there anything I can configure for it to work? If not, this should be documented somewhere. If not on the main readme, at least somewhere like here: https://wxt.dev/guide/essentials/config/typescript#typescript-configuration.
Beta Was this translation helpful? Give feedback.
All reactions