Gathering detailed insights and metrics for native-abort-controller
Gathering detailed insights and metrics for native-abort-controller
Gathering detailed insights and metrics for native-abort-controller
Gathering detailed insights and metrics for native-abort-controller
Returns native AbortController/AbortSignal if available or the abort-controller module if not
npm install native-abort-controller
Module System
Min. Node Version
Typescript Support
Node Version
NPM Version
2 Stars
25 Commits
3 Forks
3 Watching
2 Branches
1 Contributors
Updated on 20 Sept 2021
Minified
Minified + Gzipped
JavaScript (100%)
Cumulative downloads
Total Downloads
Last day
36.3%
6,958
Compared to previous day
Last week
31.8%
36,867
Compared to previous week
Last month
-13.1%
147,032
Compared to previous month
Last year
-25.4%
2,186,041
Compared to previous year
1
3
Returns native AbortController/AbortSignal if available or the abort-controller module if not
An (almost) drop-in replacement for the abort-controller
module that returns the native AbortController if available or the polyfill if not.
Some environments such as the Electron Renderer process straddle the node/browser divide with features from both APIs available. In these cases the webpack approach of always using the browser
field in your package.json
to override requires is too heavy-handed as sometimes you want to use the node version of an API.
Instead we can check for the availability of a given API and return it, rather than the node-polyfill for that API.
This module may become unecessary if mysticatea/abort-controller#24 is resolved.
You must install a version of abort-controller
alongside this module to be used if a native implementation is not available.
1$ npm install --save native-abort-controller abort-controller
1import { AbortController } from 'native-abort-controller' 2 3const controller = new AbortController() 4const signal = controller.signal 5 6signal.addEventListener('abort', () => { 7 console.log('aborted!') 8}) 9 10controller.abort()
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
no dangerous workflow patterns detected
Reason
0 existing vulnerabilities detected
Reason
Found 0/25 approved changesets -- score normalized to 0
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
detected GitHub workflow tokens with excessive permissions
Details
Reason
dependency not pinned by hash detected -- score normalized to 0
Details
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
security policy file not detected
Details
Reason
license file not detected
Details
Reason
project is not fuzzed
Details
Reason
branch protection not enabled on development/release branches
Details
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
Score
Last Scanned on 2024-11-25
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