How To Strongly Type process.env
Learn how to strongly type process.env in TypeScript by either augmenting global type or validating it at runtime with t3-env.
Relative import paths need explicit file extensions in EcmaScript imports when '--moduleResolution' is 'node16' or 'nodenext'.
// Relative import paths need explicit file extensions in
// EcmaScript imports when '--moduleResolution' is 'node16'
// or 'nodenext'.
import { example } from "./foo";
Adding a .ts
extension to the import path doesn't work, and results in the following error:
An import path can only end with a '.ts' extension when 'allowImportingTsExtensions' is enabled.
// An import path can only end with a '.ts' extension when
// 'allowImportingTsExtensions' is enabled.
import { example } from "./foo.ts";
Add the .js
extension to the import path.
import { example } from "./foo.js";
This error happens because you've specified moduleResolution: NodeNext
. This tells TypeScript that you want your imports and exports to conform strictly to the Node spec.
The Node spec requires that you use .js
file extensions for all imports and exports. This was decided so that a relative import path like ./foo.js
would work both in Node and the browser.
This also simplifies Node's module resolution strategy - Node doesn't have to do any guesswork to figure out what file to import. Thanks to Gil Tayer for clarifying this for me.
tsconfig.json
to use moduleResolution: Bundler
instead of moduleResolution: NodeNext
.Share this article with your friends
Learn how to strongly type process.env in TypeScript by either augmenting global type or validating it at runtime with t3-env.
Discover when it's appropriate to use TypeScript's any
type despite its risks. Learn about legitimate cases where any
is necessary.
Learn why TypeScript's types don't exist at runtime. Discover how TypeScript compiles down to JavaScript and how it differs from other strongly-typed languages.
Improve React TypeScript performance by replacing type & with interface extends. Boost IDE and tsc speed significantly.
In this book teaser, we discuss deriving vs decoupling your types: when building relationships between your types or segregating them makes sense.
Learn how TypeScript's new utility type, NoInfer, can improve inference behavior by controlling where types are inferred in generic functions.