From c08265a2a92276abba3d388f06a911bebf869d80 Mon Sep 17 00:00:00 2001 From: Nick Novitski Date: Thu, 28 Mar 2019 17:13:31 -0700 Subject: [PATCH] [docs] Fix broken directory links When Python's SimpleHTTPServer receives a request that matches a directory with no index.html file, it gives a succesful response with an html list of the directory's other contents. This does not match production behavior and was hiding several problems. --- .circleci/config.yml | 2 +- docs/package.json | 3 +- .../versions/unversioned/expokit/eject.md | 2 +- .../unversioned/guides/using-custom-fonts.md | 2 +- docs/pages/versions/unversioned/index.md | 4 +- .../versions/unversioned/introduction/faq.md | 4 +- .../introduction/project-lifecycle.md | 2 +- .../unversioned/sdk/document-picker.md | 2 +- .../versions/unversioned/sdk/map-view.md | 2 +- .../unversioned/workflow/glossary-of-terms.md | 2 +- .../unversioned/workflow/up-and-running.md | 2 +- docs/pages/versions/v32.0.0/expokit/eject.md | 2 +- .../v32.0.0/guides/using-custom-fonts.md | 2 +- docs/pages/versions/v32.0.0/index.md | 4 +- .../versions/v32.0.0/introduction/faq.md | 4 +- .../v32.0.0/introduction/project-lifecycle.md | 4 +- .../versions/v32.0.0/sdk/document-picker.md | 2 +- docs/pages/versions/v32.0.0/sdk/map-view.md | 2 +- .../v32.0.0/workflow/glossary-of-terms.md | 2 +- .../v32.0.0/workflow/up-and-running.md | 2 +- docs/yarn.lock | 122 +++++++++++++++++- 21 files changed, 145 insertions(+), 28 deletions(-) diff --git a/.circleci/config.yml b/.circleci/config.yml index 17239b32ab2514..1ab25dbe34be93 100644 --- a/.circleci/config.yml +++ b/.circleci/config.yml @@ -479,7 +479,7 @@ jobs: working_directory: docs - run: working_directory: docs - command: nix run expo.python --command yarn run export-server + command: yarn run export-server background: true - run: working_directory: docs diff --git a/docs/package.json b/docs/package.json index 50a823a3a68c1c..41c1175c8042ca 100644 --- a/docs/package.json +++ b/docs/package.json @@ -6,7 +6,7 @@ "dev": "node server.js", "build": "cross-env NODE_OPTIONS=--max-old-space-size=8192 next build", "export": "yarn run build && next export", - "export-server": "cd out && python -m SimpleHTTPServer 8000", + "export-server": "http-server out -p 8000", "import-react-native-docs": "node ./scripts/import-react-native-docs.js", "test-links": "blc --recursive --exclude-external --filter-level 2" }, @@ -33,6 +33,7 @@ }, "devDependencies": { "broken-link-checker": "^0.7.8", + "http-server": "^0.11.1", "minimist": "^1.2.0", "prettier": "^1.15.3" } diff --git a/docs/pages/versions/unversioned/expokit/eject.md b/docs/pages/versions/unversioned/expokit/eject.md index 5f6190c82b54bb..0e1ec55febf590 100644 --- a/docs/pages/versions/unversioned/expokit/eject.md +++ b/docs/pages/versions/unversioned/expokit/eject.md @@ -20,7 +20,7 @@ We call this "ejecting" because you still depend on the Expo SDK, but your proje ### You might want to eject if: -- Your Expo project needs a native module that Expo doesn't currently support. We're always expanding the [Expo SDK](../../sdk/), so we hope this is never the case. But it happens, especially if your app has very specific and uncommon native demands. +- Your Expo project needs a native module that Expo doesn't currently support. We're always expanding the [Expo SDK](../../sdk/overview/), so we hope this is never the case. But it happens, especially if your app has very specific and uncommon native demands. ### You should not eject if: diff --git a/docs/pages/versions/unversioned/guides/using-custom-fonts.md b/docs/pages/versions/unversioned/guides/using-custom-fonts.md index f4b453c136486b..03c36a541db335 100644 --- a/docs/pages/versions/unversioned/guides/using-custom-fonts.md +++ b/docs/pages/versions/unversioned/guides/using-custom-fonts.md @@ -36,7 +36,7 @@ Take the Open Sans zipfile that you downloaded, extract it and copy `OpenSans-Bo ## Loading the font in your app -To load and use fonts we will use the [Expo SDK](../../sdk/), which comes pre-installed when you create a new Expo project, but if for some reason you don't have it, you can install with `npm install --save expo` in your project directory. Add the following `import` in your application code: +To load and use fonts we will use the [Expo SDK](../../sdk/overview/), which comes pre-installed when you create a new Expo project, but if for some reason you don't have it, you can install with `npm install --save expo` in your project directory. Add the following `import` in your application code: ```javascript import { Font } from 'expo'; diff --git a/docs/pages/versions/unversioned/index.md b/docs/pages/versions/unversioned/index.md index 2de6f52dc74964..afd63a7f2e56ab 100644 --- a/docs/pages/versions/unversioned/index.md +++ b/docs/pages/versions/unversioned/index.md @@ -6,7 +6,7 @@ title: Getting to know Expo This is the documentation for [Expo](http://expo.io). Expo is a set of tools, libraries and services you can use to build native iOS and Android apps faster than ever before. -There are two ways to build a project with Expo, we call these workflows: you can use the "managed" workflow or the "bare" workflow. With the "managed" workflow, you only write JavaScript and lean on the [Expo SDK](sdk/) to give you access to your device capabilities and the Expo services to handle the heavy lifting of building your app binary and uploading it to the store, all without you touching Xcode or Android Studio. With the "bare" workflow, we also speed up your development with the [Expo SDK](sdk/) and React Native, and you have full control over your iOS and Android projects. +There are two ways to build a project with Expo, we call these workflows: you can use the "managed" workflow or the "bare" workflow. With the "managed" workflow, you only write JavaScript and lean on the [Expo SDK](sdk/overview/) to give you access to your device capabilities and the Expo services to handle the heavy lifting of building your app binary and uploading it to the store, all without you touching Xcode or Android Studio. With the "bare" workflow, we also speed up your development with the [Expo SDK](sdk/overview/) and React Native, and you have full control over your iOS and Android projects. ## More about the Expo SDK @@ -25,4 +25,4 @@ Expo also provides UI components to handle a variety of use-cases that almost al - Make your first project by following the [Up and Running](workflow/up-and-running/) guide. - If you're not already familiar with React and React Native, you can bootstrap your knowledge with [React Native Express](http://www.reactnativeexpress.com/). - For hands-on React Native projects from beginner to advanced, check out [Fullstack React Native](https://www.fullstackreact.com/react-native/), a (paid) book by the author of React Native Express. -- Join our [Community](introduction/community/) and let us know what you're working on! \ No newline at end of file +- Join our [Community](introduction/community/) and let us know what you're working on! diff --git a/docs/pages/versions/unversioned/introduction/faq.md b/docs/pages/versions/unversioned/introduction/faq.md index 2a4fe6b78bda33..12e84051c40edf 100644 --- a/docs/pages/versions/unversioned/introduction/faq.md +++ b/docs/pages/versions/unversioned/introduction/faq.md @@ -64,9 +64,9 @@ TL;DR you can do it, but most people never need to. Standard Expo projects don't support custom native code, including third-party libraries which require custom native components. In an Expo project, you only write pure JS. Expo is designed this way on purpose and we think it's better this way. -In [our SDK](../../sdk/), we give you a large set of commonly desired, high-quality native modules. We recommend doing as much in JS as possible, since it can immediately deploy to all your users and work across both platforms, and will always continue to benefit from Expo SDK updates. Especially in the case of UI components, there is pretty much always a better option written in JS. +In [our SDK](../../sdk/overview/), we give you a large set of commonly desired, high-quality native modules. We recommend doing as much in JS as possible, since it can immediately deploy to all your users and work across both platforms, and will always continue to benefit from Expo SDK updates. Especially in the case of UI components, there is pretty much always a better option written in JS. -However, if you need something very custom--like on-the-fly video processing or low level control over the Bluetooth radio to do a firmware update--we do have early/alpha support for [using Expo in native Xcode and Android Studio projects](../../expokit/). +However, if you need something very custom--like on-the-fly video processing or low level control over the Bluetooth radio to do a firmware update--we do have early/alpha support for [using Expo in native Xcode and Android Studio projects](../../expokit/overview/). ## Is Expo similar to React for web development? diff --git a/docs/pages/versions/unversioned/introduction/project-lifecycle.md b/docs/pages/versions/unversioned/introduction/project-lifecycle.md index d00514d4e67fbd..aea562ee7fb180 100644 --- a/docs/pages/versions/unversioned/introduction/project-lifecycle.md +++ b/docs/pages/versions/unversioned/introduction/project-lifecycle.md @@ -32,7 +32,7 @@ On iOS, you'll need to use Apple TestFlight to share your app with others. You can continue making changes locally without disrupting your users. Any time you **Publish** changes to your app, your new version becomes available immediately to anybody with the link. -We frequently release updates to the [Expo SDK](../../sdk/). Each update includes instructions for how to upgrade your project. If you decide to update to a newer version of our SDK, copies of the older version will continue to work fine. Users will download the newest copy that their client supports. +We frequently release updates to the [Expo SDK](../../sdk/overview/). Each update includes instructions for how to upgrade your project. If you decide to update to a newer version of our SDK, copies of the older version will continue to work fine. Users will download the newest copy that their client supports. ## Deploying to the Apple App Store and Google Play diff --git a/docs/pages/versions/unversioned/sdk/document-picker.md b/docs/pages/versions/unversioned/sdk/document-picker.md index c4075bf7651a2e..8b35a645f0c476 100644 --- a/docs/pages/versions/unversioned/sdk/document-picker.md +++ b/docs/pages/versions/unversioned/sdk/document-picker.md @@ -39,7 +39,7 @@ Otherwise, returns `{ type: 'success', uri, name, size }` where `uri` is a URI t ## iOS configuration -On iOS, for [standalone apps](../../distribution/building-standalone-apps/) and [ExpoKit](../../expokit/) projects, the DocumentPicker module requires the iCloud entitlement to work properly. You need to set the `usesIcloudStorage` key to `true` in your `app.json` file as specified [here](../../workflow/configuration/#ios). +On iOS, for [standalone apps](../../distribution/building-standalone-apps/) and [ExpoKit](../../expokit/overview/) projects, the DocumentPicker module requires the iCloud entitlement to work properly. You need to set the `usesIcloudStorage` key to `true` in your `app.json` file as specified [here](../../workflow/configuration/#ios). ### iCloud Application Service diff --git a/docs/pages/versions/unversioned/sdk/map-view.md b/docs/pages/versions/unversioned/sdk/map-view.md index 243b065a824057..1f8dd0a5612e7e 100644 --- a/docs/pages/versions/unversioned/sdk/map-view.md +++ b/docs/pages/versions/unversioned/sdk/map-view.md @@ -51,7 +51,7 @@ Apple Maps should just work with no extra configuration. For Google Maps, you ca ### Deploying Google Maps to ExpoKit for iOS -If you want to add MapView with Google Maps to an [ExpoKit](../../expokit) (ejected) project on iOS, you may need to manually provide a key by calling: +If you want to add MapView with Google Maps to an [ExpoKit](../../expokit/overview/) (ejected) project on iOS, you may need to manually provide a key by calling: ``` [GMSServices provideApiKey:@"your api key"] diff --git a/docs/pages/versions/unversioned/workflow/glossary-of-terms.md b/docs/pages/versions/unversioned/workflow/glossary-of-terms.md index 9a33cd1afdf48f..fda00bf618f10c 100644 --- a/docs/pages/versions/unversioned/workflow/glossary-of-terms.md +++ b/docs/pages/versions/unversioned/workflow/glossary-of-terms.md @@ -43,7 +43,7 @@ Expo Developer Tools is a web browser based UI included in [Expo CLI](#expo-cli) ### Expo SDK -The Expo SDK provides access to device/system functionality such as camera, push notification, contacts, file system, and more. Scroll to the SDK API reference in the documentation navigation to see a full list of APIs and to explore them. [Read more about the Expo SDK](../../sdk/). [Find it on Github](https://github.com/expo/expo-sdk). +The Expo SDK provides access to device/system functionality such as camera, push notification, contacts, file system, and more. Scroll to the SDK API reference in the documentation navigation to see a full list of APIs and to explore them. [Read more about the Expo SDK](../../sdk/overview/). [Find it on Github](https://github.com/expo/expo-sdk). ### ExpoKit diff --git a/docs/pages/versions/unversioned/workflow/up-and-running.md b/docs/pages/versions/unversioned/workflow/up-and-running.md index a728cebe22deab..1b0fa2a12e6b29 100644 --- a/docs/pages/versions/unversioned/workflow/up-and-running.md +++ b/docs/pages/versions/unversioned/workflow/up-and-running.md @@ -67,6 +67,6 @@ You have created a new Expo project, made a change, and seen it update. ### Next Steps - The [Additional Resources](../../introduction/additional-resources/#additional-resources) has a bunch of useful resources for learning. -- Read about the [Expo SDK](../../sdk/) to learn about some useful APIs we provide out of the box. +- Read about the [Expo SDK](../../sdk/overview/) to learn about some useful APIs we provide out of the box. - Read some of our other guides, such as how to implement [Push Notifications](../../guides/push-notifications/#push-notifications), how we can take care of [Assets](../../guides/assets/#all-about-assets) for you, or how to build [Standalone Apps](../../distribution/building-standalone-apps/#building-standalone-apps) you can submit to Apple or Google. - Join us on Slack to get your questions answered. diff --git a/docs/pages/versions/v32.0.0/expokit/eject.md b/docs/pages/versions/v32.0.0/expokit/eject.md index 5f6190c82b54bb..0e1ec55febf590 100644 --- a/docs/pages/versions/v32.0.0/expokit/eject.md +++ b/docs/pages/versions/v32.0.0/expokit/eject.md @@ -20,7 +20,7 @@ We call this "ejecting" because you still depend on the Expo SDK, but your proje ### You might want to eject if: -- Your Expo project needs a native module that Expo doesn't currently support. We're always expanding the [Expo SDK](../../sdk/), so we hope this is never the case. But it happens, especially if your app has very specific and uncommon native demands. +- Your Expo project needs a native module that Expo doesn't currently support. We're always expanding the [Expo SDK](../../sdk/overview/), so we hope this is never the case. But it happens, especially if your app has very specific and uncommon native demands. ### You should not eject if: diff --git a/docs/pages/versions/v32.0.0/guides/using-custom-fonts.md b/docs/pages/versions/v32.0.0/guides/using-custom-fonts.md index f4b453c136486b..03c36a541db335 100644 --- a/docs/pages/versions/v32.0.0/guides/using-custom-fonts.md +++ b/docs/pages/versions/v32.0.0/guides/using-custom-fonts.md @@ -36,7 +36,7 @@ Take the Open Sans zipfile that you downloaded, extract it and copy `OpenSans-Bo ## Loading the font in your app -To load and use fonts we will use the [Expo SDK](../../sdk/), which comes pre-installed when you create a new Expo project, but if for some reason you don't have it, you can install with `npm install --save expo` in your project directory. Add the following `import` in your application code: +To load and use fonts we will use the [Expo SDK](../../sdk/overview/), which comes pre-installed when you create a new Expo project, but if for some reason you don't have it, you can install with `npm install --save expo` in your project directory. Add the following `import` in your application code: ```javascript import { Font } from 'expo'; diff --git a/docs/pages/versions/v32.0.0/index.md b/docs/pages/versions/v32.0.0/index.md index 2de6f52dc74964..afd63a7f2e56ab 100644 --- a/docs/pages/versions/v32.0.0/index.md +++ b/docs/pages/versions/v32.0.0/index.md @@ -6,7 +6,7 @@ title: Getting to know Expo This is the documentation for [Expo](http://expo.io). Expo is a set of tools, libraries and services you can use to build native iOS and Android apps faster than ever before. -There are two ways to build a project with Expo, we call these workflows: you can use the "managed" workflow or the "bare" workflow. With the "managed" workflow, you only write JavaScript and lean on the [Expo SDK](sdk/) to give you access to your device capabilities and the Expo services to handle the heavy lifting of building your app binary and uploading it to the store, all without you touching Xcode or Android Studio. With the "bare" workflow, we also speed up your development with the [Expo SDK](sdk/) and React Native, and you have full control over your iOS and Android projects. +There are two ways to build a project with Expo, we call these workflows: you can use the "managed" workflow or the "bare" workflow. With the "managed" workflow, you only write JavaScript and lean on the [Expo SDK](sdk/overview/) to give you access to your device capabilities and the Expo services to handle the heavy lifting of building your app binary and uploading it to the store, all without you touching Xcode or Android Studio. With the "bare" workflow, we also speed up your development with the [Expo SDK](sdk/overview/) and React Native, and you have full control over your iOS and Android projects. ## More about the Expo SDK @@ -25,4 +25,4 @@ Expo also provides UI components to handle a variety of use-cases that almost al - Make your first project by following the [Up and Running](workflow/up-and-running/) guide. - If you're not already familiar with React and React Native, you can bootstrap your knowledge with [React Native Express](http://www.reactnativeexpress.com/). - For hands-on React Native projects from beginner to advanced, check out [Fullstack React Native](https://www.fullstackreact.com/react-native/), a (paid) book by the author of React Native Express. -- Join our [Community](introduction/community/) and let us know what you're working on! \ No newline at end of file +- Join our [Community](introduction/community/) and let us know what you're working on! diff --git a/docs/pages/versions/v32.0.0/introduction/faq.md b/docs/pages/versions/v32.0.0/introduction/faq.md index 2a4fe6b78bda33..12e84051c40edf 100644 --- a/docs/pages/versions/v32.0.0/introduction/faq.md +++ b/docs/pages/versions/v32.0.0/introduction/faq.md @@ -64,9 +64,9 @@ TL;DR you can do it, but most people never need to. Standard Expo projects don't support custom native code, including third-party libraries which require custom native components. In an Expo project, you only write pure JS. Expo is designed this way on purpose and we think it's better this way. -In [our SDK](../../sdk/), we give you a large set of commonly desired, high-quality native modules. We recommend doing as much in JS as possible, since it can immediately deploy to all your users and work across both platforms, and will always continue to benefit from Expo SDK updates. Especially in the case of UI components, there is pretty much always a better option written in JS. +In [our SDK](../../sdk/overview/), we give you a large set of commonly desired, high-quality native modules. We recommend doing as much in JS as possible, since it can immediately deploy to all your users and work across both platforms, and will always continue to benefit from Expo SDK updates. Especially in the case of UI components, there is pretty much always a better option written in JS. -However, if you need something very custom--like on-the-fly video processing or low level control over the Bluetooth radio to do a firmware update--we do have early/alpha support for [using Expo in native Xcode and Android Studio projects](../../expokit/). +However, if you need something very custom--like on-the-fly video processing or low level control over the Bluetooth radio to do a firmware update--we do have early/alpha support for [using Expo in native Xcode and Android Studio projects](../../expokit/overview/). ## Is Expo similar to React for web development? diff --git a/docs/pages/versions/v32.0.0/introduction/project-lifecycle.md b/docs/pages/versions/v32.0.0/introduction/project-lifecycle.md index d00514d4e67fbd..dc50a6f33d473a 100644 --- a/docs/pages/versions/v32.0.0/introduction/project-lifecycle.md +++ b/docs/pages/versions/v32.0.0/introduction/project-lifecycle.md @@ -32,11 +32,11 @@ On iOS, you'll need to use Apple TestFlight to share your app with others. You can continue making changes locally without disrupting your users. Any time you **Publish** changes to your app, your new version becomes available immediately to anybody with the link. -We frequently release updates to the [Expo SDK](../../sdk/). Each update includes instructions for how to upgrade your project. If you decide to update to a newer version of our SDK, copies of the older version will continue to work fine. Users will download the newest copy that their client supports. +We frequently release updates to the [Expo SDK](../../sdk/overview/). Each update includes instructions for how to upgrade your project. If you decide to update to a newer version of our SDK, copies of the older version will continue to work fine. Users will download the newest copy that their client supports. ## Deploying to the Apple App Store and Google Play -When you're ready to list your app officially on the Apple App Store and Google Play Store, Expo can generate deployment-ready `.ipa` and `.apk` archives which are ready to submit to Apple and Google. We generate them on our servers, so you still don't need any Apple or Google software. See the documentation about [Distributing Apps](../../distribution/app-stores/). +When you're ready to list your app officially on the Apple App Store and Google Play Store, Expo can generate deployment-ready `.ipa` and `.apk` archives which are ready to submit to Apple and Google. We generate them on our servers, so you still don't need any Apple or Google software. See the documentation about [Distributing Apps](../../distribution/introduction/). ## Changing native code diff --git a/docs/pages/versions/v32.0.0/sdk/document-picker.md b/docs/pages/versions/v32.0.0/sdk/document-picker.md index c4075bf7651a2e..8b35a645f0c476 100644 --- a/docs/pages/versions/v32.0.0/sdk/document-picker.md +++ b/docs/pages/versions/v32.0.0/sdk/document-picker.md @@ -39,7 +39,7 @@ Otherwise, returns `{ type: 'success', uri, name, size }` where `uri` is a URI t ## iOS configuration -On iOS, for [standalone apps](../../distribution/building-standalone-apps/) and [ExpoKit](../../expokit/) projects, the DocumentPicker module requires the iCloud entitlement to work properly. You need to set the `usesIcloudStorage` key to `true` in your `app.json` file as specified [here](../../workflow/configuration/#ios). +On iOS, for [standalone apps](../../distribution/building-standalone-apps/) and [ExpoKit](../../expokit/overview/) projects, the DocumentPicker module requires the iCloud entitlement to work properly. You need to set the `usesIcloudStorage` key to `true` in your `app.json` file as specified [here](../../workflow/configuration/#ios). ### iCloud Application Service diff --git a/docs/pages/versions/v32.0.0/sdk/map-view.md b/docs/pages/versions/v32.0.0/sdk/map-view.md index 243b065a824057..1f8dd0a5612e7e 100644 --- a/docs/pages/versions/v32.0.0/sdk/map-view.md +++ b/docs/pages/versions/v32.0.0/sdk/map-view.md @@ -51,7 +51,7 @@ Apple Maps should just work with no extra configuration. For Google Maps, you ca ### Deploying Google Maps to ExpoKit for iOS -If you want to add MapView with Google Maps to an [ExpoKit](../../expokit) (ejected) project on iOS, you may need to manually provide a key by calling: +If you want to add MapView with Google Maps to an [ExpoKit](../../expokit/overview/) (ejected) project on iOS, you may need to manually provide a key by calling: ``` [GMSServices provideApiKey:@"your api key"] diff --git a/docs/pages/versions/v32.0.0/workflow/glossary-of-terms.md b/docs/pages/versions/v32.0.0/workflow/glossary-of-terms.md index 9a33cd1afdf48f..fda00bf618f10c 100644 --- a/docs/pages/versions/v32.0.0/workflow/glossary-of-terms.md +++ b/docs/pages/versions/v32.0.0/workflow/glossary-of-terms.md @@ -43,7 +43,7 @@ Expo Developer Tools is a web browser based UI included in [Expo CLI](#expo-cli) ### Expo SDK -The Expo SDK provides access to device/system functionality such as camera, push notification, contacts, file system, and more. Scroll to the SDK API reference in the documentation navigation to see a full list of APIs and to explore them. [Read more about the Expo SDK](../../sdk/). [Find it on Github](https://github.com/expo/expo-sdk). +The Expo SDK provides access to device/system functionality such as camera, push notification, contacts, file system, and more. Scroll to the SDK API reference in the documentation navigation to see a full list of APIs and to explore them. [Read more about the Expo SDK](../../sdk/overview/). [Find it on Github](https://github.com/expo/expo-sdk). ### ExpoKit diff --git a/docs/pages/versions/v32.0.0/workflow/up-and-running.md b/docs/pages/versions/v32.0.0/workflow/up-and-running.md index a728cebe22deab..1b0fa2a12e6b29 100644 --- a/docs/pages/versions/v32.0.0/workflow/up-and-running.md +++ b/docs/pages/versions/v32.0.0/workflow/up-and-running.md @@ -67,6 +67,6 @@ You have created a new Expo project, made a change, and seen it update. ### Next Steps - The [Additional Resources](../../introduction/additional-resources/#additional-resources) has a bunch of useful resources for learning. -- Read about the [Expo SDK](../../sdk/) to learn about some useful APIs we provide out of the box. +- Read about the [Expo SDK](../../sdk/overview/) to learn about some useful APIs we provide out of the box. - Read some of our other guides, such as how to implement [Push Notifications](../../guides/push-notifications/#push-notifications), how we can take care of [Assets](../../guides/assets/#all-about-assets) for you, or how to build [Standalone Apps](../../distribution/building-standalone-apps/#building-standalone-apps) you can submit to Apple or Google. - Join us on Slack to get your questions answered. diff --git a/docs/yarn.lock b/docs/yarn.lock index c3f8b305dac351..91ccc3d9191756 100644 --- a/docs/yarn.lock +++ b/docs/yarn.lock @@ -1266,6 +1266,11 @@ async-sema@2.1.4: dependencies: double-ended-queue "2.1.0-0" +async@^1.5.2: + version "1.5.2" + resolved "https://registry.yarnpkg.com/async/-/async-1.5.2.tgz#ec6a61ae56480c0c3cb241c95618e20892f9672a" + integrity sha1-7GphrlZIDAw8skHJVhjiCJL5Zyo= + atob@^2.1.1: version "2.1.1" resolved "https://registry.yarnpkg.com/atob/-/atob-2.1.1.tgz#ae2d5a729477f289d60dd7f96a6314a22dd6c22a" @@ -2038,6 +2043,11 @@ core-util-is@~1.0.0: resolved "https://registry.yarnpkg.com/core-util-is/-/core-util-is-1.0.2.tgz#b5fd54220aa2bc5ab57aab7140c940754503c1a7" integrity sha1-tf1UIgqivFq1eqtxQMlAdUUDwac= +corser@~2.0.0: + version "2.0.1" + resolved "https://registry.yarnpkg.com/corser/-/corser-2.0.1.tgz#8eda252ecaab5840dcd975ceb90d9370c819ff87" + integrity sha1-jtolLsqrWEDc2XXOuQ2TcMgZ/4c= + cosmiconfig@^4.0.0: version "4.0.0" resolved "https://registry.yarnpkg.com/cosmiconfig/-/cosmiconfig-4.0.0.tgz#760391549580bbd2df1e562bc177b13c290972dc" @@ -2197,6 +2207,13 @@ debug@^3.1.0: dependencies: ms "2.0.0" +debug@^3.2.6: + version "3.2.6" + resolved "https://registry.yarnpkg.com/debug/-/debug-3.2.6.tgz#e83d17de16d8a7efb7717edbe5fb10135eee629b" + integrity sha512-mel+jf7nrtEl5Pn1Qx46zARXKDpBbvzezse7p7LqINmdoIk8PYP5SySaxEmYv6TZ0JyEKA1hsCId6DIhgITtWQ== + dependencies: + ms "^2.1.1" + debug@^4.1.0: version "4.1.0" resolved "https://registry.yarnpkg.com/debug/-/debug-4.1.0.tgz#373687bffa678b38b1cd91f861b63850035ddc87" @@ -2384,6 +2401,16 @@ duplexify@^3.4.2, duplexify@^3.6.0: readable-stream "^2.0.0" stream-shift "^1.0.0" +ecstatic@^3.0.0: + version "3.3.1" + resolved "https://registry.yarnpkg.com/ecstatic/-/ecstatic-3.3.1.tgz#b15b5b036c2233defc78d7bacbd8765226c95577" + integrity sha512-/rrctvxZ78HMI/tPIsqdvFKHHscxR3IJuKrZI2ZoUgkt2SiufyLFBmcco+aqQBIu6P1qBsUNG3drAAGLx80vTQ== + dependencies: + he "^1.1.1" + mime "^1.6.0" + minimist "^1.1.0" + url-join "^2.0.5" + ee-first@1.1.1: version "1.1.1" resolved "https://registry.yarnpkg.com/ee-first/-/ee-first-1.1.1.tgz#590c61156b0ae2f4f0255732a158b266bc56b21d" @@ -2577,6 +2604,11 @@ event-source-polyfill@0.0.12: resolved "https://registry.yarnpkg.com/event-source-polyfill/-/event-source-polyfill-0.0.12.tgz#e539cd67fdef2760a16aa5262fa98134df52e3af" integrity sha1-5TnNZ/3vJ2ChaqUmL6mBNN9S468= +eventemitter3@^3.0.0: + version "3.1.0" + resolved "https://registry.yarnpkg.com/eventemitter3/-/eventemitter3-3.1.0.tgz#090b4d6cdbd645ed10bf750d4b5407942d7ba163" + integrity sha512-ivIvhpq/Y0uSjcHDcOIccjmYjGLcP09MFGE7ysAwkAvkXfpZlC985pH2/ui64DKazbTW/4kN3yqozUxlXzI6cA== + events@^1.0.0, events@^1.1.0: version "1.1.1" resolved "https://registry.yarnpkg.com/events/-/events-1.1.1.tgz#9ebdb7635ad099c70dcc4c2a1f5004288e8bd924" @@ -2725,6 +2757,13 @@ flush-write-stream@^1.0.0: inherits "^2.0.1" readable-stream "^2.0.4" +follow-redirects@^1.0.0: + version "1.7.0" + resolved "https://registry.yarnpkg.com/follow-redirects/-/follow-redirects-1.7.0.tgz#489ebc198dc0e7f64167bd23b03c4c19b5784c76" + integrity sha512-m/pZQy4Gj287eNy94nivy5wchN3Kp+Q5WgUPNy5lJSZ3sgkVKSYV/ZChMAQVIgx1SqfZ2zBZtPA2YlXIWxxJOQ== + dependencies: + debug "^3.2.6" + for-in@^1.0.2: version "1.0.2" resolved "https://registry.yarnpkg.com/for-in/-/for-in-1.0.2.tgz#81068d295a8142ec0ac726c6e2200c30fb6d5e80" @@ -3021,6 +3060,11 @@ hash.js@^1.0.0, hash.js@^1.0.3: inherits "^2.0.3" minimalistic-assert "^1.0.0" +he@^1.1.1: + version "1.2.0" + resolved "https://registry.yarnpkg.com/he/-/he-1.2.0.tgz#84ae65fa7eafb165fddb61566ae14baf05664f0f" + integrity sha512-F/1DnUGPopORZi0ni+CvrCgHQ5FyEAHRLSApuYWMmrbSwoN2Mn/7k+Gl38gJnR7yyDZk6WLXwiGod1JOWNDKGw== + header-case@^1.0.0: version "1.0.1" resolved "https://registry.yarnpkg.com/header-case/-/header-case-1.0.1.tgz#9535973197c144b09613cd65d317ef19963bd02d" @@ -3094,6 +3138,29 @@ http-errors@~1.6.2: setprototypeof "1.1.0" statuses ">= 1.4.0 < 2" +http-proxy@^1.8.1: + version "1.17.0" + resolved "https://registry.yarnpkg.com/http-proxy/-/http-proxy-1.17.0.tgz#7ad38494658f84605e2f6db4436df410f4e5be9a" + integrity sha512-Taqn+3nNvYRfJ3bGvKfBSRwy1v6eePlm3oc/aWVxZp57DQr5Eq3xhKJi7Z4hZpS8PC3H4qI+Yly5EmFacGuA/g== + dependencies: + eventemitter3 "^3.0.0" + follow-redirects "^1.0.0" + requires-port "^1.0.0" + +http-server@^0.11.1: + version "0.11.1" + resolved "https://registry.yarnpkg.com/http-server/-/http-server-0.11.1.tgz#2302a56a6ffef7f9abea0147d838a5e9b6b6a79b" + integrity sha512-6JeGDGoujJLmhjiRGlt8yK8Z9Kl0vnl/dQoQZlc4oeqaUoAKQg94NILLfrY3oWzSyFaQCVNTcKE5PZ3cH8VP9w== + dependencies: + colors "1.0.3" + corser "~2.0.0" + ecstatic "^3.0.0" + http-proxy "^1.8.1" + opener "~1.4.0" + optimist "0.6.x" + portfinder "^1.0.13" + union "~0.4.3" + http-status@1.0.1: version "1.0.1" resolved "https://registry.yarnpkg.com/http-status/-/http-status-1.0.1.tgz#dc43001a8bfc50ac87d485a892f7578964bc94a2" @@ -3836,7 +3903,7 @@ mime@1.4.1: resolved "https://registry.yarnpkg.com/mime/-/mime-1.4.1.tgz#121f9ebc49e3766f311a76e1fa1c8003c4b03aa6" integrity sha512-KI1+qOZu5DcW6wayYHSzR/tXKCDC5Om4s1z2QJjDULzLcmf3DvzS7oluY4HCTrc+9FiKmWUgeNLg7W3uIQvxtQ== -mime@^1.2.11: +mime@^1.2.11, mime@^1.6.0: version "1.6.0" resolved "https://registry.yarnpkg.com/mime/-/mime-1.6.0.tgz#32cd9e5c64553bd58d19a568af452acff04981b1" integrity sha512-x0Vn8spI+wuJ1O6S7gnbaQg8Pxh4NNHb7KSINmEWKiPE4RKOplvijn+NkmYmmRgP68mc70j2EbeTFRsrswaQeg== @@ -3880,7 +3947,7 @@ minimist@^1.1.0, minimist@^1.2.0: resolved "https://registry.yarnpkg.com/minimist/-/minimist-1.2.0.tgz#a35008b20f41383eec1fb914f4cd5df79a264284" integrity sha1-o1AIsg9BOD7sH7kU9M1d95omQoQ= -minimist@~0.0.8: +minimist@~0.0.1, minimist@~0.0.8: version "0.0.10" resolved "https://registry.yarnpkg.com/minimist/-/minimist-0.0.10.tgz#de3f98543dbf96082be48ad1a0c7cda836301dcf" integrity sha1-3j+YVD2/lggr5IrRoMfNqDYwHc8= @@ -3937,7 +4004,7 @@ mkdirp@0.3.0: resolved "https://registry.yarnpkg.com/mkdirp/-/mkdirp-0.3.0.tgz#1bbf5ab1ba827af23575143490426455f481fe1e" integrity sha1-G79asbqCevI1dRQ0kEJkVfSB/h4= -mkdirp@^0.5.0, mkdirp@^0.5.1, mkdirp@~0.5.0: +mkdirp@0.5.x, mkdirp@^0.5.0, mkdirp@^0.5.1, mkdirp@~0.5.0: version "0.5.1" resolved "https://registry.yarnpkg.com/mkdirp/-/mkdirp-0.5.1.tgz#30057438eac6cf7f8c4767f38648d6697d75c903" integrity sha1-MAV0OOrGz3+MR2fzhkjWaX11yQM= @@ -4318,6 +4385,19 @@ once@^1.3.0, once@^1.3.1, once@^1.4.0: dependencies: wrappy "1" +opener@~1.4.0: + version "1.4.3" + resolved "https://registry.yarnpkg.com/opener/-/opener-1.4.3.tgz#5c6da2c5d7e5831e8ffa3964950f8d6674ac90b8" + integrity sha1-XG2ixdflgx6P+jlklQ+NZnSskLg= + +optimist@0.6.x: + version "0.6.1" + resolved "https://registry.yarnpkg.com/optimist/-/optimist-0.6.1.tgz#da3ea74686fa21a19a111c326e90eb15a0196686" + integrity sha1-2j6nRob6IaGaERwybpDrFaAZZoY= + dependencies: + minimist "~0.0.1" + wordwrap "~0.0.2" + os-browserify@^0.3.0: version "0.3.0" resolved "https://registry.yarnpkg.com/os-browserify/-/os-browserify-0.3.0.tgz#854373c7f5c2315914fc9bfc6bd8238fdda1ec27" @@ -4596,6 +4676,15 @@ pkg-up@^2.0.0: dependencies: find-up "^2.1.0" +portfinder@^1.0.13: + version "1.0.20" + resolved "https://registry.yarnpkg.com/portfinder/-/portfinder-1.0.20.tgz#bea68632e54b2e13ab7b0c4775e9b41bf270e44a" + integrity sha512-Yxe4mTyDzTd59PZJY4ojZR8F+E5e97iq2ZOHPz3HDgSvYC5siNad2tLooQ5y5QHyQhc3xVqvyk/eNA3wuoa7Sw== + dependencies: + async "^1.5.2" + debug "^2.2.0" + mkdirp "0.5.x" + posix-character-classes@^0.1.0: version "0.1.1" resolved "https://registry.yarnpkg.com/posix-character-classes/-/posix-character-classes-0.1.1.tgz#01eac0fe3b5af71a2a6c02feabb8c1fef7e00eab" @@ -4746,6 +4835,11 @@ punycode@^2.1.0, punycode@^2.1.1: resolved "https://registry.yarnpkg.com/punycode/-/punycode-2.1.1.tgz#b58b010ac40c22c5657616c8d2c2c02c7bf479ec" integrity sha512-XRsRjdf+j5ml+y/6GKHPZbrF/8p2Yga0JPtdqTIY2Xe5ohJPD9saDJJLPvp9+NSBprVvevdXZybnj2cv8OEd0A== +qs@~2.3.3: + version "2.3.3" + resolved "https://registry.yarnpkg.com/qs/-/qs-2.3.3.tgz#e9e85adbe75da0bbe4c8e0476a086290f863b404" + integrity sha1-6eha2+ddoLvkyOBHaghikPhjtAQ= + querystring-es3@^0.2.0, querystring-es3@^0.2.1: version "0.2.1" resolved "https://registry.yarnpkg.com/querystring-es3/-/querystring-es3-0.2.1.tgz#9ec61f79049875707d69414596fd907a4d711e73" @@ -5013,6 +5107,11 @@ require-from-string@^2.0.1, require-from-string@^2.0.2: resolved "https://registry.yarnpkg.com/require-from-string/-/require-from-string-2.0.2.tgz#89a7fdd938261267318eafe14f9c32e598c36909" integrity sha512-Xf0nWe6RseziFMu+Ap9biiUbmplq6S9/p+7w7YXP/JBHhrUDDUhwa+vANyubuqfZWTveU//DYVGsDG7RKL/vEw== +requires-port@^1.0.0: + version "1.0.0" + resolved "https://registry.yarnpkg.com/requires-port/-/requires-port-1.0.0.tgz#925d2601d39ac485e091cf0da5c6e694dc3dcaff" + integrity sha1-kl0mAdOaxIXgkc8NpcbmlNw9yv8= + reselect@^3.0.1: version "3.0.1" resolved "https://registry.yarnpkg.com/reselect/-/reselect-3.0.1.tgz#efdaa98ea7451324d092b2b2163a6a1d7a9a2147" @@ -5933,6 +6032,13 @@ union-value@^1.0.0: is-extendable "^0.1.1" set-value "^0.4.3" +union@~0.4.3: + version "0.4.6" + resolved "https://registry.yarnpkg.com/union/-/union-0.4.6.tgz#198fbdaeba254e788b0efcb630bc11f24a2959e0" + integrity sha1-GY+9rrolTniLDvy2MLwR8kopWeA= + dependencies: + qs "~2.3.3" + unique-filename@^1.1.0: version "1.1.1" resolved "https://registry.yarnpkg.com/unique-filename/-/unique-filename-1.1.1.tgz#1d69769369ada0583103a1e6ae87681b56573230" @@ -6044,6 +6150,11 @@ urix@^0.1.0: resolved "https://registry.yarnpkg.com/urix/-/urix-0.1.0.tgz#da937f7a62e21fec1fd18d49b35c2935067a6c72" integrity sha1-2pN/emLiH+wf0Y1Js1wpNQZ6bHI= +url-join@^2.0.5: + version "2.0.5" + resolved "https://registry.yarnpkg.com/url-join/-/url-join-2.0.5.tgz#5af22f18c052a000a48d7b82c5e9c2e2feeda728" + integrity sha1-WvIvGMBSoACkjXuCxenC4v7tpyg= + url@0.11.0, url@^0.11.0: version "0.11.0" resolved "https://registry.yarnpkg.com/url/-/url-0.11.0.tgz#3838e97cfc60521eb73c525a8e55bfdd9e2e28f1" @@ -6282,6 +6393,11 @@ win-release@^1.0.0: dependencies: semver "^5.0.1" +wordwrap@~0.0.2: + version "0.0.3" + resolved "https://registry.yarnpkg.com/wordwrap/-/wordwrap-0.0.3.tgz#a3d5da6cd5c0bc0008d37234bbaf1bed63059107" + integrity sha1-o9XabNXAvAAI03I0u68b7WMFkQc= + worker-farm@1.5.2: version "1.5.2" resolved "https://registry.yarnpkg.com/worker-farm/-/worker-farm-1.5.2.tgz#32b312e5dc3d5d45d79ef44acc2587491cd729ae"