|
@ -242,7 +242,7 @@ then it does *not* add the full resolved path to where `./lib` |
|
|
is on the filesystem. Instead, it literally adds `'./lib'`, |
|
|
is on the filesystem. Instead, it literally adds `'./lib'`, |
|
|
meaning that if you do `require('y.js')` in `/a/b/x.js`, then it'll look |
|
|
meaning that if you do `require('y.js')` in `/a/b/x.js`, then it'll look |
|
|
in `/a/b/lib/y.js`. If you then did `require('y.js')` in |
|
|
in `/a/b/lib/y.js`. If you then did `require('y.js')` in |
|
|
`/l/m/n/o/p.js`, then it'd look in `/l/m/n/o/p/lib/y.js`. |
|
|
`/l/m/n/o/p.js`, then it'd look in `/l/m/n/o/lib/y.js`. |
|
|
|
|
|
|
|
|
In practice, people have used this as an ad hoc way to bundle |
|
|
In practice, people have used this as an ad hoc way to bundle |
|
|
dependencies, but this technique is brittle. |
|
|
dependencies, but this technique is brittle. |
|
|