roots / sage

WordPress starter theme with Laravel Blade components and templates, Tailwind CSS, and a modern development workflow
https://roots.io/sage/
MIT License
12.71k stars 3.06k forks source link

chore(deps): ⬆️ bump bud to v6.9.0 #3123

Closed renovate[bot] closed 1 year ago

renovate[bot] commented 1 year ago

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@roots/bud (source) 6.8.0 -> 6.9.0 age adoption passing confidence
@roots/bud-tailwindcss 6.8.0 -> 6.9.0 age adoption passing confidence
@roots/sage 6.8.0 -> 6.9.0 age adoption passing confidence

Release Notes

roots/bud ### [`v6.9.0`](https://togithub.com/roots/bud/releases/tag/v6.9.0) [Compare Source](https://togithub.com/roots/bud/compare/v6.8.0...v6.9.0) An easy helper for dealing with uncompiled modules, dot notation getters and setters for extension options, and a bugfix for the typescript+vue support introduced in 6.8.0 ##### 🩹 fix: vue/typescript [#​2082](https://togithub.com/roots/bud/pull/2082) Moves `css`, `scss`,`ts` rules out of `oneOf` and into the top-level `module.rules` array. Fixes: - [#​2080 \[bug\] vue-typescript example does not build (possible @​roots/bud-sass issue)](https://togithub.com/roots/bud/issues/2080) - [#​2081 \[bug\] Vue SFC ts breaks build](https://togithub.com/roots/bud/issues/2081) ##### ✨ feature([@​roots/bud](https://togithub.com/roots/bud)): bud.compilePaths [#​2083](https://togithub.com/roots/bud/pull/2083) [bud.compilePaths](https://bud.js.org/docs/bud.compilePaths) is used to specify directories which should be treated as source directories. This serves as a simple replacement for the instructions found in the [compiler sources guide](https://bud.js.org/guides/general-use/compiler-sources). If you have errors which say something along the lines of `You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file.`, this is probably the function you want to use to fix that. Example adding support for the swiper lib: ```typescript export default async bud => { bud.compilePaths([ bud.path(`@src`), bud.path(`@modules/swiper`), ]) } ``` ##### ✨ improve([@​roots/bud](https://togithub.com/roots/bud)): options api [#​2078](https://togithub.com/roots/bud/pull/2078) A small change but a good one. Backwards compatible but it will let us remove a lot of extension methods in bud@7.0. ```ts export default async bud => { bud.wpjson .set(`settings.color.customDuotone`, false) .set(`settings.color.customGradient`, false) .set(`settings.color.defaultDuotone`, false) .set(`settings.color.defaultGradients`, false) .set(`settings.color.defaultPalette`, false) .set(`settings.color.duotone`, []) .enable() bud.tailwind.set(`generateImports`, true) bud.typescript .set(`appendTsSuffixTo`, [/\.vue$/]) .typecheck.enable() bud.terser .set(`extractComments`, false) .set(`terserOptions.mangle.safari10`, false) bud.vue.set(`runtimeOnly`, false) bud.imagemin.sharp .set(`encodeOptions.png.quality`, 60) .set(`encodeOptions.webp.quality`, 60) } ``` Can also retrieve options with `get`: ```ts bud.vue.get(`runtimeOnly`) ``` Right now these dot props are not type safe and you may get feedback in your IDE that the option name doesn't exist. More work is roadmapped to address this, but it's very complicated to do dot notation type transformations on generics with recursive or very deeply nested properties. If this is a problem for you you can do the prop drilling yourself with `extension.getOptions()` and `extension.setOptions()`.

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.