Skip to content

fix(deps): update dependency jiti to v2.6.1#3398

Open
renovate[bot] wants to merge 1 commit intocanaryfrom
renovate/jiti-2.x
Open

fix(deps): update dependency jiti to v2.6.1#3398
renovate[bot] wants to merge 1 commit intocanaryfrom
renovate/jiti-2.x

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate bot commented Apr 18, 2026

This PR contains the following updates:

Package Change Age Confidence
jiti 2.4.22.6.1 age confidence

Release Notes

unjs/jiti (jiti)

v2.6.1

Compare Source

compare changes

🩹 Fixes
  • interop: Only passthrough default if it is not a promise (#​408)
📦 Build
  • Revert to terser-webpack-plugin (#​407)
🏡 Chore
❤️ Contributors

v2.6.0

Compare Source

compare changes

🔥 Performance
  • Lazy load babel transform (#​405)
🩹 Fixes
  • cjs-interop: Handle function default exports (#​396)
  • Always use native for node: specifiers (#​392)
📦 Build
🏡 Chore
✅ Tests
  • Update deno and bun native test ignores (df844f8)
  • New bench script (6404427)
❤️ Contributors
  • Pooya Parsa (@​pi0)
  • Volodymyr Kolesnykov (@​sjinks)
  • Jungwoo LEE <jungwoo3490@​naver.com>

v2.5.1

Compare Source

compare changes

🩹 Fixes
  • interop: Passthrough module if it is a promise (#​389)
❤️ Contributors

v2.5.0

Compare Source

compare changes

🚀 Enhancements
  • Use sha256 for cache entries in fips mode (#​375)
  • rebuildFsCache ( JITI_REBUILD_FS_CACHE) (#​379)
🩹 Fixes
  • Interop modules with nil default export (#​377)
  • register: Handle require(<json>) (#​374)
🏡 Chore
✅ Tests
  • Update snapshot (c7cfeed)
  • Only include src for coverage report (#​372)
❤️ Contributors

Configuration

📅 Schedule: (UTC)

  • 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: Never, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.


Summary by cubic

Upgrade jiti to v2.6.1 in packages/react-email to improve performance and fix ESM/CJS interop issues. This update reduces Babel transform overhead and adds FIPS-safe cache hashing.

  • Dependencies
    • Bump jiti from 2.4.2 to 2.6.1; updated pnpm-lock.yaml.
    • Includes lazy Babel loading, native handling for node: specifiers, and safer cache keys.

Written for commit fdff1d7. Summary will update on new commits.

@vercel
Copy link
Copy Markdown
Contributor

vercel bot commented Apr 18, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
react-email Ready Ready Preview, Comment Apr 18, 2026 3:07am
react-email-demo Ready Ready Preview, Comment Apr 18, 2026 3:07am

Request Review

@changeset-bot
Copy link
Copy Markdown

changeset-bot bot commented Apr 18, 2026

⚠️ No Changeset found

Latest commit: fdff1d7

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@pkg-pr-new
Copy link
Copy Markdown

pkg-pr-new bot commented Apr 18, 2026

Open in StackBlitz

npm i https://pkg.pr.new/react-email@3398

commit: fdff1d7

Copy link
Copy Markdown
Contributor

@cubic-dev-ai cubic-dev-ai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No issues found across 2 files

Confidence score: 5/5

  • Automated review surfaced no issues in the provided summaries.
  • No files require special attention.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants