# jsonc-parser changelog > Scanner and parser for JSON with comments, as VS Code uses. - Vendor: Microsoft - Category: Frameworks & Libraries - Official site: https://github.com/microsoft/node-jsonc-parser - Tracked by: What's New (https://whatsnew.fyi/product/jsonc-parser) - Harvested from: GitHub (microsoft/node-jsonc-parser) - Entries below: 4 (newest first) What's New is an index, not a publisher: every entry below links to the vendor's own release notes, which are the authoritative source. Entries are labelled where they are hand-curated sample data, pre-releases, or drawn from a secondary source such as a developer blog. Reuse: the summaries, labels and curation here are © What's New. Quote freely with attribution and a link back; wholesale republication of the corpus is not permitted — terms: https://whatsnew.fyi/terms. The vendors' own release notes remain their publishers'. ## Releases ### v4.0.0-next.2 - Date: 2026-06-16 - Version: v4.0.0-next.2 - Original notes: https://github.com/microsoft/node-jsonc-parser/releases/tag/v4.0.0-next.2 - Permalink: https://whatsnew.fyi/product/jsonc-parser/releases/v4.0.0-next.2 - Labels: Pre-release - **fixed** — Fix off-by-one error in modify() when removing last array element - **fixed** — modify() produces invalid JSON when removing array elements - **changed** — Upgrade brace-expansion to latest versions - **changed** — Update brace-expansion dependency - **changed** — Bump picomatch from 2.3.1 to 2.3.2 - **changed** — Bump flatted from 3.3.3 to 3.4.2 ##### Changes: * #124: npm audit fix + bump to 4.0.0-next.2 * #122: chore: upgrade brace-expansion to latest versions * #120: Fix off-by-one error in `modify()` when removing last array element * #108: modify() produces invalid JSON when removing array elements * #119: fix: npm audit fix - update brace-expansion dependency * #118: Bump picomatch from 2.3.1 to 2.3.2 * #117: Bump flatted from 3.3.3 to 3.4.2 This list of changes was [auto generated](https://dev.azure.com/monacotools/Monaco/_build/results?buildId=448332&view=logs). ### v4.0.0-next.1 - Date: 2026-03-10 - Version: v4.0.0-next.1 - Original notes: https://github.com/microsoft/node-jsonc-parser/releases/tag/v4.0.0-next.1 - Permalink: https://whatsnew.fyi/product/jsonc-parser/releases/v4.0.0-next.1 - Labels: Pre-release - **fixed** — Fix off-by-one error in modify() when removing last array element - **fixed** — Fix modify() producing invalid JSON when removing array elements - **changed** — Upgrade brace-expansion to latest versions - **changed** — Update brace-expansion dependency - **changed** — Bump picomatch from 2.3.1 to 2.3.2 - **changed** — Bump flatted from 3.3.3 to 3.4.2 ##### Changes: * #122: chore: upgrade brace-expansion to latest versions * #120: Fix off-by-one error in `modify()` when removing last array element * #108: modify() produces invalid JSON when removing array elements * #119: fix: npm audit fix - update brace-expansion dependency * #118: Bump picomatch from 2.3.1 to 2.3.2 * #117: Bump flatted from 3.3.3 to 3.4.2 This list of changes was [auto generated](https://dev.azure.com/monacotools/Monaco/_build/results?buildId=446876&view=logs). ### v3.3.1 - Date: 2024-06-24 - Version: v3.3.1 - Original notes: https://github.com/microsoft/node-jsonc-parser/releases/tag/v3.3.1 - Permalink: https://whatsnew.fyi/product/jsonc-parser/releases/v3.3.1 - **removed** — remove exports ##### Changes: * #92: remove exports, prepare 3.3.1 This list of changes was [auto generated](https://dev.azure.com/monacotools/Monaco/_build/results?buildId=280483&view=logs). ### v3.3.0 - Date: 2024-06-24 - Version: v3.3.0 - Original notes: https://github.com/microsoft/node-jsonc-parser/releases/tag/v3.3.0 - Permalink: https://whatsnew.fyi/product/jsonc-parser/releases/v3.3.0 - **added** — Add insertFinalNewline option in FormattingOptions - **added** — Include source map in published package - **fixed** — Formatting valid JSON content no longer produces invalid JSON - **fixed** — parseTree() now returns correct value on empty string input - **added** — Allow the visitor to cease callbacks ##### 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](https://dev.azure.com/monacotools/Monaco/_build/results?buildId=280373&view=logs).