micromatch
crater
micromatch | crater | |
---|---|---|
4 | 23 | |
2,618 | 615 | |
0.8% | 2.3% | |
4.4 | 7.8 | |
15 days ago | about 1 month ago | |
JavaScript | Rust | |
MIT License | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
micromatch
-
A CLI for developing in monorepos, not building them
Packages on the RHS can contain wildcards, but must be escaped with brackets if so. We use micromatch for matching. Refer to their documentation for questions on matching behavior and available functionality.
-
Control your npm dependencies
All of the downloads are from an old version of https://github.com/micromatch/micromatch.
-
NPM – is-even, 160k weekly downloads
https://github.com/i-voted-for-trump/
> i-voted-for-trump
> This is a joke. You'll only see this org if you are attempting to troll me about repositories I created when I was learning to program.
> is-odd
> I created this in 2014, the year I learned how to program. All of the downloads are from an old version of https://github.com/micromatch/micromatch. I've done a few other things since: https://xn--gith-tc7a
-
BREAKING!! NPM package ‘ua-parser-js’ with more than 7M weekly download is compromised
Since then they've made things that are IMO quite useful, like enquirer, micromatch, and remarkable.
crater
-
Semver violations are common, better tooling is the answer
yup, they reference it as an inspiration: https://github.com/rust-lang/crater
it's probably impossible to automate an entire ecosystem, and there is value to enabling a tighter integration within a project ecosystem (a subset of the language ecosystem).
-
Trip Summer ISO C++ standards meeting (Varna, Bulgaria)
Rather than hypothesising about an imagined tool you could look at the actual tool which of course is in Rust's source code repo: https://github.com/rust-lang/crater
> new proposed C++ changes - are checked against only easily and "well-known" accessible package.
Now that I have, so to say, shown you mine, lets see yours. Where is the tool to perform these checks in C++?
-
GCC 13 and the state of gccrs
The "break things" part of "move fast" is not essential, Rust cares so much about breakage they literally compile and run the tests for every crate on crates.io and github using a tool called Crater. They do this just to test changes, even for stuff thats documented to be unstable, because thats just courtesy. And tooling makes it trivial to switch between Rust versions.
-
Do one thing, and do it well, or not.
The bot's named Crater if you want to look into it more.
-
Improving Rust compile times to enable adoption of memory safety
See https://github.com/rust-lang/crater
-
Discussion about the state of neovim's plugin ecosystem
Rust compiler developers use a tool called Crater to test potentially breaking compiler changes on all crates (Rust's name for libraries) uploaded to the official repository. If plugin stability is the issue, maybe a solution along these lines would be better than merging these plugins to Neovim's core?
-
Experienced C++ users: what do you like about Rust? How would you sell it to other C++ users?
https://github.com/rust-lang/crater is the bot they use to test proposed compiler/stdlib changes against slices of the crates.io library up to and including "all of it".
-
Data-driven performance optimization with Rust and Miri
The tool you're referring to is called Crater: https://github.com/rust-lang/crater.
- GHC 9.4.2 regresses being able to do math on aarch64
-
Rust for Linux officially merged
I'm pretty certain this isn't actually true. You should look at the editions, etc. Rust also has an insane guarantee which I am certain C/C++ don't offer: It rebuilds its entire library ecosystem each time it ships to make sure nothing breaks (https://crater.rust-lang.org). I've never seen an instance were old code didn't compile on a new compiler. Rust isn't forwards compatible (new code compiles on an old compiler) of course, but what is?
What are some alternatives?
picomatch - Blazing fast and accurate glob matcher written JavaScript, with no dependencies and full support for standard and extended Bash glob features, including braces, extglobs, POSIX brackets, and regular expressions. Used by GraphQL, Jest, Astro, Snowpack, Storybook, bulma, Serverless, fdir, Netlify, AWS Amplify, Revogrid, rollup, routify, open-wc, imba, ava, docusaurus, fast-glob, globby, chokidar, anymatch, cloudflare/miniflare, pts, and more than 5 million projects! Please follow picomatch's author: https://github.com/jonschlinkert
FluentValidation - A popular .NET validation library for building strongly-typed validation rules.
is-even - I created this in 2014, when I was learning how to program.
actix-net - A collection of lower-level libraries for composable network services.
emoji-regex - A regular expression to match all Emoji-only symbols as per the Unicode Standard.
Dapper - Dapper - a simple object mapper for .Net [Moved to: https://github.com/DapperLib/Dapper]
is-number - JavaScript/Node.js utility. Returns `true` if the value is a number or string number. Useful for checking regex match results, user input, parsed strings, etc.
AutoMapper - A convention-based object-object mapper in .NET.
is-odd - I created this in 2014, the year I learned how to program. All of the downloads are from an old version of https://github.com/micromatch/micromatch. I've done a few other things since: https://github.com/jonschlinkert.
rust-prehistory - historical archive of rust pre-publication development
GHSA-pjwm-rvh2-c87w
NUnit - NUnit Framework