mike-works / mike-works/modern-javascript
Dependency deprecation warning: travis-deploy-once (npm)
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 13
- Forks
- 9
- Avg merge
- 7d 5h
- Merged PRs (30d)
- 1
Description
On registry https://registry.npmjs.org/, the "latest" version (v5.0.11) of dependency travis-deploy-once has the following deprecation notice:
We recommend to use Travis Build Stages instead
Marking the latest version of an npm package as deprecated results in the entire package being considered deprecated, so contact the package author you think this is a mistake.
Affected package file(s): package.json
If you don't care about this, you can close this issue and not be warned about travis-deploy-once's deprecation again. If you would like to completely disable all future deprecation warnings then add the following to your config:
"suppressNotifications": ["deprecationWarningIssues"]
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting package.json and the dependency notice for travis-deploy-once v5.0.11 on npm. Confirm whether the project still uses this dependency and decide, with maintainer guidance, whether it should be removed or replaced by Travis Build Stages; done means the deprecation warning is addressed or intentionally documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100