Taskfile | npm | |
---|---|---|
5 | 48 | |
325 | 17,233 | |
- | - | |
0.0 | 2.1 | |
5 months ago | almost 4 years ago | |
Shell | JavaScript | |
- | 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.
Taskfile
- Shell Taskfile
-
What’s with DevOps engineers using `make` of all things?
https://github.com/adriancooney/Taskfile - my favourite for its simplicity. A shell alias and a shell script with a function for each "job". No need to learn yet another tool when you just want to run a few pre-defined commands from a project's root. I think, if you're going to complain about make, then maybe all you really need is a shell script.
- Alternatives to Makefile for Python
-
How a true gentleman navigate in Linux or Unix terminal...
You want to use $@ rather than $* so you don't have to do double-quoting on arguments that have spaces in them. That said, I'm gonna steal this. Also if you like clever composability tricks check out Taskfiles, I've adopted them all over in my own code.
-
I Prefer Makefiles over Package.json Scripts
I was amazed to discover Taskfile. Didn't realise it was a copy of Make.
https://github.com/adriancooney/Taskfile
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?
just - 🤖 Just a command runner
pnpm - Fast, disk space efficient package manager
turborepo - Incremental bundler and build system optimized for JavaScript and TypeScript, written in Rust – including Turborepo and Turbopack. [Moved to: https://github.com/vercel/turbo]
corepack - Zero-runtime-dependency package acting as bridge between Node projects and their package managers
Task - A task runner / simpler Make alternative written in Go
spm
magicfile - Simple Makefile template for documenting frequent commands.
yarn - The 1.x line is frozen - features and bugfixes now happen on https://github.com/yarnpkg/berry
tup - Tup is a file-based build system.
Bower - A package manager for the web
cod-stats - All-inclusive ETL pipeline to pull Modern Warfare statistics and generate statistical reporting for a playgroup
jspm