Have added with NPM and Yarn, still same result
yarn add v0.24.5
info No lockfile found.
[1/4] 馃攳 Resolving packages...
error Couldn't find package "@expo/bunyan" on the "npm" registry.
info Visit https://yarnpkg.com/en/docs/cli/add for documentation about this command.
yarnpkg add --dev --exact --ignore-optional react-native-scripts failed
Partial output of create-react-native-app Project --verbose:
npm http fetch GET 200 https://repo.forge.lmig.com/content/repositories/ets-npm/xdl 455ms
npm http fetch GET 404 https://repo.forge.lmig.com/content/repositories/ets-npm/@expo%2fbunyan 926ms
npm verb stack Error: 404 Not Found: @expo/[email protected]
npm verb stack at fetch.then.res (/usr/local/lib/node_modules/npm/node_modules/pacote/lib/fetchers/registry/fetch.js:42:19)
npm verb stack at tryCatcher (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/util.js:16:23)
npm verb stack at Promise._settlePromiseFromHandler (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/promise.js:512:31)
npm verb stack at Promise._settlePromise (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/promise.js:569:18)
npm verb stack at Promise._settlePromise0 (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/promise.js:614:10)
npm verb stack at Promise._settlePromises (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/promise.js:693:18)
npm verb stack at Async._drainQueue (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/async.js:133:16)
npm verb stack at Async._drainQueues (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/async.js:143:10)
npm verb stack at Immediate.Async.drainQueues (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/async.js:17:14)
npm verb stack at runCallback (timers.js:781:20)
npm verb stack at tryOnImmediate (timers.js:743:5)
npm verb stack at processImmediate [as _immediateCallback] (timers.js:714:5)
npm verb cwd /Users/n0268865/planningPoker
npm verb Darwin 16.6.0
npm verb argv "/usr/local/Cellar/node/8.4.0/bin/node" "/usr/local/bin/npm" "install" "--verbose" "--save-dev" "--save-exact" "react-native-scripts"
npm verb node v8.4.0
npm verb npm v5.5.1
npm ERR! code E404
npm ERR! 404 Not Found: @expo/[email protected]
npm verb exit [ 1, true ]
EDIT:
I pulled down the code and ran npm i --verbose inside react-native-scripts and it again failed on @expo/bunyon. I switch the dependency to just bunyon and I'm getting more of the same (last 2 attempts):
npm http fetch GET 404 https://repo.forge.lmig.com/content/repositories/ets-npm/@expo%2fspawn-async 821ms
npm http fetch GET 404 https://repo.forge.lmig.com/content/repositories/ets-npm/@expo%2fjson-file 864ms
npm http fetch GET 404 https://repo.forge.lmig.com/content/repositories/ets-npm/@expo%2fosascript 866ms
npm http fetch GET 404 https://repo.forge.lmig.com/content/repositories/ets-npm/@expo%2fschemer 886ms
npm http fetch GET 404 https://repo.forge.lmig.com/content/repositories/ets-npm/@expo%2fbunyan 888ms
npm verb stack Error: 404 Not Found: @expo/spawn-async@^1.2.8
npm http fetch GET 404 https://repo.forge.lmig.com/content/repositories/ets-npm/@expo%2fosascript 797ms
npm http fetch GET 404 https://repo.forge.lmig.com/content/repositories/ets-npm/@expo%2fjson-file 802ms
npm http fetch GET 404 https://repo.forge.lmig.com/content/repositories/ets-npm/@expo%2fschemer 840ms
npm http fetch GET 404 https://repo.forge.lmig.com/content/repositories/ets-npm/@expo%2fbunyan 846ms
npm http fetch GET 404 https://repo.forge.lmig.com/content/repositories/ets-npm/@expo%2fspawn-async 894ms
npm verb stack Error: 404 Not Found: @expo/osascript@^1.8.0
Come on, you wan't people to use your framework and you can't even make sure that the simplest get started example works?
use the normal npm registry. if it's still a problem, this is a npm bug, so open the issue there. make sure you're using latest version of yarn if you're using yarn. create-react-native-app isn't a package manager and this is a package manager bug.
Realized I had the company's registry, setting it to default worked. I've never had a problem installing other packages so I didn't bother to check that out. Thanks!
As far as I can tell, I am using the default npm registry. I have tried this with various versions of nodejs (7.x, 6.x and now 9.x) and various versions of npm as well. I've done:
sudo npm uninstall -g create-react-native-app
sudo npm install -g create-react-native-app
to reinstall with the latest versions of everything. I'm running on the latest version of High Sierra. And I continue to see the above errors when running create-react-native-app my-app.
I'm rather baffled by this.
Logs:
verbose 0.805 Request "https://registry.yarnpkg.com/lru-cache" finished with status code 200.
verbose 0.807 Performing "GET" request to "https://registry.yarnpkg.com/external-editor".
verbose 0.863 Request "https://registry.yarnpkg.com/@expo%2fbunyan" finished with status code 404.
verbose 0.863 Performing "GET" request to "https://registry.yarnpkg.com/figures".
verbose 0.864 Error: Couldn't find package "@expo/[email protected]" required by "react-native-scripts" on the "npm" registry.
at new MessageError (/usr/local/Cellar/yarn/1.5.1_1/libexec/lib/cli.js:186:110)
at PackageRequest.<anonymous> (/usr/local/Cellar/yarn/1.5.1_1/libexec/lib/cli.js:36274:17)
at Generator.throw (<anonymous>)
at step (/usr/local/Cellar/yarn/1.5.1_1/libexec/lib/cli.js:98:30)
at /usr/local/Cellar/yarn/1.5.1_1/libexec/lib/cli.js:111:13
at <anonymous>
at process._tickCallback (internal/process/next_tick.js:160:7)
Fixed a similar issue by install a missing prereq react-native-cli
Make sure you have a React Native CLI installed on your machine. To install it, run the following command in the Terminal: npm install -g react-native-cli.
I have the same problem.
npm registry is configured for https://registry.npmjs.org/
it's giving 404 for all packages named like @expo/bunyan or @expo/osascript.
I've also installed react-native-cli... that does not work. It seems to be an npm problem, but create-react-native-app could just refer latest versions of expo.
Most helpful comment
use the normal npm registry. if it's still a problem, this is a npm bug, so open the issue there. make sure you're using latest version of yarn if you're using yarn. create-react-native-app isn't a package manager and this is a package manager bug.