build(deps): bump xmldom, react-native and react-native-scripts in /Fancy UI Development

[dependabot]

Removes xmldom. It's no longer used after updating ancestor dependencies xmldom, react-native and react-native-scripts. These dependencies need to be updated together.

Removes xmldom

Updates react-native from 0.50.3 to 0.70.2

Release notes

Sourced from react-native's releases.

0.70.2

Added

iOS specific

• Add support for "Prefer Cross-Fade Transitions" into AccessibilityInfo (be7c50fefd by @​gabrieldonadel)

Changed

• Bump CLI to 9.1.3 and Metro to 0.72.3 (f164556037 by @​kelset)

Fixed

• Inform ScrollView of Keyboard Events Before Mount (26d148029c by @​NickGerleman)

Android specific

• Fix port as -1 if dev server without specifying port on Android (3d7e1380b4 by @​Kudo)

---

You can participate in the conversation on the status of this release in this discussion.

---

To help you upgrade to this version, you can use the upgrade helper ⚛️

---

You can find the whole changelog history in the changelog.md file.

0.70.1

Added

• Add more debugging settings for HermesExecutorFactory (32d12e89f8 by @​Kudo)
• Support TypeScript array types for turbo module (component only) (33d1291e1a by @​ZihanChen-MSFT)

Changed

• Accept TypeScript type T | null | undefined as a maybe type of T in turbo module. (9ecd203eec by @​ZihanChen-MSFT)
• Bump react-native-gradle-plugin to 0.70.3 (e33633644c by @​dmytrorykun)
• Bump react-native-codegen to 0.70.5 (6a8c38eef2 by @​dmytrorykun)
• Hermes version bump for 0.70.1 (5132211228 by @​dmytrorykun)

Fixed

... (truncated)

Changelog

Sourced from react-native's changelog.

v0.70.2

Added

iOS specific

• Add support for "Prefer Cross-Fade Transitions" into AccessibilityInfo (be7c50fefd by @​gabrieldonadel)

Changed

• Bump CLI to 9.1.3 and Metro to 0.72.3 (f164556037 by @​kelset)

Fixed

• Inform ScrollView of Keyboard Events Before Mount (26d148029c by @​NickGerleman)

Android specific

• Fix port as -1 if dev server without specifying port on Android (3d7e1380b4 by @​Kudo)

v0.70.1

Added

• Add more debugging settings for HermesExecutorFactory (32d12e89f8 by @​Kudo)
• Support TypeScript array types for turbo module (component only) (33d1291e1a by @​ZihanChen-MSFT)

Changed

• Accept TypeScript type T | null | undefined as a maybe type of T in turbo module. (9ecd203eec by @​ZihanChen-MSFT)
• Bump react-native-gradle-plugin to 0.70.3 (e33633644c by @​dmytrorykun)
• Bump react-native-codegen to 0.70.5 (6a8c38eef2 by @​dmytrorykun)
• Hermes version bump for 0.70.1 (5132211228 by @​dmytrorykun)

Fixed

• Fix hermes profiler (81564c1a3d by @​janicduplessis)

Android specific

• Support PlatformColor in borderColor (2d5db284b0 by @​danilobuerger)
• Avoid crash in ForwardingCookieHandler if webview is disabled (5451cd48bd by @​Pajn)
• Correctly resolve classes with FindClass(..) (361b310bcc by @​evancharlton)

iOS specific

• Fix KeyboardAvoidingView height when "Prefer Cross-Fade Transitions" is enabled (4b9382c250 by @​gabrieldonadel)
• Fix React module build error with swift integration on new architecture mode (3afef3c167 by @​Kudo)
• Fix ios pod install error (0cae4959b7 by @​Romick2005)

... (truncated)

Commits

• b9c2975 [0.70.2] Bump version numbers
• 13a2b11 Minor: Rename AccessibilityInfo.sendAccessibilityEvent_unstable to sendAccess...
• 2de4cf0 chore(deps): bump CLI to 9.1.3 and Metro to 0.72.3 (#34803)
• 7b53a24 Fix port as -1 if dev server without specifying port on Android (#34705)
• b03f536 fix: KeyboardAvoidingView height when "Prefer Cross-Fade Transitions" is enab...
• 764f584 Let ScrollView Know About Keyboard Opened Before Mount
• 75d5679 feat: Add support for "Prefer Cross-Fade Transitions" into AccessibilityInfo ...
• 73e5533 Add a pseudo flow declaration for AccessibilityInfo
• 9fd7643 Revert "fix: KeyboardAvoidingView height when "Prefer Cross-Fade Transitions"...
• a54ba33 [0.70.1] Bump version numbers
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by fb, a new releaser for react-native since your current version.

Updates react-native-scripts from 1.8.1 to 2.0.1

Changelog

Sourced from react-native-scripts's changelog.

2.0.1 (September 21, 2018)

This release merges Create React Native App with Expo CLI.

• Expo CLI is a tool based on CRNA, made by the same team
• It has all the same features, plus some additional benefits
• Like CRNA, Expo CLI does not require an Expo user account
• The create-react-native-app command will continue to work

The separate react-native-scripts package is now deprecated: new projects created with create-react-native-app will use Expo CLI instead of react-native-scripts. In addition to everything provided by CRNA, Expo CLI includes these extras:

• Web-based user interface: in addition to the CLI, there's a GUI where you can view logs, launch the app on your devices or simulators, and publish updates.
• Standalone app builds: you can build IPA and APK packages for deploying to App Store and Play Store without using Xcode or Android Studio.
• Publishing: you can push updates to your deployed apps and optionally publish your app to Expo.io.
• Tunnel: your physical device doesn’t need to be in the same wi-fi as your computer to be able to develop using it.
• Optional user accounts: logging in allows listing all your projects in development in the Expo app without having to scan any QR codes and enables additional features like standalone builds. However, just like CRNA, Expo CLI can also be used without a user account.

Why are we bringing these two tools together?

• Just one tool to learn: previously developers would start with CRNA and then switch to exp or XDE for additional features like standalone builds. Expo CLI is as easy to get started with as CRNA, but also supports everything previously offered by these separate tools.
• Less confusing options: CRNA apps have always been loaded using the Expo app and able to use the Expo APIs in addition to the core React Native APIs. Users are sometimes confused about the differences between plain React Native, CRNA and Expo apps created with tools like exp or XDE. Installing the expo-cli package will make it clearer the additional functionality is provided by Expo.
• Developer experience: Expo CLI is ahead of CRNA in terms of features and developer experience, and we’re continuously improving it.
• Maintenance: having these two projects as separate codebases requires more maintenance and CRNA has previously falled behind because of this. A single codebase helps us keep it up to date and fix issues as fast as possible.

Upgrading from 1.14.0 to 2.0.1

All apps created with create-react-native-app, are compatible with Expo CLI without changes.

Upgrade react-native-scripts to v2.0.1 with:

npm install --save --save-exact [email protected]

or

yarn add --exact [email protected]

When you run npm start for the first time, Expo CLI will be installed.

Because react-native-scripts is now a wrapper for Expo CLI, you can also follow these steps to remove it from your project and use Expo CLI directly:

1. Replace react-native-scripts with expo in the scripts config in package.json. Example:

   "scripts": {
     "start": "expo start",
     "eject": "expo eject",
     "android": "expo start --android",
   

... (truncated)

Commits

• See full diff in compare view

Maintainer changes

This version was pushed to npm by fson, a new releaser for react-native-scripts since your current version.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.