ljharb

npm-deprecations

Given an npm module name, get a map of npm version numbers to deprecation messages.

by ljharb
deprecationdeprecationsnpm
Star on GitHubForknpm

JavaScript

4 stars0 forks1 contributorQuiet · 2y agoSince 2014MIT

Meet the team

See all 1 on GitHub →
ljharb
ljharb194 contributions

Languages

View on GitHub →
JavaScript100%

Commit activity

Last 12 weeks · 0 commits

Full graph →

Community health

4 of 6 standards met

Community profile →
85
✓README✓License✓Contributing✓Code of Conduct○Issue Template○PR Template

Recent fixes

View closed PRs →
ljharb
[Tests] migrate tests to Github ActionsMergedPR

Per https://github.com/ljharb/object.assign/pull/81 travis-ci's new pricing plan, and its defaults, have caused all my repos to have zero CI whatsoever until December. @travis-ci Support is MIA, so I unfortunately can't rely on it as a service anymore.

ljharb · 5y ago
freaktechnik
Fails with NPM 5.5.1ClosedIssue

On messages.js#15 the parse fails, because it gets an empty string. My quick fix locally was to add a check to the if one line earlier.

freaktechnik · 8y ago
Structured data for AI agents

Repository: ljharb/npm-deprecations. Description: Given an npm module name, get a map of npm version numbers to deprecation messages. Stars: 4, Forks: 0. Primary language: JavaScript. Languages: JavaScript (100%). License: MIT. Topics: deprecation, deprecations, npm. Open PRs: 0, open issues: 0. Last activity: 2y ago. Community health: 85%. Top contributors: ljharb.