This PR addresses #52 (Monorepo) #53 (Upgrade react-native and react-native-svg) #54 (Fix demo - work by @sibelius)

53 + 54 are tightly coupled. I chose to include 52 because fixing dependencies would require 4 package publications (all the victory-*-native packages), just to be completely obviated when moving to the monorepo.

cc/ @boygirl

The current setup with the demo/ app existing in a subdirectory is not natural for the RN packager. As a workaround, we can use babel-plugin-module-resolver to define the victory-native location to be the local lib/, and run the demo app from the root directory:

$ npm install -g react-native-cli # install victory-native if you haven't already
$ git clone https://github.com/FormidableLabs/victory-native
$ cd victory-native
$ npm install   # install victory-native
$ npm start     # start react-native packager manually before launching demo!
$ npm demo:ios  # or react-native run-android

Do not run npm install in the demo/ directory, or the packager packager will crash due to "duplicate @providesModule declarations" found in node_modules/ and demo/node_modules.

If you have existing demo/node_modules, you'll need to nuke them.

Notice the custom npm start and npm demo:ios scripts.

Does not fix issue for Android. Will submit that separately, need to do a bit more testing for it.

cc/ @chrisbolin this PR updates Victory to 0.21.0 and adds support for polar charts.

Caveats: I couldn't figure out how to work around https://github.com/FormidableLabs/victory-native/issues/103, so I've temporarily disabled text rotations

~Spurious test failure for VictoryLabel~ Updated react-native-svg-mock to include TSpan mock

Bumps handlebars from 4.1.1 to 4.7.3.

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.

The goal is to bring our native and React dependencies in line with latest versions. React Native 60 requires the Android project use AndroidX support libraries and we can opt into Hermes. We have done both for our Android project in this case. iOS does not have any major architectural changes like Android. Finally this simplifies some of the dev deps in the JS project.

Fixes https://github.com/FormidableLabs/victory-native/issues

victory deps are victory-core, victory-chart, and victory-pie, all of which output es modules.

fixes https://github.com/FormidableLabs/victory/issues/639

Depends on https://github.com/FormidableLabs/victory-core/pull/265 Depends on https://github.com/FormidableLabs/victory-pie/pull/148

Issue #674 reports that Victory core 35.11.0 breaks Victory Native. I suspect this is due to some of the class-to-function component conversions in the core (released in 35.11.0) which are not respected in Victory Native.

One solution, short term, is for users to pin their versions via yarn's resolutions field. However, to avoid everyone having to do that, I'm proposing we do minor-version pinning at the library level here so this won't break for future users, and we don't have to tell people to do user-land resolutions to get the library to work.

Eventually, Victory Native's code will need to be updated to potentially move from class inheritance to function composition - but this seems like a fair short-time fix.

#77 Entrance transitions were completely broken, as was all dynamic clipping. Upgrading to [email protected] fixed this; however, that upgrade necessitated upgrades to [email protected] and [email protected].

Also cleaned up a related hack (from #74) that is not needed anymore, and some bogus props that made debugging more confusing :P

Port VictoryCursorContainer from victory-chart.

To do that, a few other things had to be knocked out...

• update react, victory-core, and victory-chart
• migrate to prop-types
• remove deprecated VictoryZoom
• remove deprecated VoronoiTooltip

https://github.com/FormidableLabs/victory-native/issues/81

Wait to merge for FormidableLabs/victory-chart#461 and FormidableLabs/victory-core#233 (CI will fail until then)