Security News
CISA Brings KEV Data to GitHub
CISA's KEV data is now on GitHub, offering easier access, API integration, commit history tracking, and automated updates for security teams and researchers.
500-pagelet
Advanced tools
This Pagelet is responsible for displaying server errors. By default the 500 Pagelet is provided with BigPipe. However, if you need a custom 500 you can extend this Pagelet. For example to change the default view.
The 500 Pagelet is distributed through the node package manager (npm).
npm install --save 500-pagelet
Got stuck? Or can't wrap your head around a concept or just want some feedback, we got a dedicated IRC channel for that on Freenode:
irc.freenode.net
#bigpipe
Still stuck? Create an issue. Every question you have is a bug in our documentation and that should be corrected. So please, don't hesitate to create issues, many of them.
In this example the 500 Pagelet is extended with a custom view. BigPipe will automatically discover this extended version if it is provided to BigPipe alongside the other pagelets. Note that the enviroment variable can be overruled to manage the data that is displayed.
'use strict';
//
// Extend the 500 Pagelet with a custom view.
//
var Fivehundred = require('500-pagelet').extend({
view: '/path/to/my/custom-view.html', // your custom layout
env: 'development' // defaults to process.env.NODE_ENV
});
//
// Initialise BigPipe server.
//
var pipe = require('bigpipe').createServer(2000, {
pagelets: [ Fivehundred, ... ]
});
The following methods are available on the 500 Pagelet instance. Most are only used internally. There is rarely a reason to call these methods.
public, returns Pagelet.
The 500 constructor expects several options to be provided, these
include: req
, res
and pipe
. The last option is a reference
to the BigPipe instance, mainly to ensure the same Temper
instance is re-used. All code examples assume your file is setup as:
'use strict';
var Fivehundred = require('500-pagelet');
, fivehundred = new Fivehundred({ options }, new Error('failure'));
private, returns Pagelet.
Extracts the data from the provided Error to render the template.
If the environment is production the Error.stack
will not be
provided to the template.
fivehundred.get(function render(error, data) {
// provide data to pagelet.render
});
The library makes use the diagnostics
module from Pagelet.
To display the 500 Pagelet specific debug messages, supply the
following before running the program or
DEBUG=pagelet:500 node ...
Tests are automatically run on Travis CI to ensure that everything is
functioning as intended. For local development we automatically install a
pre-commit hook that runs the npm test
command every time you commit changes.
This ensures that we don't push any broken code in to this project.
To run tests locally, make sure the development dependencies are installed.
npm test
npm run coverage
500-pagelet is released under MIT.
FAQs
Default 500 Pagelet used if anything fails in BigPipe
The npm package 500-pagelet receives a total of 11 weekly downloads. As such, 500-pagelet popularity was classified as not popular.
We found that 500-pagelet demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 2 open source maintainers 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
CISA's KEV data is now on GitHub, offering easier access, API integration, commit history tracking, and automated updates for security teams and researchers.
Security News
Opengrep forks Semgrep to preserve open source SAST in response to controversial licensing changes.
Security News
Critics call the Node.js EOL CVE a misuse of the system, sparking debate over CVE standards and the growing noise in vulnerability databases.