@narmi/design_system 3.48.0 → 3.50.0
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 +4 -4
- package/dist/index.js +1 -1
- package/dist/index.js.map +1 -1
- package/dist/style.css +2 -2
- package/dist/style.css.map +1 -1
- package/dist/tokens/css/rgbColors.css +1 -1
- package/dist/tokens/css/tokens.css +1 -1
- package/dist/tokens/js/colors.js +1 -1
- package/dist/tokens/js/manifest.js +1 -1
- package/dist/tokens/js/reactNativeWeb.js +1 -1
- package/dist/types/SeparatorList/index.d.ts +13 -0
- package/dist/types/SeparatorList/index.d.ts.map +1 -0
- package/dist/types/Slider/Thumbs.d.ts +3 -0
- package/dist/types/Slider/Thumbs.d.ts.map +1 -0
- package/dist/types/Slider/index.d.ts +30 -0
- package/dist/types/Slider/index.d.ts.map +1 -0
- package/dist/types/index.d.ts +52 -65
- package/dist/types/index.d.ts.map +1 -0
- package/dist/types/types/Icon.types.d.ts +5 -0
- package/dist/types/types/Icon.types.d.ts.map +1 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -58,7 +58,7 @@ For full documentation of available classes, see [storybook docs](https://narmi.
|
|
|
58
58
|
### Design tokens
|
|
59
59
|
|
|
60
60
|
All available distributions of design tokens can be found in `dist/tokens`.
|
|
61
|
-
All CSS custom
|
|
61
|
+
All CSS custom properties from design tokens are already included in the base
|
|
62
62
|
stylesheet, `dist/style.css`.
|
|
63
63
|
|
|
64
64
|
To request a new distribution, please [file an issue](https://github.com/narmi/design_system/issues/new/choose).
|
|
@@ -94,7 +94,7 @@ npm run dev
|
|
|
94
94
|
| `build:jsdoc` | builds jsDoc documentation to `dist/` |
|
|
95
95
|
| `build:tokens` | builds all distributions of design tokens to `dist/` |
|
|
96
96
|
| `build:components` | builds all components and base stylesheet to `dist/` |
|
|
97
|
-
| `build` | builds
|
|
97
|
+
| `build` | builds everything |
|
|
98
98
|
| `test` | runs all jest tests |
|
|
99
99
|
| `storybook` | starts storybook in dev server mode on `:6006` |
|
|
100
100
|
| `watch` | watches `src` dir, triggering `build` on changes |
|
|
@@ -112,7 +112,7 @@ parse recent git tags and commit messages to determine the new version number, t
|
|
|
112
112
|
|
|
113
113
|
#### Major releases
|
|
114
114
|
|
|
115
|
-
All PRs target `main` unless it contains breaking changes. Any branch
|
|
115
|
+
All PRs target `main` unless it contains breaking changes. Any branch containing breaking change commits should target the open major release branch.
|
|
116
116
|
For example, if NDS is on major version `1`, breaking changes should target the branch `major/v2`.
|
|
117
117
|
|
|
118
118
|
Branches containing breaking change commits should follow the naming convention `breaking/<branch name>`.
|
|
@@ -176,7 +176,7 @@ The best way to approach testing unpublished NDS changes in a consumer is to use
|
|
|
176
176
|
2. Update the `version` field of package.json to be a beta of the next minor.
|
|
177
177
|
For example, you would change `2.35.2` to `2.36.0-beta.0`.
|
|
178
178
|
DO NOT COMMIT THIS CHANGE.
|
|
179
|
-
3. Publish the package (`npm
|
|
179
|
+
3. Publish the package (`npm publish --tag beta`)
|
|
180
180
|
4. In your consuming application, you can point the `@narmi/design_system`
|
|
181
181
|
version to the beta version you just published.
|
|
182
182
|
|