NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
npm · #1970 most downloaded on npm
Wildcard matching tools
Last release 3 years ago
no release in 18 months
Ships unpredictably
gaps range from 3 weeks to 4.2 years
Rarely documented
notes for 1 of 11 stable releases
Nothing withdrawn
no release was ever pulled
15 years old
11 releases · first in 2012
Nothing published for this version
The major issue addressed in this release is how wildcard would behave when it was provided a standalone wildcard (*) or a wildcard led pattern (*.foo
The major issue addressed in this release is how wildcard would behave when it was provided a standalone wildcard (*) or a wildcard led pattern (*.foo). Prior to merging #11 sensible matches would fail and this has now been addressed.
For details on exactly what wildcard matches when, I'd recommend taking a look at the strings test file as that is fairly easy to read, plus if there is a case that you feel should be covered in the tests that isn't please feel free to raise a PR (it would be greatly appreciated).
One column per quarter.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Your coding agent can read these notes before it upgrades. Set up the MCP server →