yaml-sucks
npm
yaml-sucks | npm | |
---|---|---|
10 | 48 | |
592 | 17,233 | |
- | - | |
2.2 | 2.1 | |
11 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.
yaml-sucks
- XML is better than YAML
- Lingy brings to Perl what Clojure did for Java
- Docker Compose With TOML?
-
This just sucks.
Here are some examples.
-
Python 3.11 is out !
It's got a pretty complex spec and it does not take much to become completely unreadable by humans, not to mention the issues with parsing it.
- Does viper catch yaml config files with invalid syntax
-
Bob: A build system beyond building
Even simple examples don't get parsed the same between implementations.
-
copygen: Generate type-to-type and field-to-field struct code without reflection or dependencies (391x faster than copier)
There are plenty of well documented issues with YAML.
-
How to use YAML Aliases
Looks like some of this is either unsupported or unpredictable by different YAML parsers: https://github.com/cblp/yaml-sucks
-
Tuxedo control center: community edition
YAML sucks, use TOML instead. It is much more sane and as easy to use as YAML.
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?
tuxedo-control-center - A tool to help you control performance, energy, fan and comfort settings on TUXEDO laptops.
pnpm - Fast, disk space efficient package manager
tuxedo-keyboard - This repository will no longer get any updates as the code here is now part of tuxedo-drivers https://gitlab.com/tuxedocomputers/development/packages/tuxedo-drivers.
corepack - Zero-runtime-dependency package acting as bridge between Node projects and their package managers
goverter - Generate type-safe Go converters by simply defining an interface
spm
LGV_MeetingServer - An aggregation server for meeting list servers.
yarn - The 1.x line is frozen - features and bugfixes now happen on https://github.com/yarnpkg/berry
nix-configs - My Nix{OS} configuration files
Bower - A package manager for the web
copygen - Go generator to copy values from type to type and fields from struct to struct (copier without reflection). Generate any code based on types.
jspm