he/him 
node-semver which is what npm and yarn use is entirely regex-based which makes validation extremely crude.https://github.com/npm/node-semver
Show this thread
Continuing the trend of nice error messages. Validation of package.json including parsing of semver ranges/versions with frames pointing to the exact source location in JSON. A combination of a custom JSON parser, and then chaining it with a custom semver parser with an offset.pic.twitter.com/dQC3U5JEI9
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Validating SPDX expression with suggestion for mistyped license namepic.twitter.com/B4sS3PqENC
Show this thread -
Again, very limited amount of code. Same code handles normalization.pic.twitter.com/czspktg0vN
Show this thread
End of conversation
New conversation -
-
-
It doesn't introduce any new capabilities, just makes the errors more accessible. Tools can already tell you "this dependency value is bad" but don't actually tell you what about it is bad.
- 1 more reply
New conversation -
-
-
This functionality was easy to hook up once all the pieces were in place, which was required for other features anyway. This is the entire code for the `name` field validation.pic.twitter.com/SxKRVMDPT6
Show this threadThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Is there a plan to support JSON Schema validation?
-
There's no schema here, it's just a programattic API for consuming JSON that throws an error that's caught by something that reports it. There could be something around it that checks it against JSON schema though.
- 1 more reply
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.