eslint-plugin-restify-use-next
Advanced tools
eslint plugin to check if you call `next()` in your restify handler
eslint plugin to check if you call
next()in your restify handler 🎉
This rule enables you to verify that you are calling next() in your restify handlers.
Not calling next() has been a common mistake. Restify is different, and you have to call next() for your handler chains to work properly.
Works for simple cases. Open to PRs to enhance this plugin.
Install the module with: npm install eslint-plugin-restify-use-next --save-dev
Add to your existing eslint config file the following:
plugins: ['restify-use-next'],
rules: {
'restify-use-next/restify-use-next': 2
}
See API
Ensure that all linting and codestyle tasks are passing. Add unit tests for any new or changed functionality.
Before committing, lint and test your code using the included Makefile:
make prepush
Copyright (c) 2019 Rajat Kumar
Licensed under the MIT license.
FAQs
eslint plugin to check if you call `next()` in your restify handler
The npm package eslint-plugin-restify-use-next receives a total of 7 weekly downloads. As such, eslint-plugin-restify-use-next popularity was classified as not popular.
We found that eslint-plugin-restify-use-next demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
In this segment of the Risky Business podcast, Feross Aboukhadijeh and Patrick Gray discuss the challenges of tracking malware discovered in open source softare.
Research
Security News
A threat actor's playbook for exploiting the npm ecosystem was exposed on the dark web, detailing how to build a blockchain-powered botnet.
Security News
NVD’s backlog surpasses 20,000 CVEs as analysis slows and NIST announces new system updates to address ongoing delays.