depfu[bot] a6a7e4cbaf Update jiti 2.6.0 → 2.6.1 (patch) (#19160) ... Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request. ### What changed? #### ✳️ jiti (2.6.0 → 2.6.1) · [Repo](https://github.com/unjs/jiti) · [Changelog](https://github.com/unjs/jiti/blob/main/CHANGELOG.md) <details> <summary>Release Notes</summary> <h4><a href="https://github.com/unjs/jiti/releases/tag/v2.6.1">2.6.1</a></h4> <blockquote><p dir="auto"><a href="https://bounce.depfu.com/github.com/unjs/jiti/compare/v2.6.0...v2.6.1">compare changes</a></p> <h3 dir="auto">🩹 Fixes</h3> <ul dir="auto"> <li> <strong>interop:</strong> Only passthrough default if it is not a promise (<a href="https://bounce.depfu.com/github.com/unjs/jiti/pull/408">#408</a>)</li> </ul> <h3 dir="auto">📦 Build</h3> <ul dir="auto"> <li>Revert to <code class="notranslate">terser-webpack-plugin</code> (<a href="https://bounce.depfu.com/github.com/unjs/jiti/pull/407">#407</a>)</li> </ul> <h3 dir="auto">❤️ Contributors</h3> <ul dir="auto"> <li>Kricsleo (<a href="https://bounce.depfu.com/github.com/kricsleo">@kricsleo</a>)</li> </ul></blockquote> <p><em>Does any of this look wrong? <a href="feedback">Please let us know.</a></em></p> </details> <details> <summary>Commits</summary> <p><a href="82919cff8b...aedcdee7fe">See the full diff on Github</a>. The new version differs by 6 commits:</p> <ul> <li><a href="aedcdee7fe"><code>chore(release): v2.6.1</code></a></li> <li><a href="8b41497481"><code>chore: remove unused code</code></a></li> <li><a href="974ca4008a"><code>chore: update deps</code></a></li> <li><a href="e840692427"><code>build: revert to `terser-webpack-plugin` (#407)</code></a></li> <li><a href="092cdd9952"><code>fix(interop): only passthrough default if it is not a promise (#408)</code></a></li> <li><a href="037c646c80"><code>chore: update bench</code></a></li> </ul> </details> ---  [Depfu](https://depfu.com) will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with `@depfu rebase`. <details><summary>All Depfu comment commands</summary> <blockquote><dl> <dt>@​depfu rebase</dt><dd>Rebases against your default branch and redoes this update</dd> <dt>@​depfu recreate</dt><dd>Recreates this PR, overwriting any edits that you've made to it</dd> <dt>@​depfu merge</dt><dd>Merges this PR once your tests are passing and conflicts are resolved</dd> <dt>@​depfu cancel merge</dt><dd>Cancels automatic merging of this PR</dd> <dt>@​depfu close</dt><dd>Closes this PR and deletes the branch</dd> <dt>@​depfu reopen</dt><dd>Restores the branch and reopens this PR (if it's closed)</dd> <dt>@​depfu pause</dt><dd>Ignores all future updates for this dependency and closes this PR</dd> <dt>@​depfu pause [minor|major]</dt><dd>Ignores all future minor/major updates for this dependency and closes this PR</dd> <dt>@​depfu resume</dt><dd>Future versions of this dependency will create PRs again (leaves this PR as is)</dd> </dl></blockquote> </details> Co-authored-by: depfu[bot] <23717796+depfu[bot]@users.noreply.github.com>		2025-10-20 14:59:11 +02:00
..
@tailwindcss-browser	Release 4.1.15 (#19159)	2025-10-20 14:48:42 +02:00
@tailwindcss-cli	Release 4.1.15 (#19159)	2025-10-20 14:48:42 +02:00
@tailwindcss-node	Update jiti 2.6.0 → 2.6.1 (patch) (#19160)	2025-10-20 14:59:11 +02:00
@tailwindcss-postcss	Release 4.1.15 (#19159)	2025-10-20 14:48:42 +02:00
@tailwindcss-standalone	Release 4.1.15 (#19159)	2025-10-20 14:48:42 +02:00
@tailwindcss-upgrade	Release 4.1.15 (#19159)	2025-10-20 14:48:42 +02:00
@tailwindcss-vite	Release 4.1.15 (#19159)	2025-10-20 14:48:42 +02:00
internal-example-plugin	Prefix internal modules with internal-* (#14074)	2024-07-29 10:58:07 -04:00
tailwindcss	Release 4.1.15 (#19159)	2025-10-20 14:48:42 +02:00
tsconfig.base.json	Improve debug logs (#15303)	2024-12-11 15:27:20 +01:00