npmpackage.info

Gathering detailed insights and metrics for @semantic-release/error

Other packages similar to @semantic-release/error

@types/semantic-release__error

3.0.3

TypeScript definitions for @semantic-release/error

semantic-release

24.2.0

Automated semver compliant package publishing

@semantic-release/github

11.0.1

semantic-release plugin to publish a GitHub release and comment on released Pull Requests/Issues

fork-ts-checker-webpack-plugin

9.0.2

Runs typescript type checker and linter on separate process.

Gathering detailed insights and metrics for @semantic-release/error

@semantic-release/error

💥 💬 errors but with error code

4.0.0

MIT

JavaScript

255.00 B

323,716,757 7.4

Installations

npm install @semantic-release/error

Pull Requests

Open

2

Total

351

Closed

67

Merged

282

Issues

Open

2

Total

13

Closed

11

Releases

v4.0.0

Published on 07 Jun 2023

v3.0.0

Published on 17 Sept 2021

v3.0.0-beta.1

Published on 03 Sept 2021

v2.2.0

Published on 10 Feb 2018

v2.1.0

Published on 29 Oct 2017

v2.0.1

Published on 29 Oct 2017

View all 8 releases

Developer

semantic-release

Developer Guide

BETA

Module System

ESM

Min. Node Version

>=18

Typescript Support

No

Node Version

18.16.0

NPM Version

9.5.1 Statistics

10 Stars

326 Commits

8 Forks

4 Watching

3 Branches

15 Contributors

Updated on 26 Nov 2024

Bundle Size

386.00 B

Minified

255.00 B

Minified + Gzipped

Bundlephobia

Languages

JavaScript (100%)

Total Downloads

Cumulative downloads

Total Downloads

323,716,757

Last day

-1.4%

670,439

Compared to previous day

Last week

7.7%

4,128,161

Compared to previous week

Last month

20.4%

15,693,262

Compared to previous month

Last year

71%

131,152,814

Compared to previous year

Daily Downloads

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dev Dependencies

ava c8 codecov prettier

Versions

@semantic-release/error

Error type used by all semantic-release packages.

Errors of type SemanticReleaseError or an inherited type will be considered by semantic-release as an expected exception case (no release to be done, running on a PR etc..). That indicate to the semantic-release process to stop and exit with the 0 success code.

Any other type of error will be considered by semantic-release as an unexpected error (i/o issue, code problem etc...). That indicate to the semantic-release process to stop, log the error and exit with the 1 failure code.

Usage

1import SemanticReleaseError from "@semantic-release/error";
2
3// Default
4throw new SemanticReleaseError();
5
6// With error message
7throw new SemanticReleaseError("An error happened");
8
9// With error message and error code
10throw new SemanticReleaseError("An error happened", "ECODE");
11
12// With error message, error code and details
13throw new SemanticReleaseError("An error happened", "ECODE", "Here is some suggestions to solve this error.");
14
15// With inheritance
16class InheritedError extends SemanticReleaseError {
17  constructor(message, code, newProperty, details) {
18    super(message);
19    Error.captureStackTrace(this, this.constructor);
20    this.name = this.constructor.name;
21    this.code = code;
22    this.details = details;
23    this.newProperty = "newProperty";
24  }
25}
26
27throw new InheritedError("An error happened", "ECODE", "Here is some suggestions to solve this error.");

No vulnerabilities found.

10

Code-Review

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

10

Maintained

Determines if the project is "actively maintained".

10

Binary-Artifacts

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

10

Dangerous-Workflow

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

10

Pinned-Dependencies

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

10

License

Determines if the project has defined a license.

10

Security-Policy

Determines if the project has published a security policy.

10

Packaging

Determines if the project is published as a package that others can easily download, install, easily update, and uninstall.

10

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

0

Token-Permissions

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

0

CII-Best-Practices

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

0

Fuzzing

Determines if the project uses fuzzing.

0

SAST

Determines if the project uses static code analysis.

Score

7.4

/10

Last Scanned on 2024-11-25

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