Installations

npm install gulp-prettyerror

Pull Requests

Open

2

Total

8

Closed

4

Merged

2

Issues

Open

0

Total

5

Closed

5

Releases

1

Detailed Error Messages

v1.2.0

Published on 28 Jan 2017

View all 1 releases

Developer

AndiDittrich

Developer Guide

BETA

Module System

CommonJS

Min. Node Version

Typescript Support

No

Node Version

NPM Version

Statistics

14 Stars

17 Commits

1 Forks

2 Watching

3 Branches

2 Contributors

Updated on 01 Sept 2024

Languages

JavaScript (98.26%)

Shell (1.74%)

Total Downloads

Cumulative downloads

Total Downloads

111,106

Last day

-40.9%

68

Compared to previous day

Last week

-23.6%

431

Compared to previous week

Last month

-37.3%

2,037

Compared to previous month

Last year

66.3%

31,915

Compared to previous year

Daily Downloads

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dependencies

3

ansi-colors gulp-plumber gulplog

Dev Dependencies

4

gulp gulp-rename gulp-sourcemaps gulp-uglify

Versions

GULP-PrettyError

Display Errors in a pretty way, without breaking watching tasks

1$ yarn add gulp-prettyerror

Screenshot

Features

Simple, Robust and Easy to use
Displays task errors during development without breaking gulp-watch tasks
Uses gulp-plumber to override the standard error handling
Output styling created with gulplog and ansi-colors

Usage

1var prettyError = require('gulp-prettyerror');
2
3// default release build
4gulp.task('js', function (){
5    return gulp.src(['Source/Lib/**/*.js')
6        // add task error-handler
7        .pipe(prettyError())
8
9        // create sourcemaps for development
10        .pipe(sourcemaps.init())
11
12        // some stuff
13        .pipe(...);
14});

Any Questions ? Report a Bug ? Enhancements ?

Please open a new issue on GitHub

License

Gulp-PrettyError is OpenSource and licensed under the Terms of The MIT License (X11). You're welcome to contribute!

No vulnerabilities found.

10

Binary-Artifacts

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

10

License

Determines if the project has defined a license.

3

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

1

Code-Review

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

0

Maintained

Determines if the project is "actively maintained".

0

CII-Best-Practices

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

0

Security-Policy

Determines if the project has published a security policy.

0

Fuzzing

Determines if the project uses fuzzing.

0

Branch-Protection

Determines if the default and release branches are protected with GitHub's branch protection settings.

0

SAST

Determines if the project uses static code analysis.

Score

2.3

/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