Skip to content

Releases: inrupt/solid-client-errors-js

v0.0.4

Choose a tag to compare

@NSeydoux NSeydoux released this 16 Jun 15:53
de4e68d

Breaking Changes

  • Support for Node.js v20.x has been dropped as that version has reached end-of-life.

Patch changes

  • Transitive dependencies update

Full Changelog: v0.0.3...v0.0.4

v0.0.3

Choose a tag to compare

@NSeydoux NSeydoux released this 30 Oct 08:48
afb3890

Breaking Changes

  • Support for Node.js v18.x has been dropped as that version has reached end-of-life.

Patch changes

  • Dev dependencies upgrades. There are no runtime dependencies.

Full Changelog: v0.0.2...v0.0.3

v0.0.2

Choose a tag to compare

@edwardsph edwardsph released this 27 Aug 10:11
52bc9bd

Bugfix

  • hasErrorResponse and hasProblemDetails now check of undefined and null, preventing runtime errors.

New Features

  • Node 22 is now supported

v0.0.1

Choose a tag to compare

@NSeydoux NSeydoux released this 08 Jul 09:45
f5a3a47

Note: Both the major and minor versions being zero, this is still an alpha release. Breaking change may happen on any version bump.

New Features

  • InruptClientError: Superclass for all Inrupt client libraries runtime errors.
  • ClientHttpError, hasProblemDetails, hasErrorResponse: Class for runtime error
    thrown upon reception of an HTTP error response, i.e. 4xx and 5xx ranges. The two
    associated type guards are available to test for the presence of the specific properties
    exposed by the class.
  • BadRequestError, ConflictError, ForbiddenError, GoneError, InternalServerError,
    MethodNotAllowedError, NotAcceptableError, NotFoundError, PreconditionFailedError,
    TooManyRequestsError, UnauthorizedError, UnsupportedMediaTypeError: Specializations
    of the ClientHttpError to represent common HTTP error responses.
  • handleErrorResponse: a function to map the received HTTP error to the appropriate error
    class.