@biggive/components 0.0.9 → 0.0.12
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/package.json +1 -1
- package/readme.md +9 -0
package/package.json
CHANGED
package/readme.md
CHANGED
|
@@ -45,6 +45,15 @@ Anything externally managed should be loaded with npm and no copies checked into
|
|
|
45
45
|
|
|
46
46
|
Generated build outputs should similarly be `.gitignore`d.
|
|
47
47
|
|
|
48
|
+
### Angular components
|
|
49
|
+
|
|
50
|
+
As well as the core package `@biggive/components`, CI automatically publishes a version best tailored to
|
|
51
|
+
Angular as `@biggive/components-angular`. The former are possible to load into Angular but the latter will
|
|
52
|
+
work better [as documented](https://stenciljs.com/docs/angular).
|
|
53
|
+
|
|
54
|
+
Our Angular workspace and library are set up as per that documentation, but our Stencil library lives in this
|
|
55
|
+
repo's root, one directory up from in the docs' structure. So far this seems to have no adverse effects.
|
|
56
|
+
|
|
48
57
|
### Asset dependencies
|
|
49
58
|
|
|
50
59
|
So far our strategy has been to avoid separate file assets where this is an out-the-box option, but
|