@cobalt-ui/plugin-json
Advanced tools
Comparing version 0.4.0 to 0.4.1
# @cobalt-ui/plugin-json | ||
## 0.4.1 | ||
### Patch Changes | ||
- ed21d56: Bump deps, add config type to docs | ||
## 0.4.0 | ||
@@ -4,0 +10,0 @@ |
{ | ||
"name": "@cobalt-ui/plugin-json", | ||
"description": "Generate JSON from your design tokens schema (requires @cobalt-ui/cli)", | ||
"version": "0.4.0", | ||
"version": "0.4.1", | ||
"author": { | ||
@@ -21,3 +21,3 @@ "name": "Drew Powers", | ||
"devDependencies": { | ||
"@cobalt-ui/core": "^0.6.0" | ||
"@cobalt-ui/core": "^0.6.1" | ||
}, | ||
@@ -27,4 +27,3 @@ "scripts": { | ||
"dev": "tsc -w" | ||
}, | ||
"readme": "# @cobalt-ui/plugin-json\n\nGenerate JSON output from design tokens.\n\n```\nnpm i -D @cobalt-ui/plugin-json\n```\n\n```js\n// tokens.config.mjs\nimport json from '@cobalt-ui/plugin-json';\n\nexport default {\n plugins: [\n json({\n /** set the filename inside outDir */\n filename: './tokens.json',\n }),\n ],\n};\n```\n\nIt’s worth noting that this JSON output differs from your source `tokens.json` in a number of ways:\n\n- It’s one flat array, making iterating over all your tokens easy without deep-crawling objects\n- All values are normalized, so you won’t get unexpected missing values\n- All shared properties are filled in, e.g. if a group has a default `type` it will be applied to all children tokens\n- All aliases are resolved, so you don’t have to recursively crawl `tokens.json` yourself\n- The original token value can be found in `_original`\n- Information about a token’s parent group can be found in `_group`\n\nSo if you have need for any of the above, this format can be much friendlier to iterate over than the original schema.\n" | ||
} | ||
} |
@@ -13,2 +13,3 @@ # @cobalt-ui/plugin-json | ||
/** @type import('@cobalt-ui/core').Config */ | ||
export default { | ||
@@ -15,0 +16,0 @@ plugins: [ |
34
7270