You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Makes it possible to write client code in blade files. This is different than existing solutions because the code is parsed with other loaders (you can write postcss, sass, typescript, etc.)
Supports: js, ts, css, scss, vue.
Code is specified using @js/@endjs syntax (with whatever extension).
Included in this PR (sources/@​roots/blade-loader/vendor) are directives that can be used to stop src from rendering (uses ob_start and ob_end_clean).
I imagine there will be first-party support added to Sage in the near future. For now, you could try out this feature using blade comments:
WordPress dependencies which are imported are not included in entrypoints.json. It's unclear as of yet why. Workaround is to do the imports from a legitimate js module and then import that from the blade file:
node.js has updated LTS version and so have we. It's fine to use Node 16 in your project for now, but you should upgrade sooner rather than later.
It's tentative but we'll likely drop support for older versions of Node in bud v7 (mainly so we can use the new built-in fetch). Previously we were blocked on this due to an issue in GoogleChromeLabs/squoosh but merging #2012 has gotten us back on track.
Please don't do this in an extension you plan on distributing.
Do you just want to add a rule in your project config and don't need to worry about ecosystem compatibility? You can now add rules with standard webpack syntax. Example below but the loaders guide on bud.js.org has been updated to cover this in more detail:
Breaks the bud.wpjson feature from @roots/sage into two extensions and a webpack plugin to be combined as needed in projects. @roots/sage now includes these extensions as part of the preset it provides. See the PR for details.
Fixes an issue where setting a proper hostname (fully qualified URL or string; rather than an interface or a port) would cause proxied assets to 500.
🩹 fix: ensure process exit code is set on compilation error (#1985)
Fixes an issue where process exit code would not be set to 1 even if an error is not explicitly thrown by compiler. Adds integration test to protect against regressions.
📦 dependencies: improve peer dependencies
Better defines peer dependencies. This should hep guarantee a flat node_modules and an easier time for users of package managers with stricter peer dependencies resolution strategies (like pnpm).
Makes it possible to write client code in blade files. This is different than existing solutions because the code is parsed with other loaders (you can write postcss, sass, typescript, etc.)
Supports: js, ts, css, scss, vue.
Code is specified using @js/@endjs syntax (with whatever extension).
Included in this PR (sources/@​roots/blade-loader/vendor) are directives that can be used to stop src from rendering (uses ob_start and ob_end_clean).
I imagine there will be first-party support added to Sage in the near future. For now, you could try out this feature using blade comments:
WordPress dependencies which are imported are not included in entrypoints.json. It's unclear as of yet why. Workaround is to do the imports from a legitimate js module and then import that from the blade file:
node.js has updated LTS version and so have we. It's fine to use Node 16 in your project for now, but you should upgrade sooner rather than later.
It's tentative but we'll likely drop support for older versions of Node in bud v7 (mainly so we can use the new built-in fetch). Previously we were blocked on this due to an issue in GoogleChromeLabs/squoosh but merging #2012 has gotten us back on track.
Please don't do this in an extension you plan on distributing.
Do you just want to add a rule in your project config and don't need to worry about ecosystem compatibility? You can now add rules with standard webpack syntax. Example below but the loaders guide on bud.js.org has been updated to cover this in more detail:
Breaks the bud.wpjson feature from @roots/sage into two extensions and a webpack plugin to be combined as needed in projects. @roots/sage now includes these extensions as part of the preset it provides. See the PR for details.
Fixes an issue where setting a proper hostname (fully qualified URL or string; rather than an interface or a port) would cause proxied assets to 500.
🩹 fix: ensure process exit code is set on compilation error (#1985)
Fixes an issue where process exit code would not be set to 1 even if an error is not explicitly thrown by compiler. Adds integration test to protect against regressions.
📦 dependencies: improve peer dependencies
Better defines peer dependencies. This should hep guarantee a flat node_modules and an easier time for users of package managers with stricter peer dependencies resolution strategies (like pnpm).
Makes it possible to write client code in blade files. This is different than existing solutions because the code is parsed with other loaders (you can write postcss, sass, typescript, etc.)
Supports: js, ts, css, scss, vue.
Code is specified using @js/@endjs syntax (with whatever extension).
Included in this PR (sources/@​roots/blade-loader/vendor) are directives that can be used to stop src from rendering (uses ob_start and ob_end_clean).
I imagine there will be first-party support added to Sage in the near future. For now, you could try out this feature using blade comments:
WordPress dependencies which are imported are not included in entrypoints.json. It's unclear as of yet why. Workaround is to do the imports from a legitimate js module and then import that from the blade file:
node.js has updated LTS version and so have we. It's fine to use Node 16 in your project for now, but you should upgrade sooner rather than later.
It's tentative but we'll likely drop support for older versions of Node in bud v7 (mainly so we can use the new built-in fetch). Previously we were blocked on this due to an issue in GoogleChromeLabs/squoosh but merging #2012 has gotten us back on track.
Please don't do this in an extension you plan on distributing.
Do you just want to add a rule in your project config and don't need to worry about ecosystem compatibility? You can now add rules with standard webpack syntax. Example below but the loaders guide on bud.js.org has been updated to cover this in more detail:
Breaks the bud.wpjson feature from @roots/sage into two extensions and a webpack plugin to be combined as needed in projects. @roots/sage now includes these extensions as part of the preset it provides. See the PR for details.
Fixes an issue where setting a proper hostname (fully qualified URL or string; rather than an interface or a port) would cause proxied assets to 500.
🩹 fix: ensure process exit code is set on compilation error (#1985)
Fixes an issue where process exit code would not be set to 1 even if an error is not explicitly thrown by compiler. Adds integration test to protect against regressions.
📦 dependencies: improve peer dependencies
Better defines peer dependencies. This should hep guarantee a flat node_modules and an easier time for users of package managers with stricter peer dependencies resolution strategies (like pnpm).
This PR contains the following updates:
6.6.9
->6.7.1
6.6.9
->6.7.1
6.6.9
->6.7.1
Release Notes
roots/bud (@roots/bud)
v6.7.1
Compare Source
v6.7.0
Compare Source
A healthy mix of features and fixes.
There are changes to the API of @roots/bud-imagemin to be aware of if you are using that extension and have customized generators or minimizers.
✨ feat(@roots/sage): process blade templates with @roots/blade-loader #2035
This is a cool feature.
Makes it possible to write client code in blade files. This is different than existing solutions because the code is parsed with other loaders (you can write postcss, sass, typescript, etc.)
Supports: js, ts, css, scss, vue.
Code is specified using
@js
/@endjs
syntax (with whatever extension).Example:
index.blade.php
:bud.config.js
:Included in this PR (
sources/@​roots/blade-loader/vendor
) are directives that can be used to stop src from rendering (usesob_start
andob_end_clean
).I imagine there will be first-party support added to Sage in the near future. For now, you could try out this feature using blade comments:
If you use @roots/bud-imagemin you can now do image manipulation on-the-fly in blade templates:
WordPress dependencies which are imported are not included in
entrypoints.json
. It's unclear as of yet why. Workaround is to do the imports from a legitimate js module and then import that from the blade file:🩹 fix(@roots/wordpress-hmr): duplicative block registrations #2023
Fixes issues in some setups where blocks would be registered more than once.
🩹 fix(cli): --cwd flag #2008
Fixes two related issues which caused the
--cwd
/--basedir
flag to not work properly📦 deps: bump node to v18 lts #1962
node.js has updated LTS version and so have we. It's fine to use Node 16 in your project for now, but you should upgrade sooner rather than later.
It's tentative but we'll likely drop support for older versions of Node in bud v7 (mainly so we can use the new built-in fetch). Previously we were blocked on this due to an issue in GoogleChromeLabs/squoosh but merging #2012 has gotten us back on track.
📦 deps(@roots/bud-imagemin): use sharp instead of squoosh #2012
squoosh was abandoned by google. we're using sharp internally now. See the PR for details. API changes are documented on bud.js.org.
✨ improve(@roots/bud-build): allow adding raw webpack rules #2010
Please don't do this in an extension you plan on distributing.
Do you just want to add a rule in your project config and don't need to worry about ecosystem compatibility? You can now add rules with standard webpack syntax. Example below but the loaders guide on bud.js.org has been updated to cover this in more detail:
🩹 fix: ensure process exit code is set on compilation error #1985
Fixes #1986.
Reproduction incorporated into testing suite to prevent future regressions.
v6.6.10
Compare Source
🔧 decouple theme json from @roots/sage (#1982)
Breaks the
bud.wpjson
feature from@roots/sage
into two extensions and a webpack plugin to be combined as needed in projects.@roots/sage
now includes these extensions as part of the preset it provides. See the PR for details.🩹 fix(@roots/sage): serve options including hostname (#1983)
Fixes an issue where setting a proper hostname (fully qualified URL or string; rather than an interface or a port) would cause proxied assets to 500.
🩹 fix: ensure process exit code is set on compilation error (#1985)
Fixes an issue where process exit code would not be set to 1 even if an error is not explicitly thrown by compiler. Adds integration test to protect against regressions.
📦 dependencies: improve peer dependencies
Better defines peer dependencies. This should hep guarantee a flat
node_modules
and an easier time for users of package managers with stricter peer dependencies resolution strategies (like pnpm).Associated PRs:
🙏🏼 Update package.json contributors
Now automatically pulling contributors from git history and crediting in each package's manifest. Thanks to everyone!
roots/bud (@roots/bud-tailwindcss)
v6.7.1
Compare Source
v6.7.0
Compare Source
A healthy mix of features and fixes.
There are changes to the API of @roots/bud-imagemin to be aware of if you are using that extension and have customized generators or minimizers.
✨ feat(@roots/sage): process blade templates with @roots/blade-loader #2035
This is a cool feature.
Makes it possible to write client code in blade files. This is different than existing solutions because the code is parsed with other loaders (you can write postcss, sass, typescript, etc.)
Supports: js, ts, css, scss, vue.
Code is specified using
@js
/@endjs
syntax (with whatever extension).Example:
index.blade.php
:bud.config.js
:Included in this PR (
sources/@​roots/blade-loader/vendor
) are directives that can be used to stop src from rendering (usesob_start
andob_end_clean
).I imagine there will be first-party support added to Sage in the near future. For now, you could try out this feature using blade comments:
If you use @roots/bud-imagemin you can now do image manipulation on-the-fly in blade templates:
WordPress dependencies which are imported are not included in
entrypoints.json
. It's unclear as of yet why. Workaround is to do the imports from a legitimate js module and then import that from the blade file:🩹 fix(@roots/wordpress-hmr): duplicative block registrations #2023
Fixes issues in some setups where blocks would be registered more than once.
🩹 fix(cli): --cwd flag #2008
Fixes two related issues which caused the
--cwd
/--basedir
flag to not work properly📦 deps: bump node to v18 lts #1962
node.js has updated LTS version and so have we. It's fine to use Node 16 in your project for now, but you should upgrade sooner rather than later.
It's tentative but we'll likely drop support for older versions of Node in bud v7 (mainly so we can use the new built-in fetch). Previously we were blocked on this due to an issue in GoogleChromeLabs/squoosh but merging #2012 has gotten us back on track.
📦 deps(@roots/bud-imagemin): use sharp instead of squoosh #2012
squoosh was abandoned by google. we're using sharp internally now. See the PR for details. API changes are documented on bud.js.org.
✨ improve(@roots/bud-build): allow adding raw webpack rules #2010
Please don't do this in an extension you plan on distributing.
Do you just want to add a rule in your project config and don't need to worry about ecosystem compatibility? You can now add rules with standard webpack syntax. Example below but the loaders guide on bud.js.org has been updated to cover this in more detail:
🩹 fix: ensure process exit code is set on compilation error #1985
Fixes #1986.
Reproduction incorporated into testing suite to prevent future regressions.
v6.6.10
Compare Source
🔧 decouple theme json from @roots/sage (#1982)
Breaks the
bud.wpjson
feature from@roots/sage
into two extensions and a webpack plugin to be combined as needed in projects.@roots/sage
now includes these extensions as part of the preset it provides. See the PR for details.🩹 fix(@roots/sage): serve options including hostname (#1983)
Fixes an issue where setting a proper hostname (fully qualified URL or string; rather than an interface or a port) would cause proxied assets to 500.
🩹 fix: ensure process exit code is set on compilation error (#1985)
Fixes an issue where process exit code would not be set to 1 even if an error is not explicitly thrown by compiler. Adds integration test to protect against regressions.
📦 dependencies: improve peer dependencies
Better defines peer dependencies. This should hep guarantee a flat
node_modules
and an easier time for users of package managers with stricter peer dependencies resolution strategies (like pnpm).Associated PRs:
🙏🏼 Update package.json contributors
Now automatically pulling contributors from git history and crediting in each package's manifest. Thanks to everyone!
roots/bud (@roots/sage)
v6.7.1
Compare Source
v6.7.0
Compare Source
A healthy mix of features and fixes.
There are changes to the API of @roots/bud-imagemin to be aware of if you are using that extension and have customized generators or minimizers.
✨ feat(@roots/sage): process blade templates with @roots/blade-loader #2035
This is a cool feature.
Makes it possible to write client code in blade files. This is different than existing solutions because the code is parsed with other loaders (you can write postcss, sass, typescript, etc.)
Supports: js, ts, css, scss, vue.
Code is specified using
@js
/@endjs
syntax (with whatever extension).Example:
index.blade.php
:bud.config.js
:Included in this PR (
sources/@​roots/blade-loader/vendor
) are directives that can be used to stop src from rendering (usesob_start
andob_end_clean
).I imagine there will be first-party support added to Sage in the near future. For now, you could try out this feature using blade comments:
If you use @roots/bud-imagemin you can now do image manipulation on-the-fly in blade templates:
WordPress dependencies which are imported are not included in
entrypoints.json
. It's unclear as of yet why. Workaround is to do the imports from a legitimate js module and then import that from the blade file:🩹 fix(@roots/wordpress-hmr): duplicative block registrations #2023
Fixes issues in some setups where blocks would be registered more than once.
🩹 fix(cli): --cwd flag #2008
Fixes two related issues which caused the
--cwd
/--basedir
flag to not work properly📦 deps: bump node to v18 lts #1962
node.js has updated LTS version and so have we. It's fine to use Node 16 in your project for now, but you should upgrade sooner rather than later.
It's tentative but we'll likely drop support for older versions of Node in bud v7 (mainly so we can use the new built-in fetch). Previously we were blocked on this due to an issue in GoogleChromeLabs/squoosh but merging #2012 has gotten us back on track.
📦 deps(@roots/bud-imagemin): use sharp instead of squoosh #2012
squoosh was abandoned by google. we're using sharp internally now. See the PR for details. API changes are documented on bud.js.org.
✨ improve(@roots/bud-build): allow adding raw webpack rules #2010
Please don't do this in an extension you plan on distributing.
Do you just want to add a rule in your project config and don't need to worry about ecosystem compatibility? You can now add rules with standard webpack syntax. Example below but the loaders guide on bud.js.org has been updated to cover this in more detail:
🩹 fix: ensure process exit code is set on compilation error #1985
Fixes #1986.
Reproduction incorporated into testing suite to prevent future regressions.
v6.6.10
Compare Source
🔧 decouple theme json from @roots/sage (#1982)
Breaks the
bud.wpjson
feature from@roots/sage
into two extensions and a webpack plugin to be combined as needed in projects.@roots/sage
now includes these extensions as part of the preset it provides. See the PR for details.🩹 fix(@roots/sage): serve options including hostname (#1983)
Fixes an issue where setting a proper hostname (fully qualified URL or string; rather than an interface or a port) would cause proxied assets to 500.
🩹 fix: ensure process exit code is set on compilation error (#1985)
Fixes an issue where process exit code would not be set to 1 even if an error is not explicitly thrown by compiler. Adds integration test to protect against regressions.
📦 dependencies: improve peer dependencies
Better defines peer dependencies. This should hep guarantee a flat
node_modules
and an easier time for users of package managers with stricter peer dependencies resolution strategies (like pnpm).Associated PRs:
🙏🏼 Update package.json contributors
Now automatically pulling contributors from git history and crediting in each package's manifest. Thanks to everyone!
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR has been generated by Mend Renovate. View repository job log here.
Originally posted by @renovate in roots/sage#3106
The text was updated successfully, but these errors were encountered: