geekyants / kitchensink-vue-native

KitchenSink app for Vue Native (using NativeBase)

NativeBase KitchenSink App For Vue Native

This project was bootstrapped with Vue Native Cli.

Demo

iOS	Android

Installation

• Clone and install packages

git clone https://github.com/GeekyAnts/KitchenSink-Vue-Native.git
cd KitchenSink-Vue-Native
npm install

• Run on iOS
  • Opt #1:
    • Run npm start in your terminal
    • Scan the QR code in your Expo app
  • Opt #2:
    • Run npm run ios in your terminal

• Run on Android
  • Opt #1:
    • Run npm start in your terminal
    • Scan the QR code in your Expo app
  • Opt #2:
    • Make sure you have an Android emulator installed and running
    • Run npm run android in your terminal

kitchensink-vue-native's Issues

project is not run

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] start: expo start
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\User\AppData\Roaming\npm-cache_logs\2020-06-29T16_39_08_330Z-debug.log
**here i attach the log file please suggest me what is the issue
2020-06-18T08_54_51_095Z-debug.log
**

what is the entry point file of this project

i want to know where is main.js or app.js fle tha was entry point for assign or use components

[Question] Replacing deprecated method calls?

Hey,

We're just looking into Vue Native and loving the project so far - started delving into the kitchen sink and noticed that much of it is using deprecated functionality.

Have you any intensions on replacing these with supported calls?

Thanks

Import Material Design

Is there any way that i can use the Material Design theme to a vue native Project...?

nb-*

Hi,
Can you point me in the right direction for where the nb components come from?
Is that native-base in App.vue?
Also, why don't you have to export a name like a normal Vue SFC?
Thanks.

Cannot render app

Using the exact repo I can't finish the build, using Expo and here's the screen with error.

Update Expo SDK

Project needs to be updated to support expo sdk 36 or higher. I attempted this myself by running expo update (updating to v39) though this completed the project still does not run

Unable to resolve @expo/vector-icons/AntDesign

I am not able to run app in it showing following issue

Unable to resolve @expo/vector-icons/AntDesign" from ".//node_modules/native-base/dist/src/basic/IconNB.js"

Multiple font errors

With cloned project:

Running application on Pixel 3a.

fontFamily "Roboto_medium" is not a system font and has not been loaded through Font.loadAsync.

- If you intended to use a system font, make sure you typed the name correctly and that it is supported by your device operating system.

- If this is a custom font, be sure to load it with Font.loadAsync.
- node_modules/expo/build/environment/muteWarnings.fx.js:27:24 in error
- ... 30 more stack frames from framework internals

fontFamily "ionicons" is not a system font and has not been loaded through Font.loadAsync.

- If you intended to use a system font, make sure you typed the name correctly and that it is supported by your device operating system.

- If this is a custom font, be sure to load it with Font.loadAsync.
- node_modules/expo/build/environment/muteWarnings.fx.js:27:24 in error
- ... 33 more stack frames from framework internals

fontFamily "ionicons" is not a system font and has not been loaded through Font.loadAsync.

- If you intended to use a system font, make sure you typed the name correctly and that it is supported by your device operating system.

- If this is a custom font, be sure to load it with Font.loadAsync.
- node_modules/expo/build/environment/muteWarnings.fx.js:27:24 in error
- ... 33 more stack frames from framework internals

fontFamily "ionicons" is not a system font and has not been loaded through Font.loadAsync.

- If you intended to use a system font, make sure you typed the name correctly and that it is supported by your device operating system.

- If this is a custom font, be sure to load it with Font.loadAsync.
- node_modules/expo/build/environment/muteWarnings.fx.js:27:24 in error
- ... 33 more stack frames from framework internals

fontFamily "ionicons" is not a system font and has not been loaded through Font.loadAsync.

- If you intended to use a system font, make sure you typed the name correctly and that it is supported by your device operating system.

- If this is a custom font, be sure to load it with Font.loadAsync.
- node_modules/expo/build/environment/muteWarnings.fx.js:27:24 in error
- ... 33 more stack frames from framework internals

fontFamily "ionicons" is not a system font and has not been loaded through Font.loadAsync.

- If you intended to use a system font, make sure you typed the name correctly and that it is supported by your device operating system.

- If this is a custom font, be sure to load it with Font.loadAsync.
- node_modules/expo/build/environment/muteWarnings.fx.js:27:24 in error
- ... 33 more stack frames from framework internals

fontFamily "ionicons" is not a system font and has not been loaded through Font.loadAsync.

- If you intended to use a system font, make sure you typed the name correctly and that it is supported by your device operating system.

- If this is a custom font, be sure to load it with Font.loadAsync.
- node_modules/expo/build/environment/muteWarnings.fx.js:27:24 in error
- ... 33 more stack frames from framework internals

fontFamily "ionicons" is not a system font and has not been loaded through Font.loadAsync.

- If you intended to use a system font, make sure you typed the name correctly and that it is supported by your device operating system.

- If this is a custom font, be sure to load it with Font.loadAsync.
- node_modules/expo/build/environment/muteWarnings.fx.js:27:24 in error
- ... 33 more stack frames from framework internals

fontFamily "ionicons" is not a system font and has not been loaded through Font.loadAsync.

- If you intended to use a system font, make sure you typed the name correctly and that it is supported by your device operating system.

- If this is a custom font, be sure to load it with Font.loadAsync.
- node_modules/expo/build/environment/muteWarnings.fx.js:27:24 in error
- ... 33 more stack frames from framework internals

fontFamily "ionicons" is not a system font and has not been loaded through Font.loadAsync.

- If you intended to use a system font, make sure you typed the name correctly and that it is supported by your device operating system.

- If this is a custom font, be sure to load it with Font.loadAsync.
- node_modules/expo/build/environment/muteWarnings.fx.js:27:24 in error
- ... 33 more stack frames from framework internals

fontFamily "ionicons" is not a system font and has not been loaded through Font.loadAsync.

- If you intended to use a system font, make sure you typed the name correctly and that it is supported by your device operating system.

- If this is a custom font, be sure to load it with Font.loadAsync.
- node_modules/expo/build/environment/muteWarnings.fx.js:27:24 in error
- ... 33 more stack frames from framework internals

fontFamily "ionicons" is not a system font and has not been loaded through Font.loadAsync.

- If you intended to use a system font, make sure you typed the name correctly and that it is supported by your device operating system.

- If this is a custom font, be sure to load it with Font.loadAsync.
- node_modules/expo/build/environment/muteWarnings.fx.js:27:24 in error
- ... 33 more stack frames from framework internals

fontFamily "ionicons" is not a system font and has not been loaded through Font.loadAsync.

- If you intended to use a system font, make sure you typed the name correctly and that it is supported by your device operating system.

- If this is a custom font, be sure to load it with Font.loadAsync.
- node_modules/expo/build/environment/muteWarnings.fx.js:27:24 in error
- ... 33 more stack frames from framework internals

fontFamily "ionicons" is not a system font and has not been loaded through Font.loadAsync.

- If you intended to use a system font, make sure you typed the name correctly and that it is supported by your device operating system.

- If this is a custom font, be sure to load it with Font.loadAsync.
- node_modules/expo/build/environment/muteWarnings.fx.js:27:24 in error
- ... 33 more stack frames from framework internals

fontFamily "ionicons" is not a system font and has not been loaded through Font.loadAsync.

- If you intended to use a system font, make sure you typed the name correctly and that it is supported by your device operating system.

- If this is a custom font, be sure to load it with Font.loadAsync.
- node_modules/expo/build/environment/muteWarnings.fx.js:27:24 in error
- ... 33 more stack frames from framework internals

fontFamily "ionicons" is not a system font and has not been loaded through Font.loadAsync.

- If you intended to use a system font, make sure you typed the name correctly and that it is supported by your device operating system.

- If this is a custom font, be sure to load it with Font.loadAsync.
- node_modules/expo/build/environment/muteWarnings.fx.js:27:24 in error
- ... 33 more stack frames from framework internals

fontFamily "ionicons" is not a system font and has not been loaded through Font.loadAsync.

- If you intended to use a system font, make sure you typed the name correctly and that it is supported by your device operating system.

- If this is a custom font, be sure to load it with Font.loadAsync.
- node_modules/expo/build/environment/muteWarnings.fx.js:27:24 in error
- ... 33 more stack frames from framework internals

IOS Keyboard blinking problem on v-model

Hello, I have the problems with IOS input, when I entering the text which have the v-model it is blinking and slows down the input. There is the screen video. I just used original package and added v-model.

IMG_6517.MP4

Anyone do you have a solution or any ideas? I have used this project as the core, and it is on production of App Store.

cannot run app

I was able to successfully clone your code to a Windows 10 machine which has Expo CLI and Vue Native CLI installed. Using Git Bash, and being in the correct directory where the project files have been cloned, running npm start results in errors and the app does not start. Below is the log file output. What needs to be changed to get it to work?

0 info it worked if it ends with ok
1 verbose cli [
1 verbose cli   'C:\\Program Files\\nodejs\\node.exe',
1 verbose cli   'C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli   'start'
1 verbose cli ]
2 info using [email protected]
3 info using [email protected]
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle [email protected]~prestart: [email protected]
6 info lifecycle [email protected]~start: [email protected]
7 verbose lifecycle [email protected]~start: unsafe-perm in lifecycle true
8 verbose lifecycle [email protected]~start: PATH: C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;Z:\files\development\vue_native\code\git\KitchenSink-Vue-Native\node_modules\.bin;C:\Users\jason.black\bin;C:\Program Files\Git\mingw64\bin;C:\Program Files\Git\usr\local\bin;C:\Program Files\Git\usr\bin;C:\Program Files\Git\usr\bin;C:\Program Files\Git\mingw64\bin;C:\Program Files\Git\usr\bin;C:\Users\jason.black\bin;C:\Python27;C:\Python27\Scripts;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Windows\System32\OpenSSH;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Program Files (x86)\Microsoft SQL Server\150\DTS\Binn;C:\Program Files\Microsoft SQL Server\Client SDK\ODBC\130\Tools\Binn;C:\Program Files (x86)\Microsoft SQL Server\140\Tools\Binn;C:\Program Files\Microsoft SQL Server\140\Tools\Binn;C:\Program Files\Microsoft SQL Server\140\DTS\Binn;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files\Intel\Intel(R) Management Engine Components\DAL;C:\HashiCorp\Vagrant\bin;C:\Program Files\Git\cmd;C:\xampp\php;C:\ProgramData\ComposerSetup\bin;C:\Program Files\nodejs;C:\ProgramData\chocolatey\bin;C:\Users\jason.black\AppData\Local\Microsoft\WindowsApps;C:\Users\jason.black\AppData\Local\atom\bin;C:\Users\jason.black\AppData\Roaming\Composer\vendor\bin;C:\Users\jason.black\AppData\Roaming\npm;C:\Program Files\Git\usr\bin\vendor_perl;C:\Program Files\Git\usr\bin\core_perl
9 verbose lifecycle [email protected]~start: CWD: Z:\files\development\vue_native\code\git\KitchenSink-Vue-Native
10 silly lifecycle [email protected]~start: Args: [ '/d /s /c', 'expo start' ]
11 silly lifecycle [email protected]~start: Returned: code: 1  signal: null
12 info lifecycle [email protected]~start: Failed to exec start script
13 verbose stack Error: [email protected] start: `expo start`
13 verbose stack Exit status 1
13 verbose stack     at EventEmitter.<anonymous> (C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\index.js:332:16)
13 verbose stack     at EventEmitter.emit (events.js:210:5)
13 verbose stack     at ChildProcess.<anonymous> (C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\lib\spawn.js:55:14)
13 verbose stack     at ChildProcess.emit (events.js:210:5)
13 verbose stack     at maybeClose (internal/child_process.js:1021:16)
13 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:283:5)
14 verbose pkgid [email protected]
15 verbose cwd Z:\files\development\vue_native\code\git\KitchenSink-Vue-Native
16 verbose Windows_NT 10.0.17763
17 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "start"
18 verbose node v12.13.0
19 verbose npm  v6.12.0
20 error code ELIFECYCLE
21 error errno 1
22 error [email protected] start: `expo start`
22 error Exit status 1
23 error Failed at the [email protected] start script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]

Warning: Failed prop type: Invalid prop `style` of type `array` supplied to `StyleProvider`, expected `object`.

Hello. Why are StyleProvider not taking the theme, and throwing warning "Failed prop type: Invalid prop style of type array supplied to StyleProvider, expected object."

<template>
<nb-style-provider v-bind:style="getTheme(material)">
<nb-container>
<nb-text>Contact</nb-text>
</nb-container>
</nb-style-provider>
</template>
<script>
import Vue from "vue-native-core";
import {VueNativeBase} from "native-base";
import getTheme from './native-base-theme/components';
import material from './native-base-theme/variables/material';

Vue.use(VueNativeBase);
export default {
data: function() {
return {
getTheme: getTheme,
material: material,
};
},
};
</script>

Trying to add theme to project [undefined isIphoneX]

I'm trying to add the theme using nb-style-provider but I haven't being able to make it work.

<nb-style-provider :style="getTheme(platform)">
...

I haven't changed anything I just ran node node_modules/native-base/ejectTheme.js and tried to import it

Can you please update this repo?

It has a lot of errors, first expo cli is outdated, then metro-config has an error in blacklist.js, then the front is outdated and not working.

This repo is useless and I am done fixing all the issues.

Error on expo

I need help guys. I have not been able to get past this error after cloning your App.

Nativebase theming configuration

Hi @sanketsahusoft i have been following the progress of the project and have been able to create an app of the cli project. It would be nice if you can include the theming configuration just like you did with fonts in this kitchen sink project. would be nice to be able to try the material theme on iOS and vice versa

removing class="container" caused bug

from here KitchenSink-Vue-Native/src/boot/setup.vue

Plot 🗡
i try to remove the class, but when i run the app, i got white screen, when i add the class back, everything back to normal. hm

nb- tags

I dont understand. Which import supports that nb- tags that you are using...?? I copy paste some code to my project and i get a Render Error although i have the same package.json

Cannot run as-is

I've cloned this repo, ran npm install, ran npm start, and typed a to load up on my connected android device. I get warnings in the console as such:

3:23:33 PM: Warning: 'react' peer dependency missing. Run `npm ls` in C:\Users\laplante\Documents\KitchenSink-Vue-Native-master to see full warning.
3:23:33 PM: Warning: 'react-native' peer dependency missing. Run `npm ls` in C:\Users\laplante\Documents\KitchenSink-Vue-Native-master to see full warning.
3:23:33 PM: Warning: 'vue-native-core' peer dependency missing. Run `npm ls` in C:\Users\laplante\Documents\KitchenSink-Vue-Native-master to see full warning.
3:23:33 PM: Warning: 'vue-native-helper' peer dependency missing. Run `npm ls` in C:\Users\laplante\Documents\KitchenSink-Vue-Native-master to see full warning.
3:23:33 PM: Warning: 'vue-native-scripts' peer dependency missing. Run `npm ls` in C:\Users\laplante\Documents\KitchenSink-Vue-Native-master to see full warning.
3:23:33 PM: If there is an issue running your project, please run `npm install` in C:\Users\laplante\Documents\KitchenSink-Vue-Native-master and restart.

On the android device, a blue screen appears saying
Something went wrong.
Sorry about that. You can go back to Expo home or try to reload the Experience.

I'm using
NPM version 6.4.1
react-native-cli version 2.0.1

'expo' is not recognized as an internal or external command,

operable program or batch file.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] start: expo start
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\Manish Kini\AppData\Roaming\npm-cache_logs\2020-01-12T05_15_25_455Z-debug.log

newbie question: cannot install

here's what I got after I cloned your repo, when I ran yarn...

yarn
yarn install v1.7.0
(node:45495) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
[1/4] 🔍  Resolving packages...
[2/4] 🚚  Fetching packages...
info @expo/[email protected]: The CPU architecture "x64" is incompatible with this module.
info "@expo/[email protected]" is an optional dependency and failed compatibility check. Excluding it from installation.
info @expo/[email protected]: The platform "darwin" is incompatible with this module.
info "@expo/[email protected]" is an optional dependency and failed compatibility check. Excluding it from installation.
info @expo/[email protected]: The CPU architecture "x64" is incompatible with this module.
info @expo/[email protected]: The platform "darwin" is incompatible with this module.
info "@expo/[email protected]" is an optional dependency and failed compatibility check. Excluding it from installation.
info @expo/[email protected]: The platform "darwin" is incompatible with this module.
info "@expo/[email protected]" is an optional dependency and failed compatibility check. Excluding it from installation.
info @expo/[email protected]: The CPU architecture "x64" is incompatible with this module.
info @expo/[email protected]: The platform "darwin" is incompatible with this module.
info "@expo/[email protected]" is an optional dependency and failed compatibility check. Excluding it from installation.
info @expo/[email protected]: The CPU architecture "x64" is incompatible with this module.
info @expo/[email protected]: The platform "darwin" is incompatible with this module.
info "@expo/[email protected]" is an optional dependency and failed compatibility check. Excluding it from installation.
info @expo/[email protected]: The CPU architecture "x64" is incompatible with this module.
info @expo/[email protected]: The platform "darwin" is incompatible with this module.
info "@expo/[email protected]" is an optional dependency and failed compatibility check. Excluding it from installation.
info @expo/[email protected]: The platform "darwin" is incompatible with this module.
info "@expo/[email protected]" is an optional dependency and failed compatibility check. Excluding it from installation.
info @expo/[email protected]: The platform "darwin" is incompatible with this module.
info "@expo/[email protected]" is an optional dependency and failed compatibility check. Excluding it from installation.
info @expo/[email protected]: The CPU architecture "x64" is incompatible with this module.
info @expo/[email protected]: The platform "darwin" is incompatible with this module.
info "@expo/[email protected]" is an optional dependency and failed compatibility check. Excluding it from installation.
[3/4] 🔗  Linking dependencies...
warning "react-native > metro > @babel/[email protected]" has incorrect peer dependency "@babel/[email protected]".
warning " > [email protected]" has incorrect peer dependency "[email protected]".
warning " > [email protected]" has incorrect peer dependency "[email protected]".
warning "jest-expo > [email protected]" has unmet peer dependency "babel-core@^6.0.0 || ^7.0.0-0".
[4/4] 📃  Building fresh packages...
[1/2] ⠄ fsevents
warning Error running install script for optional dependency: "/Users/bobwalsh/KitchenSink-Vue-Native/node_modules/fsevents: Command failed.
Exit code: 1
Command: node install
Arguments:
Directory: /Users/bobwalsh/KitchenSink-Vue-Native/node_modules/fsevents
Output:
node-pre-gyp info it worked if it ends with ok
node-pre-gyp info using [email protected]
node-pre-gyp info using [email protected] | darwin | x64
node-pre-gyp info check checked for \"/Users/bobwalsh/KitchenSink-Vue-Native/node_modules/fsevents/lib/binding/Release/node-v64-darwin-x64/fse.node\" (not found)
node-pre-gyp http GET https://fsevents-binaries.s3-us-west-2.amazonaws.com/v1.1.3/fse-v1.1.3-node-v64-darwin-x64.tar.gz
node-pre-gyp http 404 https://fsevents-binaries.s3-us-west-2.amazonaws.com/v1.1.3/fse-v1.1.3-node-v64-darwin-x64.tar.gz
node-pre-gyp ERR! Tried to download(404): https://fsevents-binaries.s3-us-west-2.amazonaws.com/v1.1.3/fse-v1.1.3-node-v64-darwin-x64.tar.gz
node-pre-gyp ERR! Pre-built binaries not found for [email protected] and [email protected] (node-v64 ABI, unknown) (falling back to source compile with node-gyp)
node-pre-gyp http 404 status code downloading tarball https://fsevents-binaries.s3-us-west-2.amazonaws.com/v1.1.3/fse-v1.1.3-node-v64-darwin-x64.tar.gz
node-pre-gyp ERR! Tried to download(undefined): https://fsevents-binaries.s3-us-west-2.amazonaws.com/v1.1.3/fse-v1.1.3-node-v64-darwin-x64.tar.gz
node-pre-gyp ERR! Pre-built binaries not found for [email protected] and [email protected] (node-v64 ABI, unknown) (falling back to source compile with node-gyp)
node-pre-gyp http Connection closed while downloading tarball file
gypgyp  info infoit worked if it ends with it worked if it ends with ok
 ok
gypgyp  infoinfo  usingusing [email protected]
 [email protected]
gypgyp  infoinfo  usingusing [email protected] | darwin | x64
 [email protected] | darwin | x64
gypgyp info  okinfo
 ok
gyp info it worked if it ends with ok
gypgyp info  using [email protected]
infogyp  info it worked if it ends withusing [email protected] | darwin | x64
 ok
gyp info using [email protected]
gyp info using [email protected] | darwin | x64
gypgyp  infoinfo  spawnspawn /usr/bin/python
 /usr/bin/python
gyp gypinfo  infospawn args  [ '/usr/local/Cellar/node/10.2.1/libexec/lib/node_modules/npm/node_modules/node-gyp/gyp/gyp_main.py',
spawn argsgyp [ '/usr/local/Cellar/node/10.2.1/libexec/lib/node_modules/npm/node_modules/node-gyp/gyp/gyp_main.py',
 gypinfo  spawn argsinfo   'binding.gyp',
 spawn argsgyp   'binding.gyp',
 gypinfo  infospawn args   '-f',
 gypspawn args    '-f',
info spawn args   'make',
gyp info spawn args   '-I',
gypgyp info  infospawn args    '/Users/bobwalsh/KitchenSink-Vue-Native/node_modules/fsevents/build/config.gypi',
spawn argsgyp   'make',
 gypinfo  infospawn args    '-I',
spawn argsgyp   '-I',
 gypinfo  infospawn args    '/usr/local/Cellar/node/10.2.1/libexec/lib/node_modules/npm/node_modules/node-gyp/addon.gypi',
spawn argsgyp   '/Users/bobwalsh/KitchenSink-Vue-Native/node_modules/fsevents/build/config.gypi',
 gypinfo  infospawn args    '-I',
spawn argsgyp   '-I',
 gypinfo  infospawn args    '/Users/bobwalsh/.node-gyp/10.2.1/include/node/common.gypi',
spawn argsgyp   '/usr/local/Cellar/node/10.2.1/libexec/lib/node_modules/npm/node_modules/node-gyp/addon.gypi',
 gyp info spawn args   '-I',
gyp info spawn args   '/Users/bobwalsh/.node-gyp/10.2.1/include/node/common.gypi',
gyp info spawn args   '-Dlibrary=shared_library',
gyp info spawn args   '-Dvisibility=default',
gyp info spawn args   '-Dnode_root_dir=/Users/bobwalsh/.node-gyp/10.2.1',
gyp info spawn args   '-Dnode_gyp_dir=/usr/local/Cellar/node/10.2.1/libexec/lib/node_modules/npm/node_modules/node-gyp',
gyp info spawn argsinfo   '-Dnode_lib_file=/Users/bobwalsh/.node-gyp/10.2.1/<(target_arch)/node.lib',
gyp info  spawn args   '-Dmodule_root_dir=/Users/bobwalsh/KitchenSink-Vue-Native/node_modules/fsevents',
spawn argsgyp   '-Dlibrary=shared_library',
gyp  infoinfo  spawn argsspawn args   '-Dnode_engine=v8',
   '-Dvisibility=default',
gypgyp  infoinfo  spawn argsspawn args   '--depth=.',
   '-Dnode_root_dir=/Users/bobwalsh/.node-gyp/10.2.1',
gypgyp  infoinfo  spawn argsspawn args   '--no-parallel',
   '-Dnode_gyp_dir=/usr/local/Cellar/node/10.2.1/libexec/lib/node_modules/npm/node_modules/node-gyp',
gypgyp  infoinfo  spawn argsspawn args   '--generator-output',
   '-Dnode_lib_file=/Users/bobwalsh/.node-gyp/10.2.1/<(target_arch)/node.lib',
gypgyp  infoinfo  spawn argsspawn args   '-Dmodule_root_dir=/Users/bobwalsh/KitchenSink-Vue-Native/node_modules/fsevents',
gyp   'build',
 gypinfo  spawn argsinfo   '-Dnode_engine=v8',
 gypspawn args    '-Goutput_dir=.' ]
info spawn args   '--depth=.',
gyp info spawn args   '--no-parallel',
gyp info spawn args   '--generator-output',
gyp info spawn args   'build',
gyp info spawn args   '-Goutput_dir=.' ]
gypgyp  infoinfo  okok

gypgyp info it worked if it ends with ok
 info it worked if it ends with ok
gyp info using [email protected]
gyp info using [email protected] | darwin | x64
gyp info using [email protected]
gyp info using [email protected] | darwin | x64
gypgyp info  spawn make
info spawn make
gyp infogyp  spawn argsinfo [ 'BUILDTYPE=Release', '-C', 'build' ]
 spawn args [ 'BUILDTYPE=Release', '-C', 'build' ]
  SOLINK_MODULE(target) Release/.node
  SOLINK_MODULE(target) Release/.node
  CXX(target) Release/obj.target/fse/fsevents.o
  CXX(target) Release/obj.target/fse/fsevents.o
In file included from ../fsevents.cc:85:
In file included from ../fsevents.cc:../src/methods.cc:8514:
:12: warning: 'Call' is deprecated [-Wdeprecated-declarations]
../src/methods.cc:14:12: warning: 'Call' is deprecated [-Wdeprecated-declarations]
  handler->Call(3, argv);  handler->Call(3, argv);
           ^

           ^
../../nan/nan.h:1617:3: note: 'Call' has been explicitly marked deprecated here../../nan/nan.h:
1617:3: note: 'Call' has been explicitly marked deprecated here
  NAN_DEPRECATED inline v8::Local<v8::Value>
  ^
  NAN_DEPRECATED inline v8::Local<v8::Value>
  ^
../../nan/nan.h:../../nan/nan.h98::9840::40 :note : noteexpanded from macro 'NAN_DEPRECATED':
expanded from macro 'NAN_DEPRECATED'
# define NAN_DEPRECATED __attribute__((deprecated))
                                       ^
# define NAN_DEPRECATED __attribute__((deprecated))
                                       ^
1 warning generated.
1 warning generated.
rm: ./Release/.deps/Release/obj.target/fse/fsevents.o.d.raw: No such file or directory
make: *** [Release/obj.target/fse/fsevents.o] Error 1
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/usr/local/Cellar/node/10.2.1/libexec/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:258:23)
gyp ERR! stack     at ChildProcess.emit (events.js:182:13)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:237:12)
gyp ERR! System Darwin 17.6.0
gyp ERR! command \"/usr/local/Cellar/node/10.2.1/bin/node\" \"/usr/local/Cellar/node/10.2.1/libexec/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js\" \"build\" \"--fallback-to-build\" \"--module=/Users/bobwalsh/KitchenSink-Vue-Native/node_modules/fsevents/lib/binding/Release/node-v64-darwin-x64/fse.node\" \"--module_name=fse\" \"--module_path=/Users/bobwalsh/KitchenSink-Vue-Native/node_modules/fsevents/lib/binding/Release/node-v64-darwin-x64\"
gyp ERR! cwd /Users/bobwalsh/KitchenSink-Vue-Native/node_modules/fsevents
gyp ERR! node -v v10.2.1
gyp ERR! node-gyp -v v3.6.2
gyp ERR! not ok
  SOLINK_MODULE(target) Release/fse.node
node-pre-gyp ERR! build error
node-pre-gyp ERR! stack Error: Failed to execute 'node-gyp build --fallback-to-build --module=/Users/bobwalsh/KitchenSink-Vue-Native/node_modules/fsevents/lib/binding/Release/node-v64-darwin-x64/fse.node --module_name=fse --module_path=/Users/bobwalsh/KitchenSink-Vue-Native/node_modules/fsevents/lib/binding/Release/node-v64-darwin-x64' (1)
node-pre-gyp ERR! stack     at ChildProcess.<anonymous> (/Users/bobwalsh/KitchenSink-Vue-Native/node_modules/fsevents/node_modules/node-pre-gyp/lib/util/compile.js:83:29)
node-pre-gyp ERR! stack     at ChildProcess.emit (events.js:182:13)
node-pre-gyp ERR! stack     at maybeClose (internal/child_process.js:961:16)
node-pre-gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:248:5)
node-pre-gyp ERR! System Darwin 17.6.0
node-pre-gyp ERR! command \"/usr/local/Cellar/node/10.2.1/bin/node\" \"/Users/bobwalsh/KitchenSink-Vue-Native/node_modules/fsevents/node_modules/node-pre-gyp/bin/node-pre-gyp\" \"install\" \"--fallback-to-build\"
node-pre-gyp ERR! cwd /Users/bobwalsh/KitchenSink-Vue-Native/node_modules/fsevents
node-pre-gyp ERR! node -v v10.2.1
node-pre-gyp ERR! node-pre-gyp -v v0.6.39
node-pre-gyp ERR! not ok
Failed to execute 'node-gyp build --fallback-to-build --module=/Users/bobwalsh/KitchenSink-Vue-Native/node_modules/fsevents/lib/binding/Release/node-v64-darwin-x64/fse.node --module_name=fse --module_path=/Users/bobwalsh/KitchenSink-Vue-Native/node_modules/fsevents/lib/binding/Release/node-v64-darwin-x64' (1)
  COPY /Users/bobwalsh/KitchenSink-Vue-Native/node_modules/fsevents/lib/binding/Release/node-v64-darwin-x64/fse.node
  TOUCH Release/obj.target/action_after_build.stamp
gyp info ok"
✨  Done in 69.61s.

and when I started it:

Bobs-iMac-3:KitchenSink-Vue-Native bobwalsh$ npm start

> [email protected] start /Users/bobwalsh/KitchenSink-Vue-Native
> react-native-scripts start

11:37:59 AM: Unable to start server
See https://git.io/v5vcn for more information, either install watchman or run the following snippet:
  sudo sysctl -w kern.maxfiles=5242880
  sudo sysctl -w kern.maxfilesperproc=524288

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] start: `react-native-scripts start`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/bobwalsh/.npm/_logs/2018-06-18T18_37_59_196Z-debug.log

warning in expo

in expo, I got this warning

Picker only 1

In the burger menu, I see picker "9 types" at the inscription, but when I open it, I see only one picker in the list