microsoft/node-jsonc-parser

Issues

• Allow the visitor to abort or cease recursion

  #30 opened 4 years ago by connor4312
  8

• Support "replace" utility function

  #87 opened 3 months ago by rarkins
  0

• difficulty bundling with esbuild

  #57 opened 3 years ago by pedro-w
  7

• v3.2.1 has a breaking change

  #85 opened 4 months ago by ljharb
  5

• Feature Request: Provide endLine and endColumn for objects, arrays and values

  #86 opened 4 months ago by meisenbarth-work
  0

• Feature request: `modify` and `applyEdits` on parsed AST

  #80 opened 7 months ago by pepijndevos
  0

• formattingOptions: ability to output minified JSON

  #29 opened 5 years ago by iliazeus
  2

• Example?

  #74 opened a year ago by justinmchase
  3

• parseTree - Option to keep comments

  #28 opened 5 years ago by dsherret
  5

• Option to keep spaces before inline comments

  #76 opened a year ago by tiagoefmoraes
  0

• insertSpaces formatting option doesn't always work

  #73 opened a year ago by hessellund
  0

• CLI tool that uses this?

  #22 opened 5 years ago by dashmug
  2

• Unescaped tabs in strings should not be supported

  #63 opened 2 years ago by fabiospampinato
  2

• ncc & v3.1.0

  #68 opened 2 years ago by daiyam
  2

• This repo is missing important files

  #65 opened 2 years ago by microsoft-github-policy-service
  0

• Publish types for setProperty

  #20 opened 5 years ago by sqs
  4

• Feature request: visit() is not useable with modify()

  #48 opened 3 years ago by mcclure
  8

• Feature request: Add JSON path parameter to `JSONVisitor` functions

  #50 opened 2 years ago by Marcono1234
  3

• Clarify whether / how `Edit[]` can be concatenated

  #53 opened 3 years ago by Marcono1234
  3

• Formalize with a specification

  #55 opened 3 years ago
  1

• Enums are not documented

  #49 opened 3 years ago by mcclure
  0

• Non-standard whitespace handling

  #46 opened 3 years ago by ak1394
  0

• Add dev container

  #45 opened 3 years ago by stuartleeks
  1

• getNodePath/modify do not work for property nodes (capture too much content)

  #51 opened 3 years ago by mcclure
  0

• Can we have a "insertFinalNewline" option in "FormattingOptions"?

  #11 opened 4 years ago by nonoroazoro
  0

• Formatting valid json content is causing an invalid json

  #33 opened 4 years ago by sandy081
  0

• parseTree() returns `undefined` on empty string input

  #40 opened 4 years ago by ivanhernandez13
  1

• export mjs for esm

  #36 opened 4 years ago by xiaoxiangmoe
  5

• test issue

  #42 opened 4 years ago by roblourens
  0

• Interference between comment endings and glob's notations

  #41 opened 4 years ago by ahuglajbclajep
  1

• Parse errors make parsed tree useless

  #32 opened 4 years ago by vinnichase
  2

• Upgrading from 2.1.1 to 2.2.0 has diagnostic for file with only comments

  #31 opened 4 years ago by dsherret
  3

• Source map referenced but not included in published package

  #4 opened 5 years ago by TedDriggs
  0

• Support multi line strings

  #26 opened 5 years ago by KoyamaSohei
  3

• Remove Property is not working as expected.

  #10 opened 6 years ago by nonoroazoro
  2

• Format: ability to provide custom property ordering.

  #16 opened 5 years ago by johnspurlock
  3

• How to use this package as webpack loader?

  #19 opened 5 years ago by comerc
  1

• Question: Why are lineNumbers / column not a part of Node?

  #23 opened 5 years ago by helsont
  1

• Error objects should also contain location information

  #1 opened 7 years ago by mrennie
  3

• [question]: `ParseErrorCode` why `const enum`?

  #13 opened 5 years ago by kittaakos
  3

• Please publish new version?

  #14 opened 5 years ago by ecraig12345
  1

• Adding format and edit files breaks imports in TS projects using node module resolution

  #7 opened 6 years ago by TedDriggs
  3

• Convert Location / Segment[] to offsets/range

  #3 opened 7 years ago by TedDriggs
  1

• Remove dependency to `vscode-nls`

  #2 opened 7 years ago by jtheoof
  2