Skip to content

Commit 515879b

Browse files
AlejandraPedrozadanil-pavlov
authored andcommitted
feat: replace wasm tasks (#4704)
* update: replace wasm tasks * chore: fix typo
1 parent cb8ac88 commit 515879b

File tree

5 files changed

+15
-15
lines changed

5 files changed

+15
-15
lines changed
-88.7 KB
Loading

docs/topics/js/js-project-setup.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -272,33 +272,33 @@ Once an npm dependency is installed, you can use its API in your code as describ
272272

273273
## run task
274274

275-
The Kotlin Multiplatform Gradle plugin provides a `jsRun` task that lets you run pure Kotlin/JS projects without additional configuration.
275+
The Kotlin Multiplatform Gradle plugin provides a `jsBrowserDevelopmentRun` task that lets you run pure Kotlin/JS projects without additional configuration.
276276

277277
For running Kotlin/JS projects in the browser, this task is an alias for the `browserDevelopmentRun` task (which is also
278278
available in Kotlin multiplatform projects). It uses the [webpack-dev-server](https://webpack.js.org/configuration/dev-server/)
279279
to serve your JavaScript artifacts.
280280
If you want to customize the configuration used by `webpack-dev-server`, for example, adjust the port the server runs on,
281281
use the [webpack configuration file](#webpack-bundling).
282282

283-
For running Kotlin/JS projects targeting Node.js, use the `jsRun` task that is an alias for the `nodeRun` task.
283+
For running Kotlin/JS projects targeting Node.js, use the `jsBrowserDevelopmentRun` task that is an alias for the `nodeRun` task.
284284

285-
To run a project, execute the standard lifecycle `jsRun` task, or the alias to which it corresponds:
285+
To run a project, execute the standard lifecycle `jsBrowserDevelopmentRun` task, or the alias to which it corresponds:
286286

287287
```bash
288-
./gradlew jsRun
288+
./gradlew jsBrowserDevelopmentRun
289289
```
290290

291291
To automatically trigger a re-build of your application after making changes to the source files, use the Gradle
292292
[continuous build](https://docs.gradle.org/current/userguide/command_line_interface.html#sec:continuous_build) feature:
293293

294294
```bash
295-
./gradlew jsRun --continuous
295+
./gradlew jsBrowserDevelopmentRun --continuous
296296
```
297297

298298
or
299299

300300
```bash
301-
./gradlew jsRun -t
301+
./gradlew jsBrowserDevelopmentRun -t
302302
```
303303

304304
Once the build of your project has succeeded, the `webpack-dev-server` will automatically refresh the browser page.

docs/topics/js/running-kotlin-js.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -14,14 +14,14 @@ Depending on the target platform, some platform-specific extra setup might be re
1414

1515
## Run the Node.js target
1616

17-
When targeting Node.js with Kotlin/JS, you can simply execute the `jsRun` Gradle task. This can be done for example via the
17+
When targeting Node.js with Kotlin/JS, you can simply execute the `jsBrowserDevelopmentRun` Gradle task. This can be done for example via the
1818
command line, using the Gradle wrapper:
1919

2020
```bash
21-
./gradlew jsRun
21+
./gradlew jsBrowserDevelopmentRun
2222
```
2323

24-
If you're using IntelliJ IDEA, you can find the `jsRun` action in the Gradle tool window:
24+
If you're using IntelliJ IDEA, you can find the `jsBrowserDevelopmentRun` action in the Gradle tool window:
2525

2626
![Gradle Run task in IntelliJ IDEA](run-gradle-task.png){width=700}
2727

@@ -57,10 +57,10 @@ After making these adjustments, start the integrated development server. You can
5757
Gradle wrapper:
5858

5959
```bash
60-
./gradlew jsRun
60+
./gradlew jsBrowserDevelopmentRun
6161
```
6262

63-
When working from IntelliJ IDEA, you can find the `jsRun` action in the Gradle tool window.
63+
When working from IntelliJ IDEA, you can find the `jsBrowserDevelopmentRun` action in the Gradle tool window.
6464

6565
After the project has been built, the embedded `webpack-dev-server` will start running, and will open a (seemingly empty)
6666
browser window pointing to the HTML file you specified previously. To validate that your program is running correctly,

docs/topics/wasm/wasm-debugging.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -37,14 +37,14 @@ Create a project using the Kotlin Multiplatform wizard:
3737
>
3838
{style="note"}
3939

40-
2. In **composeApp** | **Tasks** | **kotlin browser**, select and run the **wasmJsBrowserRun** task.
40+
2. In **composeApp** | **Tasks** | **kotlin browser**, select and run the **wasmJsBrowserDevelopmentRun** task.
4141

4242
![Run the Gradle task](wasm-gradle-task-window.png){width=550}
4343

4444
Alternatively, you can run the following command in the terminal from the `WasmDemo` root directory:
4545

4646
```bash
47-
./gradlew wasmJsBrowserRun
47+
./gradlew wasmJsBrowserDevelopmentRun
4848
```
4949

5050
3. Once the application starts, open the following URL in your browser:

docs/topics/wasm/wasm-get-started.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -41,14 +41,14 @@ Create a project using the Kotlin Multiplatform wizard:
4141
>
4242
{style="note"}
4343

44-
2. In **composeApp** | **Tasks** | **kotlin browser**, select and run the **wasmJsBrowserRun** task.
44+
2. In **composeApp** | **Tasks** | **kotlin browser**, select and run the **wasmJsBrowserDevelopmentRun** task.
4545

4646
![Run the Gradle task](wasm-gradle-task-window.png){width=600}
4747

4848
Alternatively, you can run the following command in the terminal from the `WasmDemo` root directory:
4949

5050
```bash
51-
./gradlew wasmJsBrowserRun -t
51+
./gradlew wasmJsBrowserDevelopmentRun -t
5252
```
5353

5454
3. Once the application starts, open the following URL in your browser:

0 commit comments

Comments
 (0)