{"action":"opened","issue":{"url":"https://api.github.com/repos/react-community/create-react-native-app/issues/424","repository_url":"https://api.github.com/repos/react-community/create-react-native-app","labels_url":"https://api.github.com/repos/react-community/create-react-native-app/issues/424/labels{/name}","comments_url":"https://api.github.com/repos/react-community/create-react-native-app/issues/424/comments","events_url":"https://api.github.com/repos/react-community/create-react-native-app/issues/424/events","html_url":"https://github.com/react-community/create-react-native-app/issues/424","id":262245003,"number":424,"title":"Error message about npm 5 not being supported is out of date","user":{"login":"joelpresence","id":12057689,"avatar_url":"https://avatars2.githubusercontent.com/u/12057689?v=4","gravatar_id":"","url":"https://api.github.com/users/joelpresence","html_url":"https://github.com/joelpresence","followers_url":"https://api.github.com/users/joelpresence/followers","following_url":"https://api.github.com/users/joelpresence/following{/other_user}","gists_url":"https://api.github.com/users/joelpresence/gists{/gist_id}","starred_url":"https://api.github.com/users/joelpresence/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/joelpresence/subscriptions","organizations_url":"https://api.github.com/users/joelpresence/orgs","repos_url":"https://api.github.com/users/joelpresence/repos","events_url":"https://api.github.com/users/joelpresence/events{/privacy}","received_events_url":"https://api.github.com/users/joelpresence/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2017-10-02T22:11:52Z","updated_at":"2017-10-02T22:11:52Z","closed_at":null,"author_association":"NONE","body":"Please make our job easier by filling this template out to completion. If you're requesting a feature instead of reporting a bug, please feel free to skip the Environment and Reproducible Demo sections.\r\n\r\n## Description\r\n\r\n1-2 sentences describing the problem you're having or the feature you'd like to request\r\n\r\nIf you try to `create-react-native-app` with npm 5 installed, you get a helpful message indicating that npm 5 doesn't work with react native right now.  That helpful message references https://github.com/npm/npm/issues/16991 .  However, the NPM team is no longer accepting comments on that issue and have locked it down.  Being sent to that issue is now frustrating to a newbie (like myself).  Could we update the \"react native doesn't work with npm 5\" message to reference that now-locked issue, but also mention that the issue is locked, and include a message like \"you'd better downgrade to npm 4, and here's how: npm install -g npm@4\".\r\n\r\nSee the final comments on the linked issue https://github.com/npm/npm/issues/16991\r\n```\r\nI'm gonna lock this 'cause I keep getting pinged and I can't imagine this conversation going anywhere good the way it's happening.\r\n\r\nAgain: we're working on the fixes. I'm just not using this issue to track it anymore because it is not an effective medium for it. We're collecting blockers in other ways and prioritizing what we'll be fixing in the next couple of weeks/months according to that.\r\n\r\nWe're also working on new stuff, which is needed in order to help stabilize stuff -- npm is in a bit of an interim state while we move to this new model, and we're rewriting and refactoring a lot of its core. This will help us make npm more maintainable/testable/patchable, and ultimately more stable. But while all that stuff lands, we're going to have all this very fresh code, and we're going to be finding a lot of corner cases our very large community had grown used to -- and we'll have solutions for those.\r\n\r\nMy suggestion for folks is that if you can't upgrade: wait for it. npm@5 is a massive shift from older version and introduces a ton of new things and workflows. The CLI team decided to release npm5 when we did because it worked for us and for a number of people -- and the positive changes with npm5 are huge enough that there's a lot of people willing to use the bleeding edge and who have had a great experience with it. The work now is to extend those benefits to the rest of y'all <3.\r\n```\r\nI can see @zkat's point about being pinged, but as a newbie, being led to that issue with no idea how to resolve things makes react native seem a bit flaky (if your first experience is that react native won't even create an app due to npm 5 issues) when in fact I find react native to be quite stable and awesome!  :-) I just want to help with the first time experience.\r\n\r\nWould you accept a PR to update this message?\r\n\r\n## Expected Behavior\r\n\r\nWhat action did you perform, and what did you expect to happen?\r\n\r\n## Observed Behavior\r\n\r\nWhat actually happened when you performed the above actions?\r\n\r\nIf there's an error message, please paste the *full terminal output and error message* in this code block:\r\n\r\n```\r\nError text goes here!\r\n```\r\n\r\n## Environment\r\n\r\nPlease run these commands in the project folder and fill in their results:\r\n\r\n* `npm ls react-native-scripts`:\r\n* `npm ls react-native`:\r\n* `npm ls expo`:\r\n* `node -v`:\r\n* `npm -v`:\r\n* `yarn --version`:\r\n* `watchman version`:\r\n\r\nAlso specify:\r\n\r\n1. Operating system:\r\n2. Phone/emulator/simulator & version:\r\n\r\n## Reproducible Demo\r\n\r\nPlease provide a minimized reproducible demonstration of the problem you're reporting.\r\n\r\nIssues that come with minimal repro's are resolved much more quickly than issues where a maintainer has to reproduce themselves.\r\n"}}
{"actor":{"display_login":"joelpresence"}}