Sync Figma variables to tokens #98
sync-figma-to-tokens.yml
on: schedule
sync-figma-to-tokens
1m 23s
Annotations
1 error and 1 warning
sync-figma-to-tokens
Unexpected error: .husky/pre-commit: 4: Bad substitution
.husky/pre-commit: 5: Bad substitution
..Running design token checks
> [email protected] paddingY:verify
> tsx src/scripts/verify-paddingY.ts
> [email protected] build
> rm -rf ./dist && yarn build-style-dictionary
yarn run v1.22.22
$ tsx src/scripts/build-style-dictionary.js
js
✔︎ dist/esm/base.js
js/cjs
✔︎ dist/cjs/base.cjs
css
✔︎ dist/css/base.css
docs
✔︎ dist/docs/base.js
js
✔︎ dist/esm/global.js
js/cjs
✔︎ dist/cjs/global.cjs
docs
⚠️ dist/docs/global.js
While building global.js, filtered out token references were found; output may be unexpected. Ignore this warning if intentional.
Here are the references that are used but not defined in the file:
color.focus
base.dimension.50
This is caused when combining a filter and `outputReferences`.
css
✔︎ dist/css/global.css
js
✔︎ dist/esm/color.light.js
js/cjs
✔︎ dist/cjs/color.light.cjs
css
⚠️ dist/css/color.light.css
While building color.light.css, token collisions were found; output may be unexpected. Ignore this warning if intentional.
Output name hpe-color-decorative-green was generated by:
color.decorative.green #17eba0
color.decorative.green! #01a982
Output name hpe-color-decorative-purple was generated by:
color.decorative.purple #f740ff
color.decorative.purple! #7630ea
Output name hpe-color-decorative-teal was generated by:
color.decorative.teal #82fff2
color.decorative.teal! #00e8cf
Output name hpe-color-decorative-blue was generated by:
color.decorative.blue #00c8ff
color.decorative.blue! #00739d
Output name hpe-color-decorative-red was generated by:
color.decorative.red #fc6161
color.decorative.red! #c54e4b
Output name hpe-color-decorative-orange was generated by:
color.decorative.orange #ffbc44
color.decorative.orange! #ff8300
Output name hpe-color-decorative-yellow was generated by:
color.decorative.yellow #ffeb59
color.decorative.yellow! #fec901
This many-to-one issue is usually caused by some combination of:
* conflicting or similar paths/names in token definitions
* platform transforms/transformGroups affecting names, especially when removing specificity
* overly inclusive file filters
docs
✔︎ dist/docs/color.light.js
css
✔︎ dist/css/dimension.medium.css
css
✔︎ dist/css/dimension.small.css
js
✔︎ dist/esm/dimension.medium.js
js/cjs
✔︎ dist/cjs/dimension.medium.cjs
docs
✔︎ dist/docs/dimension.medium.js
js
✔︎ dist/esm/dimension.small.js
js/cjs
✔︎ dist/cjs/dimension.small.cjs
docs
✔︎ dist/docs/dimension.small.js
js
✔︎ dist/esm/components.default.js
js/cjs
✔︎ dist/cjs/components.default.cjs
docs
⚠️ dist/docs/components.js
While building components.js, filtered out token references were found; output may be unexpected. Ignore this warning if intentional.
Here are the references that are used but not defined in the file:
base.static.spacing.xxsmall
base.dimension.600
base.dimension.75
text.xsmall.fontSize
base.fontSize.90
text.xsmall.lineHeight
base.lineHeight.90
borderWidth.default
base.static.borderWidth.xsmall
base.static.spacing.xsmall
base.dimension.150
base.dimension.225
size.icon.xsmall
base.dimension.400
base.static.borderWidth.default
base.dimension.25
text.small.fontSize
base.fontSize.100
text.small.lineHeight
base.lineHeight.100
base.dimension.700
base.static.spacing.small
base.dimension.300
size.icon.small
text.medium.fontSize
base.fontSize.200
text.medium.lineHeight
base.lineHeight.200
base.dimension.900
base.dimension.450
size.icon.medium
text.large.fontSize
base.fontSize.400
text.large.lineHeight
base.lineHeight.300
base.dimension.1200
size.icon.large
base.dimension.550
text.xlarge.fontSize
base.fontSize.500
text.xlarge.lineHeight
base.lineHeight.400
base.dimension.1800
base.dimension.500
size.ico
|
sync-figma-to-tokens
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-node@v3, actions/checkout@v3, peter-evans/create-pull-request@v5. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|