quinn-respond
Advanced tools
respond(body | { statusCode, headers, body })Create a new QuinnResponse.
The body can be a string, a buffer, or a stream.
If no body is provided, it defaults to a through stream.
See the test directory for usage examples.
.status(code)Chainable way to modify res.statusCode.
.header(name, value)Chainable alternative to .setHeader.
.pipe(res)Forward response to node http response.
The minimum requirement for something to be seen as an HTTP response
is the presence of a setHeader method.
respond.text(body | { statusCode, headers, body })Same as respond but sets a text/plain content type.
respond.html(body | { statusCode, headers, body })Same as respond but sets an text/html content type.
respond.json(data, visitor, indent)Serialize the data and create an application/json response.
FAQs
Response generation for quinn
The npm package quinn-respond receives a total of 1 weekly downloads. As such, quinn-respond popularity was classified as not popular.
We found that quinn-respond 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
The UK is proposing a bold ban on ransomware payments by public entities to disrupt cybercrime, protect critical services, and lead global cybersecurity efforts.
Security News
Snyk's use of malicious npm packages for research raises ethical concerns, highlighting risks in public deployment, data exfiltration, and unauthorized testing.
Research
Security News
Socket researchers found several malicious npm packages typosquatting Chalk and Chokidar, targeting Node.js developers with kill switches and data theft.