tjsr/@tjsr/action-npm-outdated
Check for outdated npm packages
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
Inputs
| name | description | required | default |
|---|---|---|---|
| dependency | Dependency to check | yes | — |
| project | The target project name that must be the owner of the package. This is usually the directory name the package.json file resides under, not the name field in package.json | no | — |
| failOnNoNewVersion | Whether the build should fail with an exit code if no new version is available for the specified package | no | false |
| skipNpmCiExecute | Whether to skip the npm ci command execution being called implicitly | no | true |
| projectPath | The path to the project to run npm-related scripts within | no | — |
| useLatest | Whether to use the latest version of the package rather than the compatible wanted version. | no | false |
Outputs
| name | description |
|---|---|
| current | The current version used by the package |
| hasNewVersion | Whether or not there is a new version |
| latest | The latest version available |
| wanted | The version wanted by the package |
| dependent | The dependent package name - should be the same as the project input value |