Kelly Mears

- what is the output of `yarn bud doctor`? - what about verbose logging `yarn bud build -vvvv`? don't need the full output; just looking for any extra information. -...

`node -v`?

with `npm` can you: 1. run `bud build --debug` 2. open `.budfiles/sage/webpack.config.dump` 3. search for `postcss` and post the matching rule the object should look something like this: ```ts Object...

seems correct. the `--log` flag might give more insight with `npm`, as well. we might be blocked on this unless you can do a minimal reproduction.

I finally experienced it (after god knows how many builds in CI..). I _believe_ I have fixed it as part of #1697. Specifically the removal of this logger call: https://github.com/roots/bud/pull/1697/files#diff-a9ad3e31d1118714865b8bd0a1ded58e346e0c94c77e858acdcbbc55f8d70820L130-L133...

This should be fixed in [v6.4.2](https://bud.js.org/blog/6.4.2) by https://github.com/roots/bud/commit/a5dfd7aa48257e2ac5ebad91584a850632ac5721. Please feel free to reopen this issue if you are still having problems. It is a hard issue to reliably reproduce so...

i feel like `get`, as a verb, especially attached to a public method, strongly implies that this is the getting place. i think if the method is lacking in some...

that's a good idea. i'll include in next `@roots/sage` release.

this would obviously need to be updated, but I'm thinking we can revisit now. This: ```ts app.wpjson .settings((theme) => theme.set("typography.customFontSize", true)) .enable(); ``` Yields the expected result: ```ts { "__generated__":...

I approve of this. We use yarn v3 with node-linker in the roots/bud monorepo. I think it's a good tool and I agree it's a better overall tool than yarn...