Kelly Mears

@peXed you might try to configure the watch server: ```typescript app.hooks.on('dev.watch.options', () => ({/* chokidar watch options */})) ``` `@roots/bud-server` just uses the chokidar defaults. It isn't a particularly deep...

This is confirmed working by this discourse thread. Looks like you need to edit within the container. https://discourse.roots.io/t/yarn-dev-not-watching/24068/6?u=ben

That's the default behavior of `postcss-custom-properties`, I believe. https://postcss.github.io/postcss-custom-properties/

First, I'm not sure what this setting is _exactly_. But I'd start looking here: - https://github.com/csstools/postcss-plugins/tree/main/plugin-packs/postcss-preset-env - https://github.com/csstools/postcss-plugins/tree/main/plugins/postcss-custom-properties#postcss-custom-properties- The bud.js.org docs actually have a lot of information on setting postcss...

Whether this should or shouldn't be default in `postcss-preset-env` really isn't a question for bud.js. We just ship default config (with one override, but maybe even that is too opinionated?)...

`entry` is a full implementation of the webpack entry api. so, even though most people will use it like this: ```ts bud.entry('app', ['app.js']) ``` it's possible to use it like...

This is an issue with WordPress. Calling `unregisterBlockStyle` in either a `@wordpress/dom-ready` or `@roots/sage/client/dom-ready` callback will not work _reliably_. The intent is that it should, I think. See this issue:...

I haven't looked at this super closely yet but at first glance: you can't dynamically import WordPress dependencies as they are included via window variables. As in, your source: ```js...

If I replace the `node:*` with the non namespaced equivalents manually, it works. I think `@yarnpkg/builder` might need to include `node:*` as externals.

I patched it with an esbuild plugin, which should do for now.