# \#nodejs

**URL:** https://swi-prolog.discourse.group/tag/nodejs/156.md

[Latest](https://swi-prolog.discourse.group/latest.md) · [Categories](https://swi-prolog.discourse.group/categories.md) · [Tags](https://swi-prolog.discourse.group/tags.md)

---

## [Best practice for resource disposal in TCP connection](https://swi-prolog.discourse.group/t/best-practice-for-resource-disposal-in-tcp-connection/6503)

<div class="topic-metadata">

**Author:** [@atava](https://swi-prolog.discourse.group/u/atava)\
**Replies:** 3\
**Last updated:** [April 29, 2023, 11:34am UTC](https://swi-prolog.discourse.group/t/best-practice-for-resource-disposal-in-tcp-connection/6503 "2023-04-29T11:34:32Z")

</div>

I’m writing some Node code for a Visual Studio Code extension that needs to communicate with a swipl process without blocking the terminal or “polluting” it, and thanks to suggestions by Jan I managed to achieve this qui…

---

## [Answers to queries not written to stdout on WASM + Node](https://swi-prolog.discourse.group/t/answers-to-queries-not-written-to-stdout-on-wasm-node/6476)

<div class="topic-metadata">

**Author:** [@atava](https://swi-prolog.discourse.group/u/atava)\
**Replies:** 4\
**Last updated:** [April 19, 2023, 11:52am UTC](https://swi-prolog.discourse.group/t/answers-to-queries-not-written-to-stdout-on-wasm-node/6476 "2023-04-19T11:52:54Z")

</div>

For what I can gather from the source, the WASM shell example relies on the on\_output function both for showing SWI-Prolog messages and answers to queries (the latter are sent to the stdout stream). Running on Node, ans…