roots/bud
### [`v6.12.1`](https://togithub.com/roots/bud/releases/tag/v6.12.1): 6.12.1
[Compare Source](https://togithub.com/roots/bud/compare/v6.12.0...v6.12.1)
Minor release with improvements and fixes for package resolution and caching
#### Fixes
##### Failure installing custom TypeScript version with yarn
Fixes an error encountered when trying to install a custom version of TypeScript while using `@roots/bud-typescript` with yarn classic. [See #2216](https://togithub.com/roots/bud/issues/2216).
This issue is actually an upstream bug in yarn. But, our response sidesteps it and also improves compatibility with pnpm.
The short version: we don't need to declare `typescript` as a peer dependency because of changes to `bud.module` made in bud v6. It will always try to resolve from the project context before using the built-in as a fallback.
So, even without peer dependencies defined by the extension, the following call (when made from the `@roots/bud-typescript` context) will always try and resolve the module first from `node_modules/typescript`, and then `node_modules/@roots/bud-typescript/node_modules`.
```ts
bud.module.resolve(`typescript`, import.meta.url)
```
The change that fixes [#2216](https://togithub.com/roots/bud/issues/2216) has also been applied to `@roots/bud-eslint` and `@roots/bud-babel`. We'll apply it to other packages which use `peerDependencies` in future releases.
#### Improvements
##### Include eslint and tailwind configs in build dependencies
[#2233 Include tailwind & eslint configs in cached build dependencies](https://togithub.com/roots/bud/pull/2233) adds discovered `tailwind` and `eslint` configs to the map of files the compiler uses to validate the cache. Hopefully changes made to your tailwind config will now be more reliably reflected in your next build without having to use the `--force` flag. Additionally, only modules related to the changed config will be invalidated, which will be much faster than wiping everything.
##### Prevent invoking multiple `esbuild` and/or `esbuild-wasm` modules
When transforming configuration modules authored in TypeScript bud.js will now prefer `esbuild` or `esbuild-wasm` as defined by `package.json`, if they are included. The built-in `esbuild-wasm` included in `@roots/bud-support` is used as a fallback. This should be a minor improvement for users who are using `esbuild` in some other way as part of their build.
##### Vendor `bind` decorator from `helpful-decorators`.
`helpful-decorators` is an awesome package but we are only using `bind` from it and it is used in a lot of places. This change eliminates the (modest) overhead associated with all the unused modules.
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.
[ ] If you want to rebase/retry this PR, check this box
This PR has been generated by Mend Renovate. View repository job log here.
This PR contains the following updates:
6.12.0->6.12.16.12.0->6.12.16.12.0->6.12.1Release Notes
roots/bud
### [`v6.12.1`](https://togithub.com/roots/bud/releases/tag/v6.12.1): 6.12.1 [Compare Source](https://togithub.com/roots/bud/compare/v6.12.0...v6.12.1) Minor release with improvements and fixes for package resolution and caching #### Fixes ##### Failure installing custom TypeScript version with yarn Fixes an error encountered when trying to install a custom version of TypeScript while using `@roots/bud-typescript` with yarn classic. [See #2216](https://togithub.com/roots/bud/issues/2216). This issue is actually an upstream bug in yarn. But, our response sidesteps it and also improves compatibility with pnpm. The short version: we don't need to declare `typescript` as a peer dependency because of changes to `bud.module` made in bud v6. It will always try to resolve from the project context before using the built-in as a fallback. So, even without peer dependencies defined by the extension, the following call (when made from the `@roots/bud-typescript` context) will always try and resolve the module first from `node_modules/typescript`, and then `node_modules/@roots/bud-typescript/node_modules`. ```ts bud.module.resolve(`typescript`, import.meta.url) ``` The change that fixes [#2216](https://togithub.com/roots/bud/issues/2216) has also been applied to `@roots/bud-eslint` and `@roots/bud-babel`. We'll apply it to other packages which use `peerDependencies` in future releases. #### Improvements ##### Include eslint and tailwind configs in build dependencies [#2233 Include tailwind & eslint configs in cached build dependencies](https://togithub.com/roots/bud/pull/2233) adds discovered `tailwind` and `eslint` configs to the map of files the compiler uses to validate the cache. Hopefully changes made to your tailwind config will now be more reliably reflected in your next build without having to use the `--force` flag. Additionally, only modules related to the changed config will be invalidated, which will be much faster than wiping everything. ##### Prevent invoking multiple `esbuild` and/or `esbuild-wasm` modules When transforming configuration modules authored in TypeScript bud.js will now prefer `esbuild` or `esbuild-wasm` as defined by `package.json`, if they are included. The built-in `esbuild-wasm` included in `@roots/bud-support` is used as a fallback. This should be a minor improvement for users who are using `esbuild` in some other way as part of their build. ##### Vendor `bind` decorator from `helpful-decorators`. `helpful-decorators` is an awesome package but we are only using `bind` from it and it is used in a lot of places. This change eliminates the (modest) overhead associated with all the unused modules.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.