fix: more references to package name

Author: mdjastrzebski

.github/ISSUE_TEMPLATE/bug_report.md

@@ -34,5 +34,5 @@ labels: 'bug report'
 <!--
   run following command in terminal of your root project and paste the result down
 
-  `npx envinfo --npmPackages react,react-native,react-test-renderer,react-native-testing-library`
--->
+  `npx envinfo --npmPackages react,react-native,react-test-renderer,@testing-library/react-native`
+-->

CONTRIBUTING.md

@@ -63,4 +63,4 @@ You can report issues on our [bug tracker](https://github.com/callstack/react-na
 
 ## License
 
-By contributing to `react-native-testing-library`, you agree that your contributions will be licensed under its **MIT** license.
+By contributing to `@testing-library/react-native`, you agree that your contributions will be licensed under its **MIT** license.

README.md

@@ -67,13 +67,13 @@ Open a Terminal in your project's folder and run:
 #### Using `yarn`
 
 ```sh
-yarn add --dev react-native-testing-library
+yarn add --dev @testing-library/react-native
 ```
 
 #### Using `npm`
 
 ```sh
-npm install --save-dev react-native-testing-library
+npm install --save-dev @testing-library/react-native
 ```
 
 This library has a peerDependencies listing for `react-test-renderer` and, of course, `react`. Make sure to install them too!
@@ -115,7 +115,7 @@ As you may have noticed, it's not tied to React Native at all – you can safely
 
 ## API / Usage
 
-The [public API](https://callstack.github.io/react-native-testing-library/docs/api) of `react-native-testing-library` is focused around these essential methods:
+The [public API](https://callstack.github.io/react-native-testing-library/docs/api) of `@testing-library/react-native` is focused around these essential methods:
 
 - [`render`](https://callstack.github.io/react-native-testing-library/docs/api#render) – deeply renders given React element and returns helpers to query the output components.
 - [`fireEvent`](https://callstack.github.io/react-native-testing-library/docs/api#fireevent) - invokes named event handler on the element.

src/helpers/errors.js

@@ -33,7 +33,7 @@ export function printDeprecationWarning(functionName: string) {
 
   console.warn(`
   Deprecation Warning:
-  Use of ${functionName} is not recommended and will be deleted in future versions of react-native-testing-library.
+  Use of ${functionName} is not recommended and will be deleted in future versions of @testing-library/react-native.
   `);
 
   warned[functionName] = true;

website/docs/API.md

@@ -3,7 +3,7 @@ id: api
 title: API
 ---
 
-This page gathers public API of `react-native-testing-library` along with usage examples.
+This page gathers public API of `@testing-library/react-native` along with usage examples.
 
 ## `render`
 
@@ -134,7 +134,7 @@ Please note that this is done automatically if the testing framework you're usin
 For example, if you're using the `jest` testing framework, then you would need to use the `afterEach` hook like so:
 
 ```jsx
-import { cleanup, render } from 'react-native-testing-library/pure';
+import { cleanup, render } from '@testing-library/react-native/pure';
 import { View } from 'react-native';
 
 afterEach(cleanup);

website/docs/GettingStarted.md

@@ -13,7 +13,7 @@ You finally want to approach testing using only best practices, while Enzyme may
 
 ## This solution
 
-The `react-native-testing-library` is a lightweight solution for testing your React Native components. It provides light utility functions on top of `react-test-renderer` letting you always be up to date with latest React features and write any component tests you like. It also prevents you from testing implementation details because we believe this is a very bad practice.
+The `@testing-library/react-native` is a lightweight solution for testing your React Native components. It provides light utility functions on top of `react-test-renderer` letting you always be up to date with latest React features and write any component tests you like. It also prevents you from testing implementation details because we believe this is a very bad practice.
 
 This library is a replacement for [Enzyme](http://airbnb.io/enzyme/).
 
@@ -53,13 +53,13 @@ Open a Terminal in your project's folder and run:
 #### Using `yarn`
 
 ```sh
-yarn add --dev react-native-testing-library
+yarn add --dev @testing-library/react-native
 ```
 
 #### Using `npm`
 
 ```sh
-npm install --save-dev react-native-testing-library
+npm install --save-dev @testing-library/react-native
 ```
 
 This library has a peerDependencies listing for `react-test-renderer` and, of course, `react`. Make sure to install them too!

website/docs/Queries.md

@@ -203,7 +203,7 @@ const element = getByA11yValue({ min: 40 });
 
 > Use sparingly and responsibly, escape hatches here
 
-`render` from `react-native-testing-library` exposes additional queries that **should not be used in component integration testing**, but some users (like component library creators) interested in unit testing some components may find helpful.
+`render` from `@testing-library/react-native` exposes additional queries that **should not be used in component integration testing**, but some users (like component library creators) interested in unit testing some components may find helpful.
 
 <details>
   <summary>Queries helpful in unit testing</summary>

website/docs/ReactNavigation.md

@@ -3,7 +3,7 @@ id: react-navigation
 title: React Navigation
 ---
 
-This section deals with integrating `react-native-testing-library` with `react-navigation`, using Jest.
+This section deals with integrating `@testing-library/react-native` with `react-navigation`, using Jest.
 
 ## Setting up
 
@@ -127,7 +127,7 @@ const styles = StyleSheet.create({
 Install required dev dependencies:
 
 ```
-$ yarn add -D jest react-native-testing-library
+$ yarn add -D jest @testing-library/react-native
 ```
 
 Create your `jest.config.js` file (or place the following properties in your `package.json` as a "jest" property)