You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/concepts/module-resolution.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -47,7 +47,7 @@ import "module";
47
47
import"module/lib/file";
48
48
```
49
49
50
-
Modules are searched for inside directories which are specified using `resolve.modules`, which can be an array comprising of different paths.
50
+
Modules are searched for inside directories which are specified using `resolve.modules`, which can be an array comprised of different paths.
51
51
Aliasing, i. e. setting `resolve.alias` to an existing module path, allows you to replace the module path with an alias name during `require/import`.
52
52
53
53
Once the path is resolved based on the above rule, the resolver checks if the path points to a file or to a directory. If the path points to a file then it is bundled straightaway.
@@ -67,6 +67,6 @@ Every filesystem access is cached so that multiple parallel or serial requests t
67
67
68
68
### Unsafe caching
69
69
70
-
There is a configuration option `resolve.unsafeCache` which boosts performance by aggressive caching.Every resolve process is cached and isn’t ever purged. This is correct in most cases, but incorrect in edge cases (what edge cases?).
70
+
There is a configuration option `resolve.unsafeCache` which boosts performance by aggressive caching.Every resolve process is cached and isn’t ever purged. This is correct in most cases, but incorrect in edge cases (what edge cases?).
71
71
72
72
Look at [Resolve API](/configuration/resolve) for more info on the configuration mentioned above.
0 commit comments