@dunx/create-app 0.2.9 → 0.2.11
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +6 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -61,6 +61,12 @@ package shares one number and ships together - so the version doing the
|
|
|
61
61
|
scaffolding is by definition a set that works together. Writing versions into the
|
|
62
62
|
template would go stale on the next release.
|
|
63
63
|
|
|
64
|
+
Keep it that way when you add a package later. The packages peer-depend on each
|
|
65
|
+
other by caret range, so mixing minors warns on install - and can leave two copies
|
|
66
|
+
of `@dunx/core` in one tree, which breaks dependency injection outright: a token
|
|
67
|
+
*is* a class object, so two copies are two different classes and a provider bound
|
|
68
|
+
against one is invisible to the other.
|
|
69
|
+
|
|
64
70
|
**The template's `.gitignore` ships as `_gitignore`.** npm renames a published
|
|
65
71
|
`.gitignore` to `.npmignore`, which would leave every scaffolded app without one.
|
|
66
72
|
The scaffolder puts the dot back on write.
|