Skip to content

Commit 44fdfde

Browse files
JSMonkAlejandraPedroza
authored andcommitted
Fix task names in the continuous compilation doc
1 parent 4ae8242 commit 44fdfde

File tree

4 files changed

+7
-3
lines changed

4 files changed

+7
-3
lines changed
216 KB
Loading
247 KB
Loading
435 KB
Loading

docs/topics/js/dev-server-continuous-compilation.md

Lines changed: 7 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,15 +1,19 @@
11
[//]: # (title: Development server and continuous compilation)
22

33
Instead of manually compiling and executing a Kotlin/JS project every time you want to see the changes you made,
4-
you can use the _continuous compilation_ mode. Instead of using the regular `run` command, invoke the Gradle wrapper
4+
you can use the _continuous compilation_ mode. Instead of using the regular `jsBrowserDevelopmentRun` (for `browser`) and `jsNodeDevelopmentRun` (for `nodejs`) command, invoke the Gradle wrapper
55
in _continuous_ mode:
66

77
```bash
8-
./gradlew run --continuous
8+
# for `browser` project
9+
./gradlew jsBrowserDevelopmentRun --continuous
10+
11+
# for `nodejs` project
12+
./gradlew jsNodeDevelopmentRun --continuous
913
```
1014

1115
If you are working in IntelliJ IDEA, you can pass the same flag via the _run configuration_. After running the Gradle
12-
`run` task for the first time from the IDE, IntelliJ IDEA automatically generates a run configuration for it,
16+
run task for the first time from the IDE, IntelliJ IDEA automatically generates a run configuration for it,
1317
which you can edit:
1418

1519
![Editing run configurations in IntelliJ IDEA](edit-configurations.png){width=700}

0 commit comments

Comments
 (0)