Joren Broekema

Our APIs for registering custom things should be more consistent, it's currently quite confusing and easy to make mistakes due to lack of consistency. Before: ```js registerParser({ pattern: /\.json$/g, parse:...

outputReferences & iterative lifecycle restructure

2

This issue is a proposal for changing some of Style-Dictionary's core architecture with regards to resolving references and transforms. It goes over two topics, but they are quite interconnected hence...

Transforms that run after all references have been resolved

2

I'd like to propose adding a property to transforms that indicates they ought to be ran after references have been resolved entirely. This means that transforms can be ran in...

# Security tracker dependencies > This issue can be used for tracking security vulnerabilities in our direct dependencies, which should be fixed with high urgency. If they cannot be auto-fixed,...

# Security tracker devDependencies > This issue can be used for tracking security vulnerabilities in our devDependencies **which cannot be auto-fixed**, which should be acknowledged and actions taken to notify...

From the perspective of CSS , you cannot put a CSS custom property just anywhere. Example: ```css :root { --my-rgb: #ff0000; --my-rgba: rgba(var(--my-rgba), 0.8); } ``` Is invalid CSS and...

## Feature Request For the CSS property formatter or as a CSS-specific value transform (I prefer the latter, format should not be concerned much with token value changes). ```css :root...

Drop Lodash

2

@tahul Mostly wanna drop this because Lodash is quite a node_modules bloating thing, and usually modern JS can do it already anyway. We don't use that much of lodash anyway,...

@tahul Needs a bit of discussion, I aim to redesign this a bit and ensure that we have better comprehensive logging, ensure we don't bloat the console too much (e.g....

fix(less): upgrade make-dir to v4 to fix security vulnerability

2

fixes https://github.com/less/less.js/issues/3806 **What**: Bump make-dir to v4 **Why**: There is a security vulnerability in make-dir v2: ``` $ npm ls semver [email protected] project └─┬ [email protected] └── [email protected] ``` Which is...