Unclear how to indicate tsconfig to plugin
See original GitHub issueI’m using a tsconfig.json to add “DOM” to the lib compilerOptions for typescript, and running deno bundle -c tsconfig.json whatever.ts
. I can’t see any way to get the plugin to acknowledge the existing of the DOM lib though. Is this supported?
Issue Analytics
- State:
- Created 3 years ago
- Reactions:5
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Specify tsconfig file to use for heft build/start/test · Issue #2258
Currently the Heft TypeScript plugin blindly and greedily assumes that any tsconfig-*.json files in the root directory are meant for its ...
Read more >Specify path to tsconfig.json - typescript - Stack Overflow
I am using webpack with awesome-typescript-loader in an environment with multiple tsconfig.json files. Is there a way in webpack to specify the path...
Read more >TSConfig Reference - Docs on every TSConfig option
Intro to the TSConfig Reference. A TSConfig file in a directory indicates that the directory is the root of a TypeScript or JavaScript...
Read more >TypeScript: Sorting out tsconfig. Part 1 - DEV Community
Each new project I prefer to write on TS rather than native JavaScript. In this article, I will not discuss the reasons for...
Read more >3 Options to Compile Typescript to JS: Rollup, TSC, Babel
What is ideal from this config file is that the typescript plugin has ... Note that the original tsconfig has declaration set to...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I will fix it
@Ragzouken , unrelated to actually setting the tsconfig.json but related to your “dom” problem that you wanted to solve. I got it working by introducing a triple slash reference.
Edit: For compilation purposes, you also need a tsconfig.json, mine looks like this:
And compile with
deno bundle -c tsconfig.json file.ts file.js