moll/json-stringify-safe

Issues

• Array replacer raises an error

  #14 opened 10 years ago by gergoerdosi
  2

• RangeError: Invalid string length

  #38 opened 8 months ago by wparad
  5

• No lock file found in the jsonstringifysafe project on Tag: v5.0.1

  #36 opened 4 years ago by mahirkabir
  1

• I get a syntax error

  #34 opened 4 years ago by arthurmelton
  3

• RangeError: Maximum call stack size exceeded

  #8 opened 12 years ago by benbuckman
  9

• BigInt serialisation

  #33 opened 5 years ago by shashikantj
  1

• feature request: deserialize

  #32 opened 6 years ago by oprogramador
  3

• Typescript support

  #27 opened 7 years ago by SimonSchick
  4

• error during npm i

  #29 opened 7 years ago by ralyodio
  2

• Typo in package description

  #28 opened 7 years ago by alexpls
  2

• can cause unexpected behaviour in the presence of __defineGetter__

  #24 opened 8 years ago by richmarr
  5

• Missing semicolon breaks JS obfuscation

  #25 opened 8 years ago by danielmohacsi
  4

• Allow to pass object to fromJSON

  #22 opened 9 years ago by gajus
  1

• Very deep objects take a long time to stringify, maybe add a `depth` option ?

  #16 opened 9 years ago by netei
  0

• false positive for sibling (not-circular) references

  #9 opened 10 years ago by proppy
  5

• release new version

  #13 opened 10 years ago by Raynos
  2

• .indexOf() is undefined in IE8

  #6 opened 11 years ago by ericelliott
  4

• Stringify on XMLHttpRequest

  #10 opened 11 years ago by shortstuffsushi
  2

• bower.json

  #11 opened 11 years ago by Toilal
  1

• Slow when processing arrays

  #4 opened 12 years ago by geek
  3

• Isaacs, you rock. <eom>

  #5 opened 12 years ago by ericelliott
  0

• Siblings are incorrectly considered circular

  #2 opened 12 years ago by jdalton
  10

• comparison is not good enough

  #3 opened 12 years ago by mikeal
  1