v4.3.0
v4.3.0 adds the bud extensions cli command. This is the recommended way to ensure peer dependencies are met when installing new extensions. After installing a bud extension, please run bud extensions:install (or its alias: bud init).
To see what extensions are being utilized in a project you can run bud extensions:list.
There are changes to the cli interface which wil be immediately noticable, but no changes to public-facing APIs.
This release also bumps dependencies to their most recent versions and includes numerous bug fixes.
To review all the merges that make up this release, refer to the v4.3.0 milestone.
Added
bud extensionscommand
Improved
@roots/bud-typescriptonly booted if peer dependencies are met@roots/bud-postcssonly booted if peer dependencies are met@roots/bud-reactonly booted if peer dependencies are met@roots/sageloads extensions conditionally based on peer dependencies--cishould be much more reliable- Builds should be significantly faster
Fixed
- Hanging processes with cli commands
- plain js compilation (without transpilation) now works correctly (see #82)
@roots/bud-vuefixed (loader incompatible with webpack'soneOf)- Fixes errors when using memory based caching
- Fixes errors when using fs based caching
Internals
- Project now using Jest for tests (h/t @QWp6t)
- Test: suite for
@roots/container - Test: suite for
@roots/bud-build - Test: several methods from
@roots/bud-api
Contributors
- kellymears kelly@roots.io
- QWp6t hi@qwp6t.me