Installations

npm install @types/semantic-release__error

Developer Guide

BETA

Typescript

Yes

Module System

N/A

Pull Requests

Open

152

Total

61,819

Closed

9,749

Merged

51,918

Issues

Open

565

Total

8,085

Closed

7,520

Releases

1

0.1.450

Updated on Sep 04, 2019

View All 1 releases

Languages

3

TypeScript

JavaScript

Shell

TypeScript (99.84%)

JavaScript (0.15%)

Shell (0.01%)

Developer

DefinitelyTyped

Download Statistics

Total Downloads

0

Last Day

0

Last Week

0

Last Month

0

Last Year

0

GitHub Statistics

NOASSERTION License

50,032 Stars

89,737 Commits

30,433 Forks

640 Watchers

6 Branches

9,957 Contributors

Updated on Jul 14, 2025

Maintainers

1

View All 9,957 Contributors

Package Meta Information

Latest Version

3.0.3

Package Id

@types/semantic-release__error@3.0.3

Unpacked Size

6.74 kB

Size

2.12 kB

File Count

5

Published on

Nov 07, 2023

Total Downloads

Cumulative downloads

Total Downloads

NaN

Last Day

0%

NaN

Compared to previous day

Last Week

0%

NaN

Compared to previous week

Last Month

0%

NaN

Compared to previous month

Last Year

0%

NaN

Compared to previous year

Weekly Downloads

Monthly Downloads

Yearly Downloads

Installation

npm install --save @types/semantic-release__error

Summary

This package contains type definitions for @semantic-release/error (https://github.com/semantic-release/error).

Details

Files were exported from https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/semantic-release__error.

index.d.ts

1/**
2 * Error type used by all [semantic-release](https://github.com/semantic-release/semantic-release) packages.
3 *
4 * Errors of type `SemanticReleaseError` or an inherited type will be considered by
5 * [semantic-release](https://github.com/semantic-release/semantic-release) as an expected exception case
6 * (no release to be done, running on a PR etc..). That indicate to the `semantic-release` process to stop
7 * and exit with the `0` success code.
8 *
9 * Any other type of error will be considered by
10 * [semantic-release](https://github.com/semantic-release/semantic-release) as an unexpected error
11 * (i/o issue, code problem etc...). That indicate to the `semantic-release` process to stop, log the error
12 * and exit with the `1` failure code.
13 *
14 * @example
15 * import SemanticReleaseError = require("@semantic-release/error");
16 *
17 * // Default
18 * throw new SemanticReleaseError();
19 *
20 * // With error message
21 * throw new SemanticReleaseError("An error happened");
22 *
23 * // With error message and error code
24 * throw new SemanticReleaseError("An error happened", "ECODE");
25 *
26 * // With error message, error code and details
27 * throw new SemanticReleaseError("An error happened", "ECODE", "Here is some suggestions to solve this error.");
28 *
29 * // With inheritance
30 * class InheritedError extends SemanticReleaseError {
31 *   constructor(message, code, newProperty, details) {
32 *     super(message);
33 *     Error.captureStackTrace(this, this.constructor);
34 *     this.name = this.constructor.name;
35 *     this.code = code;
36 *     this.details = details;
37 *     this.newProperty = "newProperty";
38 *   }
39 * }
40 *
41 * throw new InheritedError("An error happened", "ECODE", "Here is some suggestions to solve this error.");
42 */
43declare class SemanticReleaseError extends Error {
44    name: "SemanticReleaseError";
45
46    code: string | undefined;
47
48    details: string | undefined;
49
50    semanticRelease: true;
51
52    constructor(message?: string, code?: string, details?: string);
53}
54
55export = SemanticReleaseError;
56

Additional Details

Last updated: Tue, 07 Nov 2023 15:11:36 GMT
Dependencies: none

Credits

These definitions were written by Alex Mendes, and BendingBender.

No vulnerabilities found.

10

Maintained

Determines if the project is "actively maintained".

10

Security-Policy

Determines if the project has published a security policy.

10

Dangerous-Workflow

Determines if the project's GitHub Action workflows avoid dangerous patterns.

10

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

10

Binary-Artifacts

Determines if the project has generated executable (binary) artifacts in the source repository.

9

Code-Review

Determines if the project requires human code review before pull requests (aka merge requests) are merged.

9

License

Determines if the project has defined a license.

8

Pinned-Dependencies

Determines if the project has declared and pinned the dependencies of its build process.

0

CII-Best-Practices

Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.

0

Token-Permissions

Determines if the project's workflows follow the principle of least privilege.

0

SAST

Determines if the project uses static code analysis.

0

Fuzzing

Determines if the project uses fuzzing.

Score

7

/10

Last Scanned on 2025-07-07

The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.

Learn More