ERR! 418 I'm a teapot (this is not a joke) · Issue #20791 · npm/npmYou signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert
Critical Linux filesystem permissions are being changed by latest version · Issue #19883 · npm/npm
I'm opening this issue because: npm is crashing. npm is producing an incorrect install. npm is doing something I don't understand. Other (see below for feature requests): What's going wrong? This issue has been happening ever since 5.7.0 was released a few hours ago. It seems to have completely broken my filesystem permissions and caused me to have to manually fix the permissions of critical files
Many packages suddenly disappeared · Issue #255 · npm/registry · 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 Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community. Pick a username Email Address Password Sign up for GitHub By clicking “Sign up for GitHub”, you agr
RFC: New npm link commands · Issue #19421 · npm/npm
Refreshing the npm link command This is a breaking change due to the all new npm link, the splitting of npm unlink from npm rm and the removal of npm install --link. PROBLEM The introduction of lock files and a synchronization workflow in npm@5 broke certain assumptions that the npm link and npm install --link commands took advantage of. They expected that they could replace a real module with a s
Release v5.5.0 · npm/npm
With the default two-factor authentication mode you'll be prompted to enter a one-time password when logging in, when publishing and when modifying access rights to your modules. TOKEN MANAGEMENT You can now create, list and delete authentication tokens from the comfort of the command line. Authentication tokens created this way can have NEW restrictions placed on them. For instance, you can creat
Release v5.2.0 (2017-07-05) · npm/npm
It's only been a couple of days but we've got some bug fixes we wanted to get out to you all. We also believe that npx is ready to be bundled with npm, which we're really excited about! npx!!! npx is a tool intended to help round out the experience of using packages from the npm registry — the same way npm makes it super easy to install and manage dependencies hosted on the registry, npx is meant
Release v5.1.0 · npm/npm
Hey y'all~ We've got some goodies for you here, including npm@5's first semver-minor release! This version includes a huge number of fixes, particularly for some of the critical bugs users were running into after upgrading npm. You should overall see a much more stable experience, and we're going to continue hacking on fixes for the time being. Semver-major releases, specially for tools like npm,
Release v5.0.0 · npm/npm
Wowowowowow npm@5! This release marks months of hard work for the young, scrappy, and hungry CLI team, and includes some changes we've been hoping to do for literally years. npm@5 takes npm a pretty big step forward, significantly improving its performance in almost all common situations, fixing a bunch of old errors due to the architecture, and just generally making it more robust and fault-toler
release: npm@5.0.0 by zkat · Pull Request #16244 · npm/npm
NOTE: This PR is a WIP. npm@5 beta is currently underway. See #16510 for deets. Wowowowowow npm@5! This release marks months of hard work for the young, scrappy, and hungry CLI team, and includes some changes we've been hoping to do for literally years. npm@5 takes npm a pretty big step forward, significantly improving its performance in almost all common situations, fixing a bunch of old errors d
Release v4.3.0 · npm/npm
Yay! Release time! It's a rainy day, and we have another smallish release for y'all. These things are not necessarily related. Or are they 🌧🤔 As far as news go, you may have noticed that the CLI team dropped support fornode@0.12 when that version went out of maintenance. Still, we've avoided explicitly breaking it and node@0.10 so far -- but not much longer. Sometime soon, the CLI team plans on
Release v4.0.0 · npm/npm
Welcome to npm@4, friends! This is our first semver major release since the release of npm@3 just over a year ago. Back then, @3 turned out to be a bit of a ground-shaking release, with a brand-new installer with significant structural changes to how npm set up your tree. This is the end of an era, in a way. npm@4 also marks the release when we move both npm@2 and npm@3 into maintenance: We will n
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
Release v6.0.0-next.2 · npm/npm
feat: add npm init <create-pkg-name> command by jdalton · Pull Request #20303 · npm/npm
npm/CHANGELOG.md at 47de40cc2d3bdd7c2b9545232908c7d98ddbff3b · npm/npm
spec: Describe npm-shrinkwrap.json and package-lock.json by iarna · Pull Request #16441 · npm/npm
GitHub - npmhub/npmhub: 🔎 A browser extension to explore npm dependencies on GitHub repos
"npm search" runs out of memory and dies without good error · Issue #3867 · npm/npm
npm install --depth 0 · Issue #10435 · npm/npm
conventional-changelog-atom 502 Bad Gateway · Issue #13284 · npm/npm
Remove unpublish by tlrobinson · Pull Request #12017 · npm/npm
