Skip to content

Commit 831ee66

Browse files
jeremymengjeremymeng
committed
pnpm build => pnpm turbo build
1 parent e63382c commit 831ee66

6 files changed

Lines changed: 19 additions & 17 deletions

‎documentation/Quickstart-on-how-to-write-tests.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -129,11 +129,11 @@ After writing your test cases you need to run your test cases and record the tes
129129

130130
## Run tests in record mode
131131

132-
Before running tests, it's advised to update the dependencies and build our project by running the command `pnpm install && pnpm build --filter=<package-name>...`. Please notice this command is time-consuming and it will take around 10 mins, you could refer [here](https://github.com/Azure/azure-sdk-for-js/blob/main/CONTRIBUTING.md#resolving-dependency-version-conflicts) for more details.
132+
Before running tests, it's advised to update the dependencies and build our project by running the command `pnpm install && pnpm turbo build --filter=<package-name>...`. Please notice this command is time-consuming and it will take around 10 mins, you could refer [here](https://github.com/Azure/azure-sdk-for-js/blob/main/CONTRIBUTING.md#resolving-dependency-version-conflicts) for more details.
133133

134134
```Shell
135135
> pnpm install
136-
> pnpm build --filter=@azure-rest/purview-datamap...
136+
> pnpm turbo build --filter=@azure-rest/purview-datamap...
137137
```
138138

139139
Then, we could go to the project folder to run the tests. By default, if you don't specify `TEST_MODE`, it will run previously recorded tests.

‎documentation/RLC-Swagger-quickstart.md‎

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -110,7 +110,7 @@ We are working on to automatically generate everything right now, but currently,
110110
111111
```shell
112112
pnpm update
113-
pnpm build --filter=<your-package-name>...
113+
pnpm turbo build --filter=<your-package-name>...
114114
cd <your-sdk-folder>
115115
pnpm pack
116116
```
@@ -155,14 +155,14 @@ See the [JavaScript Codegen Quick Start for Test](https://github.com/Azure/azure
155155
On Linux, you could use `export` to set env variable:
156156
157157
```shell
158-
pnpm build --filter=${PACKAGE_NAME}...
158+
pnpm turbo build --filter=${PACKAGE_NAME}...
159159
export TEST_MODE=record && pnpm test # this will run live test and generate a recordings folder, you will need to submit it in the PR.
160160
```
161161
162162
On Windows, you could use `SET`:
163163
164164
```shell
165-
pnpm build --filter=${PACKAGE_NAME}...
165+
pnpm turbo build --filter=${PACKAGE_NAME}...
166166
SET TEST_MODE=record&& pnpm test # this will run live test and generate a recordings folder, you will need to submit it in the PR.
167167
```
168168
@@ -171,14 +171,14 @@ See the [JavaScript Codegen Quick Start for Test](https://github.com/Azure/azure
171171
On Linux, you could use below commands:
172172
173173
```shell
174-
pnpm build --filter=${PACKAGE_NAME}...
174+
pnpm turbo build --filter=${PACKAGE_NAME}...
175175
export TEST_MODE=playback && pnpm test # this will run live test and generate a recordings folder, you will need to submit it in the PR.
176176
```
177177
178178
On Windows, you can use:
179179
180180
```shell
181-
pnpm build --filter=${PACKAGE_NAME}...
181+
pnpm turbo build --filter=${PACKAGE_NAME}...
182182
SET TEST_MODE=playback&& pnpm test # this will run live test and generate a recordings folder, you will need to submit it in the PR.
183183
```
184184
@@ -265,7 +265,7 @@ Now, we can use the exact same steps to build an releasable artifact.
265265
266266
```shell
267267
pnpm install
268-
pnpm build --filter=<your-package-name>...
268+
pnpm turbo build --filter=<your-package-name>...
269269
cd <your-sdk-folder>
270270
export TEST_MODE=record && pnpm test
271271
pnpm pack

‎documentation/case-study-investigating-a-pipeline-that-hangs.md‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,7 @@
11
# Case Study: Investigating a Pipeline that Hangs
22

3+
> **Note:** This is a historical case study. It describes the tooling and environment in use at the time of the investigation (mocha test runner, Node.js 8). The repository has since migrated to vitest and requires LTS versions of Node.js.
4+
35
## Problem
46

57
We have encountered a problem where the pipelines hung right after the identity tests were run [only(majorly) on Windows].

‎documentation/linting.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ In this document, we describe how to address common linting issues for a package
77
Our custom linting rules and recommended configurations is hosted in the `@azure/eslint-plugin-azure-sdk` package. You MUST build it first before linting any SDK packages.
88

99
- `pnpm install`
10-
- `pnpm build --filter=@azure/eslint-plugin-azure-sdk...`
10+
- `pnpm turbo build --filter=@azure/eslint-plugin-azure-sdk...`
1111

1212
It also gets built as a dependency of any SDK packages.
1313

‎documentation/migrating-to-typespec.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -243,7 +243,7 @@ Delete the following files that are no longer needed:
243243
2. **Build the package:**
244244

245245
```bash
246-
pnpm build
246+
pnpm turbo build
247247
```
248248

249249
3. **Run tests:**
@@ -269,7 +269,7 @@ After migration, your development workflow becomes:
269269

270270
1. **Update TypeSpec definitions** in azure-rest-api-specs
271271
2. **Generate new code:** `npm run generate:client`
272-
3. **Build and test:** `pnpm build && pnpm test`
272+
3. **Build and test:** `pnpm turbo build && pnpm test`
273273

274274
### Version Management
275275

‎documentation/steps-after-generations.md‎

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ After this finishes, you will see the generated code in `src` folder in your **{
99

1010
```shell
1111
pnpm install
12-
pnpm build --filter=<your-package-name>...
12+
pnpm turbo build --filter=<your-package-name>...
1313
```
1414

1515
# Customizing the generated code
@@ -60,14 +60,14 @@ See the [Javascript Codegen Quick Start for Test](https://github.com/Azure/azure
6060
On Linux, you could use `export` to set env variable:
6161

6262
```shell
63-
pnpm build --filter=${PACKAGE_NAME}...
63+
pnpm turbo build --filter=${PACKAGE_NAME}...
6464
export TEST_MODE=record && pnpm test # this will run live test and generate a recordings folder, you will need to submit it in the PR.
6565
```
6666

6767
On Windows, you could use `SET`:
6868

6969
```shell
70-
pnpm build --filter=${PACKAGE_NAME}...
70+
pnpm turbo build --filter=${PACKAGE_NAME}...
7171
SET TEST_MODE=record&& pnpm test # this will run live test and generate a recordings folder, you will need to submit it in the PR.
7272
```
7373

@@ -76,13 +76,13 @@ See the [Javascript Codegen Quick Start for Test](https://github.com/Azure/azure
7676
On Linux, you could use below commands:
7777

7878
```shell
79-
pnpm build --filter=${PACKAGE_NAME}...
79+
pnpm turbo build --filter=${PACKAGE_NAME}...
8080
export TEST_MODE=playback && pnpm test # this will run live test and generate a recordings folder, you will need to submit it in the PR.
8181
```
8282
On Windows, you can use:
8383

8484
```shell
85-
pnpm build --filter=${PACKAGE_NAME}...
85+
pnpm turbo build --filter=${PACKAGE_NAME}...
8686
SET TEST_MODE=playback&& pnpm test # this will run live test and generate a recordings folder, you will need to submit it in the PR.
8787
```
8888

@@ -155,7 +155,7 @@ Now, we can use the exact same steps to build a releasable artifact.
155155
156156
```shell
157157
pnpm update
158-
pnpm build --filter=<your-package-name>...
158+
pnpm turbo build --filter=<your-package-name>...
159159
cd <your-sdk-folder>
160160
export TEST_MODE=record && pnpm test
161161
pnpm pack

0 commit comments

Comments
 (0)