Fred Boyle

Thanks for the quick response @jonschlinkert. We have config files that are mostly simple `module.exports =` but they are consumed by a runner that loads it and starts a server...

Ugh that's a bummer. Thanks.

@romainmenke Seems reasonable to me and not much of a burden on developers. Makes things a bit more universal and without the need to calculate relative paths every time.

Doing some digging and it appears `GroupMessages.GROUP.FilteredOutputReferences` has what might be needed. If something like this was added: ```javascript if (options.valuesForFilteredOutReferences === true && GroupMessages.GROUP.FilteredOutputReferences.contains(ref.name)) { return token.value; } ```...

Put together a quick hack for a component but it would still be nice if Floating UI did this automatically. ```js // Add the Floating UI data attribute if (refs.elem.current)...

After much trial and error I did manage to succeed with a custom formatter. I'm not certain this is the best approach but thought I'd share my current solution so...

@spirkolos Attached is a screenshot of the directory structure in our project. You'll notice that Style Dictionary is self contained within a subdirectory. When we run our custom Style Dictionary...

```json { "source": ["tokens/**/*.json"], "platforms": { "scss": { "transformGroup": "custom/scss", "prefix": "pds", "buildPath": "src/styles/global/", "files": [ { "destination": "_variables.scss", "format": "scss/variables" } ] }, "css": { "transformGroup": "custom/css", "prefix": "pds",...

Checking in for any help on this. Thanks.