[Snyk] Upgrade jsonc-parser from 3.2.0 to 3.3.1

[HaLaGu1L]

Snyk has created this PR to upgrade jsonc-parser from 3.2.0 to 3.3.1.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

---

• The recommended version is 3 versions ahead of your current version.

• The recommended version was released on 4 months ago.

Release notes

Package name: jsonc-parser

• 3.3.1 - 2024-06-24
  

  Changes:

  • #92: remove exports, prepare 3.3.1

  This list of changes was auto generated.

• 3.3.0 - 2024-06-24
  

  Changes:

  Feature Requests:

  • #11: Can we have a "insertFinalNewline" option in "FormattingOptions"?
  • #4: Source map referenced but not included in published package

  Bugs:

  • #33: Formatting valid json content is causing an invalid json
  • #40: parseTree() returns undefined on empty string input

  Others:

  • #90: prepare 3.3.0
  • #88: Allow the visitor to cease callbacks
  • #89: Bump braces from 3.0.2 to 3.0.3
  See More

  • #84: prepare 3.2.1
  • #81: perf(format): cache breaklines and spaces as much as possible
  • #79: update dependencies
  • #75: ci: add batch
  • #72: delete pr-chat action
  • #71: add publish pipeline & cleanup ci
  • #70: set preserveConstEnums: true, switch to es2020
  • #69: sort edits in applyEdits
  • #66: An additional parameter keepLines has been added into the formatting options which allows to keep the original line formatting
  • #64: Adding Microsoft SECURITY.MD
  • #62: Add JSON path supplier parameter to visitor functions
  • #44: findNodeAtLocation does not handle incomplete property pair
  • #61: Update API section in README
  • #53: Clarify whether / how Edit[] can be concatenated
  • #46: Non-standard whitespace handling
  • #47: Improve README
  • #54: readme: improve ParseOptions documentation
  • #43: Add file extenstion to typings property value
  • #34: Optimize parseLiteral for number-heavy JSON files (ala GeoJSON)
  • #39: Bump lodash from 4.17.15 to 4.17.19
  • #35: Allow for array modifications, add inPlace formatting option.
  • #32: Parse errors make parsed tree useless
  • #31: Upgrading from 2.1.1 to 2.2.0 has diagnostic for file with only comments
  • #25: Fix typo in README
  • #24: parse function should include properties with empty string as their keys
  • #21: Update README.md
  • #18: JavaScipt -> JavaScript
  • #17: add line and column information to scanner and visitor
  • #15: Fix a few typos in doc comments
  • #12: Do not mutate the given path
  • #9: Refactor computeIndentLevel method
  • #8: Fix typo of token
  • #6: Allow trailing commas in array
  • #5: add JSON formatter and editor from VS Code
  • #1: Error objects should also contain location information

  This list of changes was auto generated.

• 3.2.1 - 2024-01-22
  

  prepare 3.2.1 (#84)

• 3.2.0 - 2022-08-30
  

  set preserveConstEnums: true, switch to es2020 (#70)

from jsonc-parser GitHub release notes

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• This PR was automatically created by Snyk using the credentials of a real user.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

• 🧐 View latest project report
• 📜 Customise PR templates
• 🛠 Adjust upgrade PR settings
• 🔕 Ignore this dependency or unsubscribe from future upgrade PRs

[coderabbitai]

Important

Review skipped

Ignore keyword(s) in the title.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

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>, 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 @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 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 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.