is-js-error
Advanced tools
Check if a page contains a JavaScript error
npm install -g is-js-error
From the command line,
$ is-js-error example.com
✔ OK
# With a specific time to wait for before reporting no error (in ms)
$ is-js-error example.com --wait 3000
✔ OK
The exit status is 1 for a page that fails to load and 2 for a JS error.
This project relies on Electron, which requires a GUI. See the following Travis guide.
You first need to clone the project on your computer, and to install Node. This project uses nvm to execute a specific node version.
Install the project with:
git clone git@github.com:thibaudcolas/is-js-error.git
cd is-js-error
nvm install
npm install
npm install -g eslint babel-eslint eslint-config-airbnb
./.githooks/deploy
To run the tests:
npm run test
Test pages:
To release a new version:
npm version minor -m "Release %s"
git push origin master
git push --tags
npm publish
FAQs
Check if a page contains a JavaScript error
The npm package is-js-error receives a total of 1 weekly downloads. As such, is-js-error popularity was classified as not popular.
We found that is-js-error 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.
Research
/Security News
Socket identified 80 fake candidates targeting engineering roles, including suspected North Korean operators, exposing the new reality of hiring as a security function.
Application Security
/Research
/Security News
Socket detected multiple compromised CrowdStrike npm packages, continuing the "Shai-Hulud" supply chain attack that has now impacted nearly 500 packages.
Research
/Security News
Malicious update to @ctrl/tinycolor on npm is part of a supply-chain attack hitting 40+ packages across maintainers