diff options
| author | michael spengler <43786652+michael-spengler@users.noreply.github.com> | 2020-09-22 05:52:04 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-09-22 13:52:04 +1000 |
| commit | 5a8a4da524a38fcade24ca7645ae0c034602b9aa (patch) | |
| tree | f54f3d1800ed7c6e4dce2edf8b4544673eb0c5c0 | |
| parent | 9caeff3208a33098418ac2c64414010a3060a362 (diff) | |
docs: minor documentation improvement (#7603)
Closes #7602
| -rw-r--r-- | docs/examples/manage_dependencies.md | 5 |
1 files changed, 4 insertions, 1 deletions
diff --git a/docs/examples/manage_dependencies.md b/docs/examples/manage_dependencies.md index 978a8ce48..44b3082f8 100644 --- a/docs/examples/manage_dependencies.md +++ b/docs/examples/manage_dependencies.md @@ -20,7 +20,10 @@ they are all imported individually into individual modules. The standard practice for solving this problem in Deno is to create a `deps.ts` file. All required remote dependencies are referenced in this file and the required methods and classes are re-exported. The dependent local modules then -reference the `deps.ts` rather than the remote dependencies. +reference the `deps.ts` rather than the remote dependencies. If now for example +one remote dependency is used in several files, upgrading to a new version of +this remote dependency is much simpler as this can be done just within +`deps.ts`. With all dependencies centralized in `deps.ts`, managing these becomes easier. Dev dependencies can also be managed in a separate `dev_deps.ts` file, allowing |