Release v9.0.0 · npm/cli
9.0.0 (2022-10-19) ⚠️ BREAKING CHANGES npm is now compatible with the following semver range for node: ^14.17.0 || ^16.13.0 || >=18.0.0 npm will no longer attempt to modify ownership of files it creates the presence of auth related settings that are not scoped to a specific registry found in a config file is no longer supported and will throw errors login, adduser, and auth-type changes legacy aut
[RRFC] Change the default save-prefix from ^ to none · Issue #509 · npm/rfcs
(Ported from npm/cli#4227) TLDR This PR changes the default behaviour of NPM to not save package versions with the ^ prefix. Instead, packages would be saved with no prefix. As a TL;DR, the implications of this is that all dependencies will be pinned to the version you installed by default. Changing This Yourself If you're reading this PR and want to apply it to your own environments, invoke npm c
![[RRFC] Change the default save-prefix from ^ to none · Issue #509 · npm/rfcs](https://cdn-ak-scissors.b.st-hatena.com/image/square/7151739049775dd451b336b47ac31ef71aeca3b0/height=288;version=1;width=512/https%3A%2F%2Fopengraph.githubassets.com%2F4ef62f29af41028e3b0eae1c0bbfa2049f77b18bf3d69a6443b58332590f9f95%2Fnpm%2Frfcs%2Fissues%2F509)
⚠️ [RRFC] Breaking changes for `npm@8` · Issue #445 · npm/rfcs
Motivation ("The Why") Consolidate comms & desired feature-set for next version of the npm CLI (ie. v8) We are approaching the node@16 "Active LTS" Release milestone & want to make some decisions quickly In this next release our team has expressed an interest to... minimize breaking changes increase supportability while decreasing our maintenance burden align more closely with node's release caden
![⚠️ [RRFC] Breaking changes for `npm@8` · Issue #445 · npm/rfcs](https://cdn-ak-scissors.b.st-hatena.com/image/square/5798881ef751b99865831ee7da8cf8457d171df9/height=288;version=1;width=512/https%3A%2F%2Fopengraph.githubassets.com%2F371de195f3ffa49c7eeff11bd95725907e44512124dc885a9e97b21c2551c839%2Fnpm%2Frfcs%2Fissues%2F445)
[FEATURE] opt-in install and postinstall scripts · npm/rfcs · Discussion #80
What / Why install and postinstall are npm scripts that run while npm install ${package} or npm ci. It means that we allow the package author to run any scripts on our machine, which is definitely dangerous if we don't recognize what packages are installed as dependencies. Unfortunately, it might be impossible to recognize all the dependencies on your project so we run scripts we don't know while
![[FEATURE] opt-in install and postinstall scripts · npm/rfcs · Discussion #80](https://cdn-ak-scissors.b.st-hatena.com/image/square/89cf293f5adcfe9e8e23a979153502808884414f/height=288;version=1;width=512/https%3A%2F%2Fopengraph.githubassets.com%2Fc10494af8d2693c962d16428ffef32136070b1784c5d330cb86ce1b77c0a925a%2Fnpm%2Frfcs%2Fdiscussions%2F80)
rfcs/0001-package-aliases.md at latest · npm/rfcs · GitHub
Dismiss Join GitHub today GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together. Sign up Package Aliases Summary This proposal introduces a new package alias system that allows installation of packages with names other than the ones in package.json, as well as a new dependency type that allows referencing registry-hosted
rfcs/0010-monorepo-subdirectory-declaration.md at latest · npm/rfcs · GitHub
Monorepo subdirectory declaration Summary Add an optional directory field to the repository declaration a package makes in its package.json. If populated, use this directory to construct a more accurate link to the package's source code from its www.npmjs.com show page, and include it in the API response from registry.npmjs.org. Motivation Currently if a package is developed within a monorepo then
npm/tink: a dependency unwinder for javascript
tink tink is an experimental package manager for JavaScript. Don't expect to be able to use this with any of your existing projects. IN DEVELOPMENT This package is still in development. Do not use it for production. It is missing major features and the interface should be considered extremely unstable. If you're feeling adventurous, though, read ahead... Usage $ npx tink Table of Contents Features
package-lock.json and optional packages · Issue #17722 · npm/npm
I'm opening this issue because: npm is doing something I don't understand. What's going wrong? Npm accidently make changes to package-lock.json How can the CLI team reproduce the problem? Assume you have a 2 developers, one on mac, and one on linux. You use npm@5.1 and your project depends on chokidar package. That package has optional dependency of fsevents, which is useful only for mac. So, you
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
[RRFC] npm init add a new question: type => "commonjs/module" · Issue #620 · npm/rfcs
`.valid()` trims build metadata?.. · Issue #264 · npm/node-semver
feat: set engines and prerelease for npm 10 by lukekarrys · Pull Request #6674 · npm/cli
GitHub - npmhub/npmhub: 🔎 A browser extension to explore npm dependencies on GitHub repos
install: fix install checks for optional/dev dependencies by larsgw · Pull Request #76 · npm/cli
[BUG] Critical dependency: the request of a dependency is an expression after upgrade to 7.0.0 · Issue #299 · npm/node-semver
Add `rtl` option to coerce from right to left · npm/node-semver@388ec1c
GitHub - npm/stringify-package: stringifies npm-written json files
rfcs/0002-changelog.md at latest · npm/rfcs · GitHub
https://github.com/npm/npm/blob/canary/doc/cli/npm-archive.md
feat: add npm init support of git, path, url, and version names by jdalton · Pull Request #20403 · npm/npm
Release v6.1.0-next.0 · npm/npm