@lwc/signals
Advanced tools
@lwc/signals - npm Package Compare versions
Comparing version 0.0.0 to 6.2.0
| { | ||
| "name": "@lwc/signals", | ||
| "version": "0.0.0", | ||
| "description": "Placeholder for signals package", | ||
| "main": "index.js", | ||
| "author": "", | ||
| "license": "ISC" | ||
| } | ||
| "//": [ | ||
| "THIS FILE IS AUTOGENERATED. If you modify it, it will be rewritten by check-and-rewrite-package-json.js", | ||
| "You can safely modify dependencies, devDependencies, keywords, etc., but other props will be overwritten." | ||
| ], | ||
| "name": "@lwc/signals", | ||
| "version": "6.2.0", | ||
| "description": "Provides the interface to interact with reactivity from outside the framework", | ||
| "keywords": [ | ||
| "lwc" | ||
| ], | ||
| "homepage": "https://lwc.dev", | ||
| "repository": { | ||
| "type": "git", | ||
| "url": "https://github.com/salesforce/lwc.git", | ||
| "directory": "packages/@lwc/signals" | ||
| }, | ||
| "bugs": { | ||
| "url": "https://github.com/salesforce/lwc/issues" | ||
| }, | ||
| "license": "MIT", | ||
| "publishConfig": { | ||
| "access": "public" | ||
| }, | ||
| "main": "dist/index.cjs.js", | ||
| "module": "dist/index.js", | ||
| "types": "dist/index.d.ts", | ||
| "files": [ | ||
| "dist" | ||
| ], | ||
| "scripts": { | ||
| "build": "rollup --config ../../../scripts/rollup/rollup.config.js", | ||
| "dev": "rollup --config ../../../scripts/rollup/rollup.config.js --watch --no-watch.clearScreen" | ||
| }, | ||
| "nx": { | ||
| "targets": { | ||
| "build": { | ||
| "outputs": [ | ||
| "{projectRoot}/dist" | ||
| ] | ||
| } | ||
| } | ||
| } | ||
| } |
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
New author
Supply chain riskA new npm collaborator published a version of the package for the first time. New collaborators are usually benign additions to a project, but do indicate a change to the security surface area of a package.
Found 1 instance in 1 package
No contributors or author data
MaintenancePackage does not specify a list of contributors or an author in package.json.
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
Empty package
Supply chain riskPackage does not contain any code. It may be removed, is name squatting, or the result of a faulty package publish.
Found 1 instance in 1 package
No README
QualityPackage does not have a README. This may indicate a failed publish or a low quality package.
Found 1 instance in 1 package
No bug tracker
MaintenancePackage does not have a linked bug tracker in package.json.
Found 1 instance in 1 package
No repository
Supply chain riskPackage does not have a linked source code repository. Without this field, a package will have no reference to the location of the source code use to generate the package.
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
No website
QualityPackage does not have a website.
Found 1 instance in 1 package
Improved metrics
- Total package byte prevSize
- increased by3326.09%
5516
- Number of package files
- increased by600%
7
- Lines of code
- increased byInfinity%
58
- Number of low maintenance alerts
- decreased by-50%
1
- Number of low quality alerts
- decreased by-100%
0
- Number of medium quality alerts
- decreased by-100%
0
- Number of lines in readme file
- increased byInfinity%
76
- Number of low supply chain risk alerts
- decreased by-100%
0