Upgrade docusaurus

Author: satya164

.markdownlint-cli2.yaml

@@ -2,6 +2,7 @@ globs:
   - '**/*.md'
 ignores:
   - node_modules
+  - build
   - versioned_docs/version-1.x
   - versioned_docs/version-2.x
   - versioned_docs/version-3.x

.markdownlint.yaml

@@ -6,5 +6,9 @@ MD013: false
 # Disable checks for inline HTML
 MD033: false
 
+# Disable checks that treat MDX comments/components as Markdown formatting
+MD037: false
+MD032: false
+
 # Descriptive link text
 MD059: false

.prettierrc.json

@@ -1,4 +1,17 @@
 {
+  "overrides": [
+    {
+      "files": [
+        "src/pages/**/*.md",
+        "blog/*.md",
+        "docs/**/*.md",
+        "versioned_docs/**/*.md"
+      ],
+      "options": {
+        "parser": "mdx"
+      }
+    }
+  ],
   "singleQuote": true,
   "tabWidth": 2,
   "trailingComma": "es5",

blog/2018-02-06-react-navigation-1.0.md

@@ -6,7 +6,7 @@ tags: [release, announcement]
 
 As of today, React Navigation version 1.0 has been released! To see a list of recent improvements leading up to the release, refer to the “[Renewed Path to React Navigation V1.0](https://github.com/react-navigation/react-navigation/issues/2585)” issue. Thank you to everybody who has filed high-quality bug reports, submitted pull requests, and helped out fellow developers while we were in beta!
 
-<!--truncate-->
+{/* truncate */}
 
 This release isn’t meant to be interpreted as a signal that React Navigation is “finished" &mdash; work is already underway on a number of significant changes to the API that aim to make React Navigation easier to use and more powerful. These changes will be run through our [new RFC process](https://github.com/react-navigation/rfcs). For example, the [Navigator View API RFC](https://github.com/react-navigation/rfcs/blob/master/text/0002-navigator-view-api.md) outlines a plan to decouple views from the router in order to make it easier for other navigation APIs, such as [react-native-router-flux](https://github.com/aksonov/react-native-router-flux) and [react-router-native](https://github.com/ReactTraining/react-router/tree/master/packages/react-router-native), to build on top of the same navigation views. We’re also very excited about a plan (no RFC is open yet, but keep an eye out for it) to use [react-native-gesture-handler](https://github.com/software-mansion/react-native-gesture-handler) to run navigation gestures (sliding a drawer open, or swiping back on a stack, for example) on the UI thread using the Animated native driver.
 

blog/2018-04-06-react-navigation-2.0-rc.md

@@ -6,7 +6,7 @@ tags: [release, announcement]
 
 Exactly two months after the release of React Navigation 1.0, we are close to another major version release. We’d like to invite developers that use the library to give the release candidate a try in your app and let us know if you encounter any issues.
 
-<!--truncate-->
+{/* truncate */}
 
 ```bash
 yarn add react-navigation@^2.0.0-rc.1

blog/2018-05-07-react-navigation-2.0.md

@@ -6,7 +6,7 @@ tags: [release, announcement]
 
 The documentation is now live at [reactnavigation.org](https://reactnavigation.org), and v1 lives [here](/docs/1.x/getting-started).
 
-<!--truncate-->
+{/* truncate */}
 
 ## Significant breaking changes
 

blog/2018-11-01-react-navigation-3.0-rc.md

@@ -8,7 +8,7 @@ We are excited to announce the release candidate of version 3.0 today!
 
 This is the first release where React Navigation depends on a native module outside of React Native core: it now depends on react-native-gesture-handler. This library provides an excellent set of primitives for leveraging the operating systems’ native gesture APIs and has enabled us to fix a variety of issues with stack and drawer navigators. React Navigation also depends on react-native-screens, but you don’t need to install the native module if you prefer not to use it (we have a blog post coming soon that will explain what react-native-screens is and why you may want to use it, or you can watch [this talk](https://www.youtube.com/watch?v=Z0Jl1KCWiag) by the author of the library).
 
-<!--truncate-->
+{/* truncate */}
 
 We didn’t get around to every feature that we wanted to land for this release, but we also didn’t want to hold it up further because we expect that you will want to start using it right away - the release includes performance improvements, bugfixes, ergonomics improvements, some handy new features, and a re-organizing of the internals to improve support for web as a target of React Navigation.
 

blog/2018-11-17-react-navigation-3.0.md

@@ -8,7 +8,7 @@ The documentation is now live at [reactnavigation.org](https://reactnavigation.o
 
 This is the first release where React Navigation depends on a native module outside of React Native core: it now depends on react-native-gesture-handler. This library provides an excellent set of primitives for leveraging the operating systems’ native gesture APIs and has enabled us to fix a variety of issues with stack and drawer navigators. React Navigation also depends on react-native-screens, but you don’t need to install the native module if you prefer not to use it (we have a blog post coming soon that will explain what react-native-screens is and why you may want to use it, or you can watch [this talk](https://www.youtube.com/watch?v=Z0Jl1KCWiag) by the author of the library).
 
-<!--truncate-->
+{/* truncate */}
 
 We didn’t get around to every feature that we wanted to land for this release, but we also didn’t want to hold it up further because we expect that you will want to start using it right away - the release includes performance improvements, bugfixes, ergonomics improvements, some handy new features, and a re-organizing of the internals to improve support for web as a target of React Navigation.
 

blog/2019-09-16-react-navigation-4.0.md

@@ -8,7 +8,7 @@ The documentation is now live at [reactnavigation.org](https://reactnavigation.o
 
 In this release, we have removed the navigators from the react-navigation package. The navigators have lived in separate packages for quite a while and you could already use those packages manually, but we still bundled them in the react-navigation package. This made it difficult for us to release significant updates to navigators, because we had to then do a major version release of react-navigation too. By separating the navigator packages there is more freedom to update and improve navigators without any impact on folks that don't use them.
 
-<!--truncate-->
+{/* truncate */}
 
 For example, you will find when you install the latest versions of the drawer and tab navigators that the animations are more performant because they use react-native-reanimated to smoothly animate gestures. These have been available in react-navigation-drawer and react-navigation-tabs for several months now but we delayed updating them in react-navigation itself because we did not want to force every user to update.
 

blog/2019-10-17-react-navigation-native.md

@@ -6,7 +6,7 @@ tags: [announcement]
 
 React Navigation steps firmly into the next level and we’re very excited to announce to you something great happening in React Navigation codebase.
 
-<!--truncate-->
+{/* truncate */}
 
 ## Make it custom
 
@@ -32,8 +32,16 @@ After years of growing development, we need to admit that we’re not always abl
 
 Thanks to the great work of Krzysztof Magiera for [React Native Screens](https://github.com/kmagiera/react-native-screens) library now we can use truly native components instead of JS replicas.
 
-<img src="/assets/blog/5.x/android-native-stack.gif" height="530" alt="Native Stack on Android" />
-<img src="/assets/blog/5.x/ios-native-stack.gif" height="530" alt="Native Stack on iOS" />
+<img
+  src="/assets/blog/5.x/android-native-stack.gif"
+  height="530"
+  alt="Native Stack on Android"
+/>
+<img
+  src="/assets/blog/5.x/ios-native-stack.gif"
+  height="530"
+  alt="Native Stack on iOS"
+/>
 
 We believe you will find it useful in your projects and strongly encourage you to get acquainted with our [documentation](https://github.com/kmagiera/react-native-screens/native-stack). Things that I’m the most excited about are iOS header animations!