---
title: "Discussion on \"Kotlin Coroutines on wasmJs: why there is no `runBlocking` (and why “hacks” are risky)\" | Hashnode"
description: "Discussion on \"Kotlin Coroutines on wasmJs: why there is no `runBlocking` (and why “hacks” are risky)\". Explains why Kotlin's `runBlocking` is absent for wasmJs, highlighting risks and limitations of implementing blocking in JS/WASM environments"
url: "https://hashnode.com/posts/kotlin-coroutines-on-wasmjs-why-there-is-no-runblocking-and-why-hacks-are-risky/69592f7f6143a50acc62b709"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Kotlin Coroutines on wasmJs: why there is no \`runBlocking\` (and why “hacks” are risky)](https://blog.softartdev.org/kotlin-coroutines-on-wasmjs-why-there-is-no-runblocking-and-why-hacks-are-risky?utm_source=hashnode&utm_medium=feed)

Explains why Kotlin's \`runBlocking\` is absent for wasmJs, highlighting risks and limitations of implementing blocking in JS/WASM environments

Jan 3 · 5 min read · blog.softartdev.org  
Read the article

-   [#kotlin](https://hashnode.com/tag/kotlin)
-   [#kotlin-coroutines](https://hashnode.com/tag/kotlin-coroutines)
-   [#wasm](https://hashnode.com/tag/wasm)
-   [#js](https://hashnode.com/tag/js)
-   [#kotlin-multiplatform](https://hashnode.com/tag/kotlin-multiplatform)

## Written by

[SoftArtDev](https://hashnode.com/@softartdev)

@softartdev

  
[View profile](https://hashnode.com/@softartdev)

software-engineering concurrency security architecture

## Responses

Markdown supported · ⌘↵ to post

No responses yet.