Update jiti 2.6.1 → 2.7.0 (minor)

[depfu]

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.1 → 2.7.0) · Repo · Changelog

Release Notes

2.7.0

compare changes

🚀 Enhancements

• Add explicit resource management (using/await using) support (#422)
• Support opt-in tsconfigPaths (#427)
• Support virtual modules (#428)
• Add jiti/static subpath (#430)

🔥 Performance

• interopDefault: Add caching to reduce proxy overhead by ~2x (#421)

🩹 Fixes

• require: Passthrough resolve options (#412)
• require: Fallback to transpilation when tryNative fails (#413)
• Fallback for ENAMETOOLONG when evaluating esm (#429)

📦 Build

• Upgrade rspack to v2 (55194fb)
• Experimental rolldown config (8c0243f)

✅ Tests

• Ignore jsx test for bun/cjs (3a744ca)

❤️ Contributors

• Pooya Parsa (@pi0)
• Kricsleo (@kricsleo)
• Espen Hovlandsdal (@rexxars)
• Rintaro Itokawa (@re-taro)
• Matteo Collina (@mcollina)
• Mario Zechner (@badlogic)

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 29 commits:

• chore(release): v2.7.0
• chore: update release script
• fix: fallback for `ENAMETOOLONG` when evaluating esm (#429)
• build: experimental rolldown config
• build: upgrade rspack
• ci: update node test matrix
• chore: update tsconfig
• chore: update deps
• feat: add `jiti/static` export (#430)
• feat: support virtual modules option (#428)
• fix(require): fallback to transpilation when `tryNative` fails (#413)
• chore: update agents.md
• lint
• feat: support opt-in `tsconfigPaths` (#427)
• chore: init agents.md
• feat: add explicit resource management (using/await using) support (#422)
• perf(interopDefault): add caching to reduce proxy overhead by ~2x (#421)
• fix(ci): skip `--coverage` flag for node 18
• chore: lint
• chore: add missing prettier dep
• chore(deps): update autofix-ci/action digest to 7a166d7 (#424)
• chore(deps): update actions/checkout action to v6 (#419)
• chore: update deps
• test: update
• test: ignore jsx test for bun/cjs
• chore: update deps
• chore: fix lint issues
• chore(deps): update actions/setup-node action to v6 (#411)
• fix(require): passthrough resolve options (#412)

---

Depfu 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.

All Depfu comment commands

@​depfu rebase

Rebases against your default branch and redoes this update

@​depfu recreate

Recreates this PR, overwriting any edits that you've made to it

@​depfu merge

Merges this PR once your tests are passing and conflicts are resolved

@​depfu cancel merge

Cancels automatic merging of this PR

@​depfu close

Closes this PR and deletes the branch

@​depfu reopen

Restores the branch and reopens this PR (if it's closed)

@​depfu pause

Ignores all future updates for this dependency and closes this PR

@​depfu pause [minor|major]

Ignores all future minor/major updates for this dependency and closes this PR

@​depfu resume

Future versions of this dependency will create PRs again (leaves this PR as is)

[greptile-apps]

Confidence Score: 5/5

Safe to merge — purely a lockfile and version-specifier update with no logic changes.

The only changes are the jiti version strings in two package.json files and the regenerated pnpm-lock.yaml. The upstream release is a minor bump with additive features and targeted bug fixes; no breaking changes are noted. There is nothing in the diff that could introduce a regression in Tailwind's own code.

No files require special attention.

_{Reviews (1): Last reviewed commit: "Update jiti to version 2.7.0" | Re-trigger Greptile}

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: f1b138d2-730c-415b-80ff-3caccc9bbb0a

📥 Commits

Reviewing files that changed from the base of the PR and between 5752161 and 0733ebc.

⛔ Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (2)

• packages/@tailwindcss-node/package.json
• packages/@tailwindcss-upgrade/package.json

---

Walkthrough

This PR updates the jiti dependency from version ^2.6.1 to ^2.7.0 in two packages: @tailwindcss-node and @tailwindcss-upgrade. Both changes are straightforward dependency version bumps in their respective package.json files with no modifications to package exports, APIs, or runtime logic.

🚥 Pre-merge checks | ✅ 3 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Linked Issues check	⚠️ Warning	The linked issue #424 requests adding a dark theme to tailwindcss.com documentation, which is completely unrelated to updating the jiti dependency in package.json files.	Verify the correct issue is linked to this PR. This PR updates a dependency and should not be linked to a documentation dark theme feature request.

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely describes the main change: updating the jiti dependency from version 2.6.1 to 2.7.0.
Description check	✅ Passed	The description is directly related to the changeset, providing detailed release notes, changelog, and commit information for the jiti 2.7.0 update.
Out of Scope Changes check	✅ Passed	The PR changes are limited to updating the jiti dependency version in two package.json files, which aligns with the PR title and description. No out-of-scope changes detected.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[depfu]

Sorry, but the merge failed with:

At least 1 approving review is required by reviewers with write access.