Gathering detailed insights and metrics for assert
NPM was acquired by GitHub in March 2020.
Gathering detailed insights and metrics for assert
NPM was acquired by GitHub in March 2020.
npm install assert
91.9
Supply Chain
91.9
Quality
81.5
Maintenance
100
Vulnerability
298 Stars
199 Commits
58 Forks
9 Watching
4 Branches
37 Contributors
Updated on 07 Nov 2024
Minified
Minified + Gzipped
JavaScript (100%)
Cumulative downloads
Total Downloads
Last day
16.4%
2,620,188
Compared to previous day
Last week
19.3%
13,596,577
Compared to previous week
Last month
12.6%
54,647,755
Compared to previous month
Last year
-1%
646,308,161
Compared to previous year
The
assert
module from Node.js, for the browser.
With browserify, simply require('assert')
or use the assert
global and you will get this module.
The goal is to provide an API that is as functionally identical to the Node.js assert
API as possible. Read the official docs for API documentation.
To use this module directly (without browserify), install it as a dependency:
npm install assert
assert
Due to differences between browsers, some error properties such as message
and stack
will be inconsistent. However the assertion behaviour is as close as possible to Node.js and the same error code
will always be used.
Bundlers like webpack 5
and Vite.js
(and possibly others) don't automatically include polyfills for Node.js APIs. Like most packages on npm, this module depends on other Node.js APIs, so it won't work with these bundlers without also including a polyfill for the process
Node.js global. You can use this library to polyfill the process
global.
Note that this is not a flaw in this package - this package will work without any manual configuration with browserify
and webpack 4
and other working bundlers. Unfortunately, some bundlers decided to require an explicit allow-list of all Node.js API specific packages instead of having them work out of the box, hence the incompatibility. See https://github.com/browserify/commonjs-assert/issues/55 for some more context.
To contribute, work on the source files. Then build and run the tests against the built files. Be careful to not introduce syntax that will be transpiled down to unsupported syntax. For example, for...of
loops will be transpiled to use Symbol.iterator
which is unavailable in IE.
npm run build
Builds the project into the build
dir.
npm run dev
Watches source files for changes and rebuilds them into the build
dir.
npm run test
Builds the source files into the build
dir and then runs the tests against the built project.
npm run test:nobuild
Runs the tests against the built project without rebuilding first.
This is useful if you're debugging in the transpiled code and want to re-run the tests without overwriting any changes you may have made.
npm run test:source
Runs the tests against the unbuilt source files.
This will only work on modern Node.js versions.
npm run test:browsers
Run browser tests against the all targets in the cloud.
Requires airtap credentials to be configured on your machine.
npm run test:browsers:local
Run a local browser test server. No airtap configuration required.
When paired with npm run dev
any changes you make to the source files will be automatically transpiled and served on the next request to the test server.
MIT © Joyent, Inc. and other Node contributors
No vulnerabilities found.
Reason
license file detected
Details
Reason
security policy file detected
Details
Reason
no binaries found in the repo
Reason
no dangerous workflow patterns detected
Reason
0 existing vulnerabilities detected
Reason
Found 4/22 approved changesets -- score normalized to 1
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
dependency not pinned by hash detected -- score normalized to 0
Details
Reason
detected GitHub workflow tokens with excessive permissions
Details
Reason
branch protection not enabled on development/release branches
Details
Reason
project is not fuzzed
Details
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
Score
Last Scanned on 2024-11-11
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More