Skip to content

[Snyk] Upgrade jsonc-parser from 3.2.0 to 3.3.1#6

Open
mysommer wants to merge 1 commit intomainfrom
snyk-upgrade-d37107d4efa95912b4556800c5690a04
Open

[Snyk] Upgrade jsonc-parser from 3.2.0 to 3.3.1#6
mysommer wants to merge 1 commit intomainfrom
snyk-upgrade-d37107d4efa95912b4556800c5690a04

Conversation

@mysommer
Copy link
Member

@mysommer mysommer commented Sep 1, 2025

snyk-top-banner

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 a year 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:

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

See this package in npm:
jsonc-parser

See this project in Snyk:
https://app.snyk.io/org/bysnet/project/68adff7a-a2da-4379-a52b-9b765b2b972d?utm_source=github&utm_medium=referral&page=upgrade-pr
@vercel
Copy link

vercel bot commented Sep 1, 2025

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

Project Deployment Preview Comments Updated (UTC)
vscode Ready Ready Preview Comment Sep 1, 2025 2:38am

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Summary of Changes

Hello @bysnet, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request focuses on maintaining the project's dependency health by automatically updating the jsonc-parser library. The upgrade ensures the integration of the latest features, bug fixes, and potential security enhancements from the updated package, contributing to the overall stability and reduced technical debt of the project.

Highlights

  • Dependency Upgrade: Upgraded the jsonc-parser dependency from version 3.2.0 to 3.3.1. This is an automated update initiated by Snyk to keep project dependencies current.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in issue comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request from Snyk upgrades the jsonc-parser dependency from 3.2.0 to 3.3.1. The changes are correctly applied to package.json and package-lock.json for the vscode-colorize-perf-tests extension. This is a minor version update, which is good practice for maintenance and security, and it should not introduce any breaking changes. The changes are consistent and look good to merge.

@bito-code-review
Copy link

Bito Automatic Review Skipped - Files Excluded

Bito didn't auto-review this change because all changed files are in the exclusion list for automatic reviews. No action is needed if you didn't intend for the agent to review it. Otherwise, to manually trigger a review, type /review in a comment and save.
You can change the excluded files settings here, or contact your Bito workspace admin at i@michaelsommer.dev.

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.

2 participants