chore(deps): update devdependency unbuild to v0.9.4 - autoclosed

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
unbuild	0.7.2 -> 0.9.4

---

Release Notes

unjs/unbuild (unbuild)

v0.9.4

Compare Source

v0.9.3

Compare Source

v0.9.2

Compare Source

v0.9.1

Compare Source

v0.9.0

Compare Source

v0.8.11

Compare Source

v0.8.10

Compare Source

v0.8.9

Compare Source

v0.8.8

Compare Source

v0.8.7

Compare Source

v0.8.6

Compare Source

v0.8.5

Compare Source

v0.8.4

Compare Source

v0.8.3

Compare Source

v0.8.2

Compare Source

v0.8.1

Compare Source

v0.8.0

Compare Source

⚠ BREAKING CHANGES

• always enable esmResolve for jiti (stub and config)
• exit with code (1) on build warnings (#​98)

Features

• always enable esmResolve for jiti (stub and config) (b87c8df)
• exit with code (1) on build warnings (#​98) (ffc0d7c)
• rollup: generated named exports in esm stub (c9fce24)

0.7.6 (2022-07-20)

Bug Fixes

• pkg: use default export condition to avoid breaking change (858d35d), closes #​89

0.7.5 (2022-07-20)

Features

• enable esmResolve when loading build.config (#​93) (c856812)

Bug Fixes

• pkg: add types field for exports (#​89) (457f043)
• properly calculate bytes of output size (#​82) (1888978)

0.7.4 (2022-04-13)

Bug Fixes

• deps: update mlly (c935845)

0.7.3 (2022-04-12)

Bug Fixes

• resolve asbolute path to jiti for pnpm support (#​58) (81d6da7)
• stub: use file:// protocol for windows compatibility (12a99c1)
• work around issue building with pnpm (#​57) (eb7da84)

0.7.2 (2022-03-25)

Bug Fixes

• revert builtins from default externals (0b808c6)

0.7.1 (2022-03-25)

Bug Fixes

• add builtins and node: prefixes to externals (2af233d)

v0.7.6

Compare Source

v0.7.5

Compare Source

v0.7.4

Compare Source

v0.7.3

Compare Source

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - "before 4am on Monday" (UTC).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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.

[socket-security]

👍 Dependency issues cleared. Learn more about Socket for GitHub ↗︎

This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored.

View full report↗︎

[socket-security]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/[email protected]	Transitive: environment, filesystem, network, shell, unsafe	+147	112 MB	pi0

🚮 Removed packages: npm/[email protected])

View full report↗︎

[coderabbitai]

Warning

Rate limit exceeded

@renovate[bot] has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 11 minutes and 39 seconds before requesting another review.

How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

Commits

Files that changed from the base of the PR and between 5b7b92b and 5711077.

Walkthrough

The change involves an update to the version of the "unbuild" package in the package.json file, moving from version "0.7.2" to "0.9.4". This indicates an upgrade to a more recent version, potentially introducing new features, bug fixes, or performance enhancements.

Changes

File	Change Summary
package.json	Updated "unbuild" version from "0.7.2" to "0.9.4"

Sequence Diagram(s)

(No sequence diagrams generated as the changes are too simple to warrant a visual representation.)

Poem

🐇 In the garden where the daisies sway,
A new version hops in, hip-hip-hooray!
With "unbuild" now spry, it's time to play,
Bugs and fixes, come out and stay!
So let's leap and bound, with joy we convey,
A bright new path on this fine day! 🌼

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between a3f56f6 and 5b7b92b.

Files ignored due to path filters (1)

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

Files selected for processing (1)

• package.json (1 hunks)

Additional comments not posted (1)

package.json (1)

83-83: LGTM! But verify the impact of the new version.

The update to the "unbuild" package version is approved. However, ensure that the new version does not introduce any breaking changes or issues.

The code changes are approved.

Run the following script to verify the impact of the new version: