Mihkel Eidast
Mihkel Eidast
Ran into this myself. Solved it by adding to wrapper elements (ugh, I know) to the existing flex parent that have the styles ``` .wrapper { display: flex; } .wrapper-inner...
After a bit of trial and error, I found a workaround for this issue. I need to add `freesans` to my CSS font stack before the default `sans-serif` final fallback....
Two notes I ran into today when trying to update: - the tags are prefixed with `v`, so when using a specific version, need to remember that: `image: validator/validator:v20.0.28`. This...
As far as I know, this is still a problem. A workaround I have used is setting `"baseUrl": "./src",` in my tsconfig, that way it does not try to resolve...
This worked pre-1.0.0. We ran into issues after updating. We've rolled back to 0.7.2 for now, until this is solved.
@moroshko thanks for the feedback, I added returning the output from the function, plus a couple of tests as well. The CI seems to be failing on test coverage, though...
Seems like CI runs on Node 12, if I use it locally, it also fails on some weird lines, like the final `}` of the run function, which I do...
@moroshko done, updated to Node 16, all green now!
Sharing my CSS transform as well - this supports stacked shadow tokens, as well as aliased color references, and inset shadows: ```js StyleDictionaryPackage.registerTransform({ name: 'shadow/css', type: 'value', // necessary in...
> Q on this: you'd only want to reference multiple single shadow tokens that way? Or would you expect if you reference a shadow token that has 3 layers of...