docs: improve tabs and package manager scripts (#1339)

Author: nickserv

docs/bs-react-testing-library/intro.mdx

@@ -15,6 +15,9 @@ Bindings for several testing libraries have been ported to [ReasonML][re].
 
 ```bash npm2yarn
 npm install --save-dev bs-dom-testing-library
+```
+
+```bash npm2yarn
 npm install --save-dev bs-react-testing-library
 ```
 

docs/dom-testing-library/api-custom-queries.mdx

@@ -3,9 +3,6 @@ id: api-custom-queries
 title: Custom Queries
 ---
 
-import Tabs from '@theme/Tabs'
-import TabItem from '@theme/TabItem'
-
 `DOM Testing Library` exposes many of the helper functions that are used to
 implement the default queries. You can use the helpers to build custom queries.
 For example, the code below shows a way to override the default `testId` queries

docs/dom-testing-library/api-debugging.mdx

@@ -32,7 +32,7 @@ value is `7000`. You will see `...` in the console, when the DOM content is
 stripped off, because of the length you have set or due to default size limit.
 Here's how you might increase this limit when running tests:
 
-```
+```bash npm2yarn
 DEBUG_PRINT_LIMIT=10000 npm test
 ```
 
@@ -46,7 +46,7 @@ colors, such as in cases where the output is written to a log file for debugging
 purposes. You can use the environment variable `COLORS` to explicitly force the
 colorization off or on. For example:
 
-```
+```bash npm2yarn
 COLORS=false npm test
 ```
 

docs/ecosystem-user-event.mdx

@@ -3,9 +3,6 @@ id: ecosystem-user-event
 title: user-event v13
 ---
 
-import Tabs from '@theme/Tabs'
-import TabItem from '@theme/TabItem'
-
 [`user-event`][gh] is a companion library for Testing Library that provides more
 advanced simulation of browser interactions than the built-in
 [`fireEvent`](dom-testing-library/api-events.mdx#fireevent) method.
@@ -21,23 +18,10 @@ fixes and new features.
 
 ## Installation
 
-  <Tabs defaultValue="npm" values={[{ label: 'npm', value: 'npm' }, { label: 'Yarn', value: 'yarn' }]}>
-  <TabItem value="npm">
-
-```sh
+```bash npm2yarn
 npm install --save-dev @testing-library/user-event @testing-library/dom
 ```
 
-  </TabItem>
-  <TabItem value="yarn">
-
-```sh
-yarn add --dev @testing-library/user-event @testing-library/dom
-```
-
-  </TabItem>
-  </Tabs>
-
 Now simply import it in your tests:
 
 ```js

docs/example-react-intl.mdx

@@ -141,4 +141,4 @@ the component in a way that will simulate the user behavior as much as posible.
 | Use strings from the default language      | Test is easy to read, and asserts expected default output. If you have variables in your strings, you can test that they work properly with correct output.                                                                                                                          | 1. Strings hardcoded into tests mean you have to update both tests and code for any copy changes. 2. If multiple elements have the same string/substring text, find-and-replace may be hard to use reliably.                                                          |
 | Mock the translation library               | If your library is difficult to use in the test environment, you can mock it so it is easier. For example, you can add the message ID as a data-attribute to the text so you can query by that.                                                                                      | Test code deviates from what runs in production. Tests may assert about message IDs but not enough about content, so errors are possible.                                                                                                                             |
 | Use translation library in tests           | Decouples strings from tests, so you can update the message files in one place without worrying about breaking tests. Can run tests in another language or multiple languages. `const buttonText = getNodeText(<FormattedMessage id="buttonText" defaultMessage="Hello Button" />);` | Overhead - it takes more lines of code to write the test, and you need to know the variables and message IDs to create the right strings. It's not obvious what the text actually is when you read the test code, making maintaining it harder.                       |
-| Use translation library + inline snapshots | Same as above, but by adding an inline snapshot of the string, you can read the test code and see what strings are in use, but easily update them with `jest -u` if the messages change. `expect(buttonText).toMatchInlineSnapshot("'My button text'")`                              | Tests are longer because of the extra lines. You can wrap up some of the translation-related code into a helper function to make it a little more inline-able and avoid repeating yourself, but you still need to know the message IDs and variables inside the test. |
+| Use translation library + inline snapshots | Same as above, but by adding an inline snapshot of the string, you can read the test code and see what strings are in use, but easily update them with `jest --updateSnapshot` if the messages change. `expect(buttonText).toMatchInlineSnapshot("'My button text'")`                | Tests are longer because of the extra lines. You can wrap up some of the translation-related code into a helper function to make it a little more inline-able and avoid repeating yourself, but you still need to know the message IDs and variables inside the test. |

docs/marko-testing-library/api.mdx

@@ -294,8 +294,8 @@ You can turn off the automatic test cleanup by importing the following module:
 import '@marko/testing-library/dont-cleanup-after-each'
 ```
 
-With mocha you can use `mocha -r @marko/testing-library/dont-cleanup-after-each`
-as a shorthand.
+With mocha you can use
+`mocha --require @marko/testing-library/dont-cleanup-after-each` as a shorthand.
 
 If you are using Jest, you can include
 `setupFilesAfterEnv: ["@marko/testing-library/dont-cleanup-after-each"]` in your

docs/marko-testing-library/setup.mdx

@@ -80,7 +80,7 @@ To run server-side Marko tests with `mocha` you can simply run the following
 command:
 
 ```console
-mocha -r marko/node-require
+mocha --require marko/node-require
 ```
 
 This enables the

docs/nightwatch-testing-library/intro.mdx

@@ -14,7 +14,7 @@ in [Nightwatch](https://nightwatchjs.org) for end-to-end web testing.
 then just
 
 ```bash npm2yarn
-npm install -D @testing-library/nightwatch
+npm install --save-dev @testing-library/nightwatch
 ```
 
 - [nightwatch-testing-library on GitHub][gh]

docs/react-testing-library/setup.mdx

@@ -478,7 +478,7 @@ do this with Jest's `setupFiles` configuration:
 Or with mocha's `-r` flag:
 
 ```
-mocha -r @testing-library/react/dont-cleanup-after-each
+mocha --require @testing-library/react/dont-cleanup-after-each
 ```
 
 Alternatively, you could import `@testing-library/react/pure` in all your tests
@@ -508,5 +508,5 @@ exports.mochaHooks = {
 And register it using mocha's `-r` flag:
 
 ```
-mocha -r ./mocha-watch-cleanup-after-each.js
+mocha --require ./mocha-watch-cleanup-after-each.js
 ```

docs/svelte-testing-library/setup.mdx

@@ -87,7 +87,7 @@ npm install --save-dev @vitest/ui
    how) and run the following command to run the tests.
 
    ```bash npm2yarn
-   npm run test
+   npm test
    ```
 
 ## Jest
@@ -104,7 +104,7 @@ npm install --save-dev @vitest/ui
     {
       "scripts": {
         "test": "jest src",
-        "test:watch": "npm run test -- --watch"
+        "test:watch": "jest src --watch"
       }
     }
     ```
@@ -180,7 +180,7 @@ npm install --save-dev @vitest/ui
     and run it
 
     ```bash npm2yarn
-    npm run test
+    npm test
     ```
 
 ### TypeScript