From 5183c7fc5b0c446cf35c5c3ee8c090631faaeddc Mon Sep 17 00:00:00 2001 From: esainane Date: Fri, 18 Oct 2024 13:32:10 +0000 Subject: [PATCH] Fix minor typo in README (#274) --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 3c39b17..3e1b354 100644 --- a/README.md +++ b/README.md @@ -10,7 +10,7 @@ Use this to load modules whose location is specified in the `paths` section of ` Typescript by default mimics the Node.js runtime resolution strategy of modules. But it also allows the use of [path mapping](https://www.typescriptlang.org/docs/handbook/module-resolution.html) which allows arbitrary module paths (that doesn't start with "/" or ".") to be specified and mapped to physical paths in the filesystem. The typescript compiler can resolve these paths from `tsconfig` so it will compile OK. But if you then try to execute the compiled files with node (or ts-node), it will only look in the `node_modules` folders all the way up to the root of the filesystem and thus will not find the modules specified by `paths` in `tsconfig`. -If you require this package's `tsconfig-paths/register` module it will read the `paths` from `tsconfig.json` or `jsconfig.json` and convert node's module loading calls into to physical file paths that node can load. +If you require this package's `tsconfig-paths/register` module it will read the `paths` from `tsconfig.json` or `jsconfig.json` and convert node's module loading calls to physical file paths that node can load. ## How to install