Meet the team
See all 1 on GitHub →
Commit activity
Last 12 weeks · 0 commits
Community health
4 of 6 standards met
Recent fixes
Hey, I came into this project when tracking dependencies over a suite that I'm using internally and see this package as used by others. However, from the README I don't see the pretended usage of this. Could you please explain what's the possible advantage of using Versus Using Javascript's intrinsic type constructor directly? Are you polyfilling the errors for old Node versions? I don't see that in the implementation. I'd be happy to make a proposal for better docs, but I don't really understand what's really the value of this package, that's why I'm raising this question 😅 Thanks!
When trying to install the package (npm i es-errors@1.3.0), I get an error: No matching version found for es-errors@1.3.0. The same happens with v1.2.1 Version that works: v1.0.0 Tried on: Node 18, Node 16
Repository: ljharb/es-errors. Description: A simple cache for a few of the JS Error constructors. Stars: 11, Forks: 3. Primary language: JavaScript. Languages: JavaScript (100%). License: MIT. Topics: ecmascript, error, javascript, rangeerror, syntaxerror, typeerror. Open PRs: 0, open issues: 1. Last activity: 2y ago. Community health: 85%. Top contributors: ljharb.