Strictly speaking, the former is interpreted as a declaration file for a JavaScript file named .īecause relative files imports need to include extensions in Node’s ESM support, TypeScript would error on our example in an ESM file under -moduleResolution node16 or nodenext.įor more information, read up the proposal for this feature and its corresponding pull request. Note that historically, a similar effect has often been achievable by adding a declaration file named .ts instead of app.d.css.ts - however, this just worked through Node’s require resolution rules for CommonJS. By default, this import will raise an error to let you know that TypeScript doesn’t understand this file type and your runtime might not support importing it.īut if you’ve configured your runtime or bundler to handle it, you can suppress the error with the new -allowArbitraryExtensions compiler option.
0 Comments
Leave a Reply. |