- Notifications
You must be signed in to change notification settings - Fork4
[Snyk] Upgrade jsonc-parser from 3.2.1 to 3.3.1#100
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Open
ghaschel wants to merge1 commit intomasterChoose a base branch
base:master
Could not load branches
Branch not found:{{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline, and old review comments may become outdated.
Uh oh!
There was an error while loading.Please reload this page.
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.Learn more about bidirectional Unicode characters
Snyk has created this PR to upgrade jsonc-parser from 3.2.1 to 3.3.1.See this package in npm:jsonc-parserSee this project in Snyk:https://app.snyk.io/org/ghaschel/project/ffbf9dc1-0653-4746-8f94-125508a27176?utm_source=github&utm_medium=referral&page=upgrade-pr
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Labels
None yet
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR was automatically created by Snyk using the credentials of a real user.
Snyk has created this PR to upgrade jsonc-parser from 3.2.1 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 is2 versions ahead of your current version.
The recommended version was released on22 days ago.
Release notes
Package name:jsonc-parser
- 3.3.1 -2024-06-24
- #92: remove exports, prepare 3.3.1
- 3.3.0 -2024-06-24
- #11: Can we have a "insertFinalNewline" option in "FormattingOptions"?
- #4: Source map referenced but not included in published package
- #33: Formatting valid json content is causing an invalid json
- #40: parseTree() returns
- #90: prepare 3.3.0
- #88: Allow the visitor to cease callbacks
- #89: Bump braces from 3.0.2 to 3.0.3
- #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
- #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
- #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
- 3.2.1 -2024-01-22
fromjsonc-parser GitHub release notesChanges:
This list of changes wasauto generated.
Changes:
Feature Requests:
Bugs:
undefinedon empty string inputOthers:
See More
preserveConstEnums: true, switch to es2020Edit[]can be concatenatedThis list of changes wasauto generated.
prepare 3.2.1 (#84)
Important
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: