npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@woigl/jsend

v1.2.2

Published

TypeScript and JavaScript utilities and HTTP middleware for creating, sending and verifying JSend responses.

Downloads

4

Readme

@woigl/jsend

code style: Prettier npm (scoped) License

TypeScript and JavaScript utilities and HTTP middleware for creating, sending and verifying JSend responses.

Installation

npm install -S @woigl/jsend

Response Creation

Responses can be created using the success, fail, and error methods:

// You can pass any data or a JSend response to success
jSend.success({ foo: 'bar' }); // { status: 'success', data: { foo: 'bar' } }
jSend.success(['foo', 'bar']); // { status: 'success', data: [ 'foo', 'bar' ] }
jSend.success('Some text'); // { status: 'success', data: 'Some text' }
jSend.success(4711); // { status: 'success', data: 4711 }
jSend.success(false); // { status: 'success', data: false }
jSend.success(null); // { status: 'success', data: null }

// You can pass any data or a JSend response to fail
jSend.fail({ reason: 'Some reason text' }); // { status: 'fail', data: { reason: 'Some reason text' } }
jSend.fail({ code: 'NOT_EXISTING' }); // { status: 'fail', data: { code: 'NOT_EXISTING' } }

// You can pass a message or an object with a message and optionally data and code
jSend.error('That just failed!'); // { status: 'error', message: 'That just failed!' }
jSend.error({
    code: 123,
    message: 'That just failed!'
}); // { status: 'error', code: 123, message: 'That just failed!' }
jSend.error({
    code: 123,
    message: 'That just failed!',
    data: {
        stack: '...'
    }
}); // { status: 'error', code: 123, message: 'That just failed!', data: { stack: '...' } }

HTTP Middleware

The jSend HTTP middleware provides methods for easily sending "success", "fail" and "error" responses and optionally allows to specify HTTP response status codes:

expressApp.use(jSend.middleware);

expressApp.get('/', function(req, res) {
    if(!checkToken(req.params.token)
        return res.jSend.sendFail({ authentication:['You are not authenticated'] }, 401);

    if(!req.params.someParam)
        return res.jSend.sendFail({ validation:['someParam is required'] });

    loadData(req.params.someParam, function(err, data) {
        if(err) return res.jSend.sendError(err);
        res.jSend.sendSuccess(data);
    });
});

Response Validation

By default jSend.isValid validates that all required properties exist.

// Returns true
jSend.isValid({
    status: 'success',
    data: { foo: 'bar' }
});

// Returns false
jSend.isValid({
    status: 'success'
});

// Returns true
jSend.isValid({
    status: 'success',
    data: { foo: 'bar' },
    junk: 'is ok'
});

Using jSendStrict.isValid instead of jSend.isValid causes to also validate that extraneous properties do not exist.

// Returns true
jSend.isValid({
    status: 'success',
    data: { foo: 'bar' }
});

// Returns false
jSend.isValid({
    status: 'success'
});

// Returns false
jSend.isValid({
    status: 'success',
    data: { foo: 'bar' },
    junk: 'is ok'
});

Validate if Response is "success"

You can also check if a response is a "success" response.

// Returns true
jSend.isSuccess({
    status: 'success',
    data: { foo: 'bar' }
});

// Returns false
jSend.isSuccess({
    status: 'error',
    data: { stack: '...' }
});

Use jSendStrict to check with strict mode enabled.

Validate if Response is "fail"

You can also check if a response is a "fail" response.

// Returns true
jSend.isFail({
    status: 'fail',
    data: { foo: 'bar' }
});

// Returns false
jSend.isFail({
    status: 'error',
    data: { stack: '...' }
});

Use jSendStrict to check with strict mode enabled.

Validate if Response is "error"

You can also check if a response is an "error" response.

// Returns true

jSend.isError({
    status: 'error',
    message: 'Error message',
    data: { stack: '...' }
});

// Returns false
jSend.isError({
    status: 'success',
    data: { foo: 'bar' }
});

Use jSendStrict to check with strict mode enabled.

Bugs, Feature Requests, Questions and so on...

If you want to report some bugs, have the need and ideas for enhancements, or you are just looking for some help or clarification, then just create an issue on GitHub at https://github.com/woigl/jsend/issues.

If you want to improve the code, then you can start straight with a pull request.

Expression of Gratitude

I would like to express my gratitude towards Matt Dunlap, who is the maintainer of the jsend NPM package. Unfortunately, the package did not satisfy my needs in terms of Typescript support and HTTP status codes. Therefore I've decided to develop a slightly similar library. Once again, thanks to Matt for his great work!

License

MIT