pants | npm | |
---|---|---|
35 | 48 | |
3,098 | 17,233 | |
0.8% | - | |
9.8 | 2.1 | |
6 days ago | over 3 years ago | |
Python | JavaScript | |
Apache License 2.0 | Artistic License 2.0 |
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.
pants
-
The xz attack shell script
> C/C++'s header system with conditional inclusion
Wouldn't it be more accurate to say something like "older build systems"? I don't think any of the things you listed are "modern". Which isn't a criticism of their legacy! They have been very useful for a long time, and that's to be applauded. But they have huge problems, which is a big part of why newer systems have been created.
FWIW, I have been using pants[0] (v2) for a little under a year. We chose it after also evaluating it and bazel (but not nix, for better or worse). I think it's really really great! Also painful in some ways (as is inevitably the case with any software). And of course it's nearly impossible to entirely stomp out "genrules" use cases. But it's much easier to get much closer to true hermeticity, and I'm a big fan of that.
0: https://www.pantsbuild.org/
-
Monorepo + Microservices + Dependency Managment + Build system HELL
Does pants/bazel can help me?
- Pants 2: The ergonomic build system
-
Go Dependency management in large company projects - How do you do it?
Hyper-large tech companies managing hyper-large monorepos using Bazel (google), buck (Facebook), please (thought machine), pants (Twitter, Foursquare & Square) enjoy them but also have a lot of resources devoted to running and maintaining it.
-
Reason to use other Build Tool than Make?
Yeah there's definitely some alternatives out there. Pants is another one that has a lot of traction.
-
Is it possible pickle a function with its dependencies?
You should look into pex, or it’s parent build system pants. A PEX (Python EXecutable) file can package up all your code including dependencies and run on another machine of similar OS with just an available compatible interpreter.
-
Sanity check of my decision for "Iterative AI" (DVC, MLEM, CML) pipeline over Azure ML
We don't have the CD yet, but I think what I put in place counts as simple CI (even if incomplete)? Every push & PR trigger an azure pipeline, which runs pants. This install the dependencies from the lockfile, run some linters, uses DVC to pull the data necessary for tests, and run unit tests (mypy check is deactivated until I solve a weird error). Basically the same script runs on laptops cross-platform (one of us uses Max, one Ubuntu with GPU, one Ubuntu with CPU, the scripts runs on every platform). The only difference with CI is the installation of Pants and the gestion of Cache (needs to be downloaded in CI so it takes ~3min in CI versus 20 seconds on my laptop).
- Pants 2: fast, scalable, user-friendly build system for codebases of all sizes
-
Maintain a Clean Architecture in Python with Dependency Rules
This has also been recently integrated in pants.
https://github.com/pantsbuild/pants/issues/13393
- Blazing fast CI with MicroVMs
npm
-
XML is better than YAML
The fact that JSON doesn't support comments is so annoying, and I always thought that Douglas Crockford's rationale for this basically made no sense ("They can be misused!" - like, so what, nearly anything can be misused. So without support for comments e.g. in package.json files I have to do even worse hacky workaround bullshit like "__some_field_comment": "this is my comment"). There is of course jsonc and JSON5 but the fact that it's not supported everywhere means 10 years later we still can't write comments in package.json (there is https://github.com/npm/npm/issues/4482 and about a million related issues).
-
Jest not recommended to be used in Node.js due to instanceOf operator issues
Things like the sparkline charts on npmjs (e.g. https://www.npmjs.com/package/npm ) are interactive SVGs. I think they're pretty common for data visualizations of all kinds
-
JavaScript registry NPM vulnerable to 'manifest confusion' abuse
I actually did a POC 7 years ago about this - https://github.com/tanepiper/steal-ur-stuff
It was reported to npm at the time, but they chose to ignore it - https://github.com/npm/npm/issues/17724
-
I'm a Teapot
Every time this pops up, I'm reminded of the day that the NPM registry started returning 418 responses.
I remember being at a training course that day and my manager asking me what we could do to fix it because our CI was failing to pull dependencies from NPM.
Trying to explain that NPM was returning a status code intended as an April Fools joke and which was never meant to see the light of production was quite difficult
https://github.com/npm/npm/issues/20791
-
Dissecting Npm Malware: Five Packages And Their Evil Install Scripts
I should really get around to how I discovered this 6 years ago and still nothing done about it
-
Attackers are hiding malware in minified packages distributed to NPM
Whenever something like this comes up I usually have to tap the sign (and the original report)
-
NPM Vs PNPM
NPM is not "Node Package Manager". https://www.npmjs.com/package/npm
-
A not so unfortunate sharp edge in Pipenv
> which can be overriden with env setting
Support for this is not great. Lots of packages still don't support this properly. My experience matches the 2015 comment https://github.com/npm/npm/issues/775#issuecomment-71294085
> Not sure why "symlinks" would be involved.
If you make your node_modules a symlink, multiple packages will fail. Even if you're not interested in doing that, others are.
> What NPM does is leaps and bounds ahead
Unless you change your node / gyp version. It doesn't really have a concept of runtime version. You can restrict it, but not have two concurrent versions if they conflict.
-
Front-end Guide
[email protected] was released in May 2017 and it seems to address many of the issues that Yarn aims to solve. Do keep an eye on it!
-
Framework axios pushed a broken update, crippling thousands of websites
I think it's had been supposed to do that since forever. Apart from some bug in npm 5.3. Are you sure your package-lock versions actually conform to the semver ranges in your package.json?
What are some alternatives?
Bazel - a fast, scalable, multi-language and extensible build system
pnpm - Fast, disk space efficient package manager
megalinter - 🦙 MegaLinter analyzes 50 languages, 22 formats, 21 tooling formats, excessive copy-pastes, spelling mistakes and security issues in your repository sources with a GitHub Action, other CI tools or locally.
corepack - Zero-runtime-dependency package acting as bridge between Node projects and their package managers
please - High-performance extensible build system for reproducible multi-language builds.
spm
pyflow - An installation and dependency system for Python
yarn - The 1.x line is frozen - features and bugfixes now happen on https://github.com/yarnpkg/berry
pyupgrade - A tool (and pre-commit hook) to automatically upgrade syntax for newer versions of the language.
Bower - A package manager for the web
Buck - A fast build system that encourages the creation of small, reusable modules over a variety of platforms and languages.
jspm