A bugfix release for bud v6.6.x.
fix: wordpress@6.?.? enqueues react-refresh on its own #1913
breaking
react-refresh is no longer enqueued automatically. wordpress seems to be enqueuing it now; I’m guessing when
WP_ENV
isdevelopment
.bud.react.refresh.enable()
needs to be called in your config if you want to addreact-refresh
to entrypoints (but you’ll wind up with two instances ofreact-refresh
running in the browser if you don’t do anything to account for the wordpress behavior!)
fix: @roots/bud-server proxy #1913
This fixes problems with 6.6.3 and 6.6.4’s proxy server setup. It also makes a backwards compatible change to the bud.proxy
API. The docs have been expanded, as well.
improve: bud.proxy api improvements
docs: add bud.proxy options
test: expands unit tests for bud.proxy
fix: @roots/browserslist-config #1920
Fixes caniuse-lite
upgrade notices and prevents lockfile conflicts. caniuse-lite
now updated when @roots/bud
is installed.
fix: @roots/browserslist-config caniuse-lite upgrade issue
add: export exact copy of default wp config:
@roots/browserslist-config/wordpress
add: export exact copy of default next.js config:
@roots/browserslist-config/next
fix: bud.provide does not accept string values in object #1911
Surfaced by this discourse topic.
fix: bud.provide should accept
object
withstring
values.docs: update bud.provide documentation
test: add unit tests for
string
andarray
values