Steven G. Harris<p>I published a <a href="https://mastodon.social/tags/SwiftLog" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SwiftLog</span></a> backend for <a href="https://mastodon.social/tags/NodeSwift" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>NodeSwift</span></a>. I’ve been working on a VSCode extension using NodeSwift to access my existing <a href="https://mastodon.social/tags/Swift" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Swift</span></a> library. The SwiftLog backend routes, for example, `logger.info(“message”)` to node.js and includes a simple `NodeConsole.log(“message”)` to send messages to the node console. <a href="https://swiftpackageindex.com/stevengharris/NodeSwiftLogging" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">swiftpackageindex.com/stevengh</span><span class="invisible">arris/NodeSwiftLogging</span></a>. For reference: NodeSwift: <a href="https://github.com/kabiroberai/node-swift" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/kabiroberai/node-sw</span><span class="invisible">ift</span></a> and SwiftLog: <a href="https://github.com/apple/swift-log" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="">github.com/apple/swift-log</span><span class="invisible"></span></a>.</p>