{"action":"created","issue":{"url":"https://api.github.com/repos/npm/npm/issues/16510","repository_url":"https://api.github.com/repos/npm/npm","labels_url":"https://api.github.com/repos/npm/npm/issues/16510/labels{/name}","comments_url":"https://api.github.com/repos/npm/npm/issues/16510/comments","events_url":"https://api.github.com/repos/npm/npm/issues/16510/events","html_url":"https://github.com/npm/npm/issues/16510","id":226159083,"number":16510,"title":"npm@5 beta tracking","user":{"login":"zkat","id":17535,"avatar_url":"https://avatars2.githubusercontent.com/u/17535?v=3","gravatar_id":"","url":"https://api.github.com/users/zkat","html_url":"https://github.com/zkat","followers_url":"https://api.github.com/users/zkat/followers","following_url":"https://api.github.com/users/zkat/following{/other_user}","gists_url":"https://api.github.com/users/zkat/gists{/gist_id}","starred_url":"https://api.github.com/users/zkat/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/zkat/subscriptions","organizations_url":"https://api.github.com/users/zkat/orgs","repos_url":"https://api.github.com/users/zkat/repos","events_url":"https://api.github.com/users/zkat/events{/privacy}","received_events_url":"https://api.github.com/users/zkat/received_events","type":"User","site_admin":false},"labels":[{"id":597514195,"url":"https://api.github.com/repos/npm/npm/labels/npm5","name":"npm5","color":"b60205","default":false}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":25,"created_at":"2017-05-04T01:45:21Z","updated_at":"2017-05-26T09:53:50Z","closed_at":null,"body":"This is the official npm@5 beta tracking issue listing known issues and, if relevant, workarounds. The npm@5 beta will run from May 4 to May 30, when it will (hopefully) be released as part of node@8.\r\n\r\nTo install the beta, you can run `npm i -g npm5`. This will give you an `npm5` binary and leave your regular `npm` command intact. Use `npm5` in the command line in order to use the beta.\r\n\r\nFor the general changelog and release-branch tracking issue, see #16244. The feature list for npm5 is listed there.\r\n\r\nWant to help? Check for [tagged `npm5` issues](https://github.com/npm/npm/issues?q=is%3Aopen+is%3Aissue+label%3Anpm5), or pick up any of the open bugs in [`pacote`](https://github.com/zkat/pacote/issues), [`cacache`](https://github.com/zkat/cacache), or [`make-fetch-happen`](https://github.com/zkat/make-fetch-happen). These libraries are all fundamental infrastructure for the new cache, and any improvements will have a direct effect on npm5 itself.\r\n\r\n### Known Issues\r\n\r\nThe following issues are known, and will (hopefully!) be fixed by the time npm5 goes to `latest` on May 30th:\r\n\r\n* The new `notice` loglevel messes with some tools that use `npmlog`. For example, you might see verbose log output from `node-pre-gyp` during lifecycle script execution.\r\n\r\n* directory dependencies aren't quite done yet in a couple of cases: you might see weird issues with dependencies of dir dependencies causing errors, or even `Max callstack exceeded` errors for certain combinations.\r\n\r\n* cross-platform `package-lock.json` is still pending some WIP patches. _Soooooooon_\r\n\r\n* some `git+ssh` services are failing to authenticate (but others are not?)\r\n\r\n### Fixed Issues\r\n\r\n* **FIXED** in`beta.34` ~a bad commit accidentally broke cache corruption recovery. Oops! Fix forthcoming.~\r\n\r\n* **FIXED** in `beta.35` ~dependencies in package.json with spaces in them fail to match (#16520)~\r\n\r\n* **FIXED** in `beta.36` ~dependencies with `=` don't resolve (#16524)~\r\n\r\n* **FIXED** in `beta.37` (thanks, @zarenner!) ~npm5 fails to authenticate for registries that aren't hosted at the host root (#16528)~\r\n\r\n* **FIXED** in `beta.38` This wasn't an npm5 bug per se, but some packages had tarballs with package.json data that did not match the package metadata uploaded (???). npm5 compensates a bit for this now. ~There's apparently some situations where extraneous packages get added, or correct packages get marked as extraneous (#16517)~\r\n\r\n* **FIXED** in `beta.43` (thanks, @ivanph!) ~npm5 sends original auth headers with tarballs hosted outside of the manifest registry (https://github.com/zkat/pacote/issues/87, https://github.com/npm/node-fetch-npm/issues/1)~\r\n\r\n* **FIXED** in `beta.46` ~Lockfiles are still generated off the filesystem, so they are not yet fully cross-platform.~\r\n\r\n* **FIXED** in `beta.46` ~Bundled dependencies might be replaced even if marked as bundled in your `package-lock.json`. This should only yield a warning, since npm will simply replace acceptable versions of those dependencies with regular downloads.~\r\n\r\n* **FIXED** in `beta.46` ~Local file/directory dependencies are not complete and will have weird interactions with the `package-lock.json`. This is pending merging https://github.com/npm/npm/tree/link-specifier (#16536)~\r\n\r\n* **FIXED** in `beta.47` ~Global installs are failing with a `cannot read 'package' of null` error (#16603)~\r\n\r\n* **FIXED** in `beta.48` ~npm crashes with a url not being a valid semver spec (#16600)~\r\n\r\n* **FIXED** in `beta.50` ~npm fails to send auth data to scoped private registries~\r\n\r\n* **FIXED** in `beta.56` ~`package.json` might be saved even if `package-lock.json` fails to save for some reason. (nb: this should happen much less as of `beta.46`)~\r\n\r\n* **FIXED** in `beta.56` ~The installer is still erroneously marking some packages as extraneous (#16517)~\r\n\r\n* **FIXED** in `beta.57` ~`npm update` will by default save any updated `devDeps` as if they were `dependencies`.~\r\n\r\n* **FIXED** in `beta.58` (Thanks, @nlkluth!) ~Downloads the redirect from http to https and vice versa are not supported right now (#16613, https://github.com/zkat/make-fetch-happen/issues/26)~\r\n\r\n* **FIXED** in `beta.59` and `beta.60` (Thanks, @yyjdelete!) ~http->https tunneling proxies don't work~\r\n\r\n* **FIXED** in `beta.61` ~`uid must be an unsigned int` error during install (#16544)~\r\n\r\n* **FIXED** in `beta.63` ~Using a proxy will keep the proxy agent alive, preventing the node process from exiting. You can safely `^C` out if this happens.~\r\n\r\n* **FIXED** in `beta.63` ~Some users have reported symlink issues while upgrading the beta. We tracked down the race, and there should be a fix very soon (#16686)~\r\n\r\n* **FIXED** in `beta.64` ~Installing with `sudo` will write cache entries as `root` instead of dropping permissions for cache writes (#16707)~\r\n\r\n* **FIXED** in `beta.69` ~username/password registry auth doesn't seem to be working at least for some people~\r\n\r\n* **FIXED** in `beta.69` ~package-lock entries previously marked as `optional: true` or `dev: true`, or even `bundled: true` are having those settings clobbered on the following install and written back as full, regular deps.~\r\n\r\n* **FIXED** in `npm@5.0.0` ~The `prepare`, `prepublish`, `prepublishOnly` dance isn't quite set in stone yet. Things might be a bit confusing. (https://github.com/npm/npm/issues/16685)~"},"comment":{"url":"https://api.github.com/repos/npm/npm/issues/comments/304241218","html_url":"https://github.com/npm/npm/issues/16510#issuecomment-304241218","issue_url":"https://api.github.com/repos/npm/npm/issues/16510","id":304241218,"user":{"login":"simonua","id":8005145,"avatar_url":"https://avatars3.githubusercontent.com/u/8005145?v=3","gravatar_id":"","url":"https://api.github.com/users/simonua","html_url":"https://github.com/simonua","followers_url":"https://api.github.com/users/simonua/followers","following_url":"https://api.github.com/users/simonua/following{/other_user}","gists_url":"https://api.github.com/users/simonua/gists{/gist_id}","starred_url":"https://api.github.com/users/simonua/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/simonua/subscriptions","organizations_url":"https://api.github.com/users/simonua/orgs","repos_url":"https://api.github.com/users/simonua/repos","events_url":"https://api.github.com/users/simonua/events{/privacy}","received_events_url":"https://api.github.com/users/simonua/received_events","type":"User","site_admin":false},"created_at":"2017-05-26T09:53:50Z","updated_at":"2017-05-26T09:53:50Z","body":"@zkat and team, congratulations on the 5.0.0 release! Awesome stuff! \r\n\r\nWill you maintain the 5.0.0-beta.x releases if or while remaining items on the npm5 bug tracker may be worked through between now and Tuesday? I want to keep working with npm5 side-by-side, but I am not quite comfortable yet replacing 4.6.1 as my rock-solid backup.\r\n\r\nThank you! =)"}}
{"actor":{"display_login":"simonua"}}