sindresorhus/serialize-error

Issues

• Optionally preserve current stack

  #98 opened 2 months ago by fregante
  4

• Wrong typescript declaration for errorConstructors

  #78 opened 2 years ago
  7

• `cause` prop is not being serialized

  #90 opened a year ago by razbensimon
  4

• v9+ throws ERR_REQUIRE_ESM when imported

  #95 opened 10 months ago by jmechevarria
  1

• Error require of ES Module not supported

  #82 opened 2 years ago by MickL
  21

• Jest encounters `SyntaxError: Cannot use import statement outside a module` while trying to test code that uses `serialize-error`

  #80 opened 2 years ago by barshopen
  8

• Remove direct usage of Buffer

  #93 opened a year ago by VictorPuga
  0

• Feature request: handle AggregateErrors

  #91 opened a year ago by sandinmyjoints
  0

• ESBuild error when importing serialize-error

  #89 opened a year ago by casertap
  1

• ERR_REQUIRE_ESM

  #88 opened a year ago by jeremythille
  1

• Received error object is not extensible when calling serialize error

  #87 opened a year ago by Raynos
  0

• `option` to treat undefined as null

  #86 opened a year ago by bombillazo
  1

• Keep old versions of the lib on a separate branch

  #85 opened 2 years ago by belchior
  1

• Enumerable properties are made non-enumerable

  #84 opened 2 years ago by MikeJerred
  0

• Visibility of undefined values in the objects

  #83 opened 2 years ago by dawidk92
  0

• Error [ERR_REQUIRE_ESM]: require() of ES

  #58 opened 3 years ago by vrecan
  11

• Error subclasses are lost when deserializing

  #48 opened 3 years ago by fregante
  7

• If string is passed as unknown, the value returned from serializeError is badly typed as ErrorObject

  #81 opened 2 years ago by PabloSzx
  1

• Wrong typescript definition for serializeError

  #79 opened 2 years ago
  4

• Handle custom error constructors with incompatible signatures

  #72 opened 3 years ago by fregante
  0

• `deserializeError` serializes/destroys properties unnecessarily

  #76 opened 3 years ago by fregante
  1

• Nested errors are still not serialized

  #74 opened 3 years ago by fregante
  0

• Unknown object type "asyncfunction"

  #75 opened 3 years ago by walshe
  3

• Nested Error's are not deserialized

  #46 opened 3 years ago by jessetabak
  2

• Optionally ignore `toJSON`

  #66 opened 3 years ago by fregante
  2

• Add `isErrorObject` type guard / function

  #47 opened 3 years ago by fregante
  5

• `toJSON` example is confusing

  #67 opened 3 years ago by fregante
  0

• Add support for (or document) Error#cause

  #50 opened 3 years ago by fregante
  4

• The output is not JSON.stringify-safe

  #55 opened 3 years ago by tjconcept
  6

• Jest encountered an unexpected token

  #64 opened 3 years ago by kkorus
  1

• Version 9.1.1 with CRA default Babel config gives "Module parse failed"

  #63 opened 3 years ago by gianpaolopascasidc
  1

• Error: Cannot read property 'pipe' of null

  #59 opened 3 years ago by rj-david
  0

• AWS SDK v3 exposes Readable in Error object

  #56 opened 3 years ago by wodka
  0

• CommonJS

  #53 opened 3 years ago by hansnull
  1

• Can type-fest be moved to devDependencies?

  #51 opened 3 years ago by EricCrosson
  4

• Use stricter type for JsonObject

  #52 opened 3 years ago by gajus
  2

• Consider making common error properties non enumerable

  #29 opened 5 years ago by Weakky
  1

• Merge stack traces

  #49 opened 3 years ago by fregante
  5

• Feat: Add a option to indicate how deep to scan Error object

  #16 opened 4 years ago by OsoianMarcel
  3

• In-browser use error: ReferenceError: Buffer is not defined

  #41 opened 4 years ago by vladimiry
  1

• Consider Object.toJSON() method

  #20 opened 4 years ago by samchon
  3

• `serializeError` converts a `Date` object into an empty plain object

  #34 opened 4 years ago by jbhoot
  0

• OutOfMemory exception on errors containing Buffers

  #37 opened 4 years ago by cyrilgandon
  4

• Dual package with native ES Modules output

  #36 opened 4 years ago by dandv
  1

• Type definitions not being imported

  #33 opened 4 years ago by farah
  0

• v7 doesn't work as described

  #31 opened 5 years ago by goloroden
  3

• Add option to decide behavior

  #25 opened 5 years ago by sindresorhus
  5

• change in v5: `const {inspect} = require('util');` can lead to web bundle bloat

  #26 opened 5 years ago by dylang
  7

• Bug: Does not work correctly with Node 6

  #17 opened 6 years ago by kibertoad
  1

• Export transpiled JS rather than ES6

  #13 opened 6 years ago by vaclav-zeman
  1