Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Fix typo in pnpm config note #13226

Merged
merged 1 commit into from Sep 9, 2022
Merged

Fix typo in pnpm config note #13226

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
6 changes: 3 additions & 3 deletions docs/Configuration.md
View file
Open in desktop
Expand Up @@ -2185,13 +2185,13 @@ export default config;

:::tip

If you use `pnpm` and need to convert some packages under `node_modules`, you need to note that the packages in this folder (e.g. `node_modules/package-a/`) have been symlinked to the path under `.pnpm` (e.g. `node_modules/.pnpm/package-a@x.x.x/node_modules/pakcage-a/`), so using `<rootdir>/node_modules/(?!(package-a|package-b)/)` directly will not be recognized, while is to use:
If you use `pnpm` and need to convert some packages under `node_modules`, you need to note that the packages in this folder (e.g. `node_modules/package-a/`) have been symlinked to the path under `.pnpm` (e.g. `node_modules/.pnpm/package-a@x.x.x/node_modules/pakcage-a/`), so using `<rootDir>/node_modules/(?!(package-a|package-b)/)` directly will not be recognized, while is to use:

```js tab
/** @type {import('jest').Config} */
const config = {
transformIgnorePatterns: [
'<rootdir>/node_modules/.pnpm/(?!(package-a|package-b)@)',
'<rootDir>/node_modules/.pnpm/(?!(package-a|package-b)@)',
],
};

Expand All @@ -2203,7 +2203,7 @@ import type {Config} from 'jest';

const config: Config = {
transformIgnorePatterns: [
'<rootdir>/node_modules/.pnpm/(?!(package-a|package-b)@)',
'<rootDir>/node_modules/.pnpm/(?!(package-a|package-b)@)',
],
};

Expand Down
4 changes: 2 additions & 2 deletions website/versioned_docs/version-25.x/Configuration.md
View file
Open in desktop
Expand Up @@ -1342,12 +1342,12 @@ Example:

:::tip

If you use `pnpm` and need to convert some packages under `node_modules`, you need to note that the packages in this folder (e.g. `node_modules/package-a/`) have been symlinked to the path under `.pnpm` (e.g. `node_modules/.pnpm/package-a@x.x.x/node_modules/pakcage-a/`), so using `<rootdir>/node_modules/(?!(package-a|package-b)/)` directly will not be recognized, while is to use:
If you use `pnpm` and need to convert some packages under `node_modules`, you need to note that the packages in this folder (e.g. `node_modules/package-a/`) have been symlinked to the path under `.pnpm` (e.g. `node_modules/.pnpm/package-a@x.x.x/node_modules/pakcage-a/`), so using `<rootDir>/node_modules/(?!(package-a|package-b)/)` directly will not be recognized, while is to use:

```json
{
"transformIgnorePatterns": [
"<rootdir>/node_modules/.pnpm/(?!(package-a|package-b)@)"
"<rootDir>/node_modules/.pnpm/(?!(package-a|package-b)@)"
]
}
```
Expand Down
4 changes: 2 additions & 2 deletions website/versioned_docs/version-26.x/Configuration.md
View file
Open in desktop
Expand Up @@ -1342,12 +1342,12 @@ Example:

:::tip

If you use `pnpm` and need to convert some packages under `node_modules`, you need to note that the packages in this folder (e.g. `node_modules/package-a/`) have been symlinked to the path under `.pnpm` (e.g. `node_modules/.pnpm/package-a@x.x.x/node_modules/pakcage-a/`), so using `<rootdir>/node_modules/(?!(package-a|package-b)/)` directly will not be recognized, while is to use:
If you use `pnpm` and need to convert some packages under `node_modules`, you need to note that the packages in this folder (e.g. `node_modules/package-a/`) have been symlinked to the path under `.pnpm` (e.g. `node_modules/.pnpm/package-a@x.x.x/node_modules/pakcage-a/`), so using `<rootDir>/node_modules/(?!(package-a|package-b)/)` directly will not be recognized, while is to use:

```json
{
"transformIgnorePatterns": [
"<rootdir>/node_modules/.pnpm/(?!(package-a|package-b)@)"
"<rootDir>/node_modules/.pnpm/(?!(package-a|package-b)@)"
]
}
```
Expand Down
4 changes: 2 additions & 2 deletions website/versioned_docs/version-27.x/Configuration.md
View file
Open in desktop
Expand Up @@ -1411,12 +1411,12 @@ Example:

:::tip

If you use `pnpm` and need to convert some packages under `node_modules`, you need to note that the packages in this folder (e.g. `node_modules/package-a/`) have been symlinked to the path under `.pnpm` (e.g. `node_modules/.pnpm/package-a@x.x.x/node_modules/pakcage-a/`), so using `<rootdir>/node_modules/(?!(package-a|package-b)/)` directly will not be recognized, while is to use:
If you use `pnpm` and need to convert some packages under `node_modules`, you need to note that the packages in this folder (e.g. `node_modules/package-a/`) have been symlinked to the path under `.pnpm` (e.g. `node_modules/.pnpm/package-a@x.x.x/node_modules/pakcage-a/`), so using `<rootDir>/node_modules/(?!(package-a|package-b)/)` directly will not be recognized, while is to use:

```json
{
"transformIgnorePatterns": [
"<rootdir>/node_modules/.pnpm/(?!(package-a|package-b)@)"
"<rootDir>/node_modules/.pnpm/(?!(package-a|package-b)@)"
]
}
```
Expand Down
4 changes: 2 additions & 2 deletions website/versioned_docs/version-28.x/Configuration.md
View file
Open in desktop
Expand Up @@ -1653,12 +1653,12 @@ Example:

:::tip

If you use `pnpm` and need to convert some packages under `node_modules`, you need to note that the packages in this folder (e.g. `node_modules/package-a/`) have been symlinked to the path under `.pnpm` (e.g. `node_modules/.pnpm/package-a@x.x.x/node_modules/pakcage-a/`), so using `<rootdir>/node_modules/(?!(package-a|package-b)/)` directly will not be recognized, while is to use:
If you use `pnpm` and need to convert some packages under `node_modules`, you need to note that the packages in this folder (e.g. `node_modules/package-a/`) have been symlinked to the path under `.pnpm` (e.g. `node_modules/.pnpm/package-a@x.x.x/node_modules/pakcage-a/`), so using `<rootDir>/node_modules/(?!(package-a|package-b)/)` directly will not be recognized, while is to use:

```json
{
"transformIgnorePatterns": [
"<rootdir>/node_modules/.pnpm/(?!(package-a|package-b)@)"
"<rootDir>/node_modules/.pnpm/(?!(package-a|package-b)@)"
]
}
```
Expand Down
6 changes: 3 additions & 3 deletions website/versioned_docs/version-29.0/Configuration.md
View file
Open in desktop
Expand Up @@ -2185,13 +2185,13 @@ export default config;

:::tip

If you use `pnpm` and need to convert some packages under `node_modules`, you need to note that the packages in this folder (e.g. `node_modules/package-a/`) have been symlinked to the path under `.pnpm` (e.g. `node_modules/.pnpm/package-a@x.x.x/node_modules/pakcage-a/`), so using `<rootdir>/node_modules/(?!(package-a|package-b)/)` directly will not be recognized, while is to use:
If you use `pnpm` and need to convert some packages under `node_modules`, you need to note that the packages in this folder (e.g. `node_modules/package-a/`) have been symlinked to the path under `.pnpm` (e.g. `node_modules/.pnpm/package-a@x.x.x/node_modules/pakcage-a/`), so using `<rootDir>/node_modules/(?!(package-a|package-b)/)` directly will not be recognized, while is to use:

```js tab
/** @type {import('jest').Config} */
const config = {
transformIgnorePatterns: [
'<rootdir>/node_modules/.pnpm/(?!(package-a|package-b)@)',
'<rootDir>/node_modules/.pnpm/(?!(package-a|package-b)@)',
],
};

Expand All @@ -2203,7 +2203,7 @@ import type {Config} from 'jest';

const config: Config = {
transformIgnorePatterns: [
'<rootdir>/node_modules/.pnpm/(?!(package-a|package-b)@)',
'<rootDir>/node_modules/.pnpm/(?!(package-a|package-b)@)',
],
};

Expand Down