npm | Pipenv | |
---|---|---|
48 | 33 | |
17,233 | 24,609 | |
- | 0.3% | |
2.1 | 9.4 | |
over 3 years ago | 1 day ago | |
JavaScript | Python | |
Artistic License 2.0 | 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.
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?
Pipenv
-
Pipenv VS instld - a user suggested alternative
2 projects | 9 Dec 2023
- Managing dependencies - pipenv?
-
Adding Virtual Environments to Git Repo
pipenv solves this by having both kinds of requirement files: Pipfile lists package names and known constraints on which versions can be used, while Pipfile.lock gives specific package versions with hashes. Theoretically the Pipfile (and its lockfile) format were supposed to be a standard that many different tools could use, but I haven't seen it get adopted much outside of pipenv itself, so I'm not sure if it's really going to catch on.
- Renaming folders is usually a bad idea right?
-
A not so unfortunate sharp edge in Pipenv
* Tons of longstanding bugs that fail to be resolved in any sort of timely manner like this one: https://github.com/pypa/pipenv/issues/2413
I am sick and tired of the python packaging space pushing this godawful tool for Python. Please just use pip-tools or poetry instead.
-
Publish Webhooks From Your FastAPI API With Convoy
ℹ️ You may use a different virtual environment manager like Pipenv or poetry.
- Why does Pipenv install do the same thing as Pipenv install --ignore-pipfile
-
pipenv integration with neovim
Hey lua would you mind looking at this question for me? https://github.com/pypa/pipenv/discussions/5411
-
Top 10 Python security best practices
Alternatively, you can look into Pipenv, which has a lot more tools to develop secure applications with.
-
Why Fedora still has pipenv v2021.5.29? Over five updates since, the last v2022.3.28
https://github.com/pypa/pipenv/releases https://bodhi.fedoraproject.org/updates/?search=pipenv (pipenv-2021.5.29-7.fc35 for the current Fedora release)
What are some alternatives?
pnpm - Fast, disk space efficient package manager
Poetry - Python packaging and dependency management made easy
corepack - Zero-runtime-dependency package acting as bridge between Node projects and their package managers
pyenv - Simple Python version management
spm
virtualenv - Virtual Python Environment builder
yarn - The 1.x line is frozen - features and bugfixes now happen on https://github.com/yarnpkg/berry
PDM - A modern Python package and dependency manager supporting the latest PEP standards
Bower - A package manager for the web
pip-tools - A set of tools to keep your pinned Python dependencies fresh.
jspm
Pew - A tool to manage multiple virtual environments written in pure python