react-hotkeys-hook
Advanced tools
react-hotkeys-hook - npm Package Compare versions
Comparing version 0.1.4 to 1.0.0
| { | ||
| "name": "react-hotkeys-hook", | ||
| "version": "0.1.4", | ||
| "version": "1.0.0", | ||
| "main": "dist/index.js", | ||
@@ -5,0 +5,0 @@ "typings": "dist/index.d.ts", |
@@ -55,7 +55,7 @@ # react-hotkeys-hook | ||
| ```typescript | ||
| useHotkey(keys: string, callback: (event: KeyboardEvent, handler: HotkeysEvent) => void) | ||
| useHotkeys(keys: string, callback: (event: KeyboardEvent, handler: HotkeysEvent) => void) | ||
| ``` | ||
| The `useHotkey` hook follows the [hotkeys] call signature. | ||
| The callback function takes the exact parameters as the callback function in the hotkeys-js package. | ||
| The `useHotkeys` hook follows the [hotkeys] call signature. | ||
| The callback function takes the exact parameters as the callback function in the hotkeys package. | ||
| See [hotkeys] documentation for more info or look into the typings file. | ||
@@ -62,0 +62,0 @@ |
Sorry, the diff of this file is not supported yet
New alerts
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
Major refactor
Supply chain riskPackage has recently undergone a major refactor. It may be unstable or indicate significant internal changes. Use caution when updating to versions that include significant changes.
Found 1 instance in 1 package
Uses eval
Supply chain riskPackage uses dynamic code execution (e.g., eval()), which is a dangerous practice. This can prevent the code from running in certain environments and increases the risk that the code may contain exploits or malicious behavior.
Found 1 instance in 1 package
Dynamic require
Supply chain riskDynamic require can indicate the package is performing dangerous or unsafe dynamic code execution.
Found 1 instance in 1 package
Fixed alerts
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
No v1
QualityPackage is not semver >=1. This means it is not stable and does not support ^ ranges.
Found 1 instance in 1 package
Improved metrics
- Total package byte prevSize
- increased by534.33%
3001155
- Number of package files
- increased by16.67%
21
- Lines of code
- increased by16550%
21312
- Number of low quality alerts
- decreased by-50%
1
Worsened metrics
- Number of low supply chain risk alerts
- increased by100%
2
- Number of medium supply chain risk alerts
- increased byInfinity%
2