chore(deps): update dependency browserify to v17
This PR contains the following updates:
| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
| browserify | 16.5.2 -> 17.0.1 |
Release Notes
browserify/browserify (browserify)
v17.0.1
- Use
hasowninstead ofhas. (4b1a5dc) - Use
String.prototype.sliceinstead ofString.prototype.substr. (#2036) - Support relative paths in the
noParseoption. (#2080)
v17.0.0
- Upgrade events to v3.x. EventEmitter instances now have an
off()method.require('events').oncecan be used to react to an event being emitted withasync/awaitsyntax. (#1839) - Upgrade path-browserify to v1.x. (#1838)
- Upgrade stream-browserify to v3.x.
require('stream')now matches the Node.js 10+ API. (#1970) - Upgrade util to v0.12. Most notably,
util.promisifyandutil.callbackifyare finally available by default in browserify. (#1844) - Add JSON syntax checking. Syntax errors in
.jsonfiles will now fail to bundle. (#1700)
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 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.
:warning: We detected 13 security issues in this pull request:
Vulnerable Libraries (13)
| Severity | Details |
|---|---|
| High | [email protected] (t) upgrade to: >1.0.0-rc.12 |
| High | [email protected] (t) upgrade to: >=3.0.1 |
| Critical | @babel/[email protected] (t) upgrade to: >=7.23.2 |
| Medium | [email protected] (t) upgrade to: >=3.1.10 |
| High | [email protected] (t) upgrade to: >4.19.2 || >5.0.0-beta.3 |
| Medium | [email protected] (t) upgrade to: >=4.0.8 |
| High | [email protected] (t) upgrade to: >=2.79.2 |
| High | [email protected] (t) upgrade to: >5.7.1 || >6.3.0 || >7.5.1 |
| Medium | [email protected] (t) upgrade to: >1.16.0 |
| Medium | [email protected] (t) upgrade to: >=4.1.3 |
| Medium | [email protected] (t) upgrade to: >5.93.0 |
| High | [email protected] (t) upgrade to: >5.3.3 |
| Medium | [email protected] (t) upgrade to: >=1.2.4 |
More info on how to fix Vulnerable Libraries in JavaScript.
👉 Go to the dashboard for detailed results.
📥 Happy? Share your feedback with us.
[!IMPORTANT]
Review skipped
Bot user detected.
To trigger a single review, invoke the
@coderabbitai reviewcommand.You can disable this status message by setting the
reviews.review_statustofalsein the CodeRabbit configuration file.
🪧 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>, please review it. -
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
@coderabbitaiin 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
@coderabbitaiin 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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase. -
@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 pauseto pause the reviews on a PR. -
@coderabbitai resumeto resume the paused reviews. -
@coderabbitai reviewto trigger an incremental review. This is useful when automatic reviews are disabled for the repository. -
@coderabbitai full reviewto do a full review from scratch and review all the files again. -
@coderabbitai summaryto regenerate the summary of the PR. -
@coderabbitai resolveresolve all the CodeRabbit review comments. -
@coderabbitai configurationto show the current CodeRabbit configuration for the repository. -
@coderabbitai helpto get help.
Other keywords and placeholders
- Add
@coderabbitai ignoreanywhere in the PR description to prevent this PR from being reviewed. - Add
@coderabbitai summaryto generate the high-level summary at a specific location in the PR description. - Add
@coderabbitaianywhere in the PR title to generate the title automatically.
CodeRabbit Configuration File (.coderabbit.yaml)
- You can programmatically configure CodeRabbit by adding a
.coderabbit.yamlfile 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.