websocket-text-relay 1.1.6 → 1.1.7

package/README.md

@@ -3,8 +3,6 @@
 This application connects to your text editor using the Language Server Protocol (LSP) and then starts a websocket
 server that front end clients can connect to and subscribe to file change events. This allows users to see their
 front end changes evaluated immediately as they type, without having to first save the file to disk or reload the browser.
-It's a similar concept to sites like CodePen and JsFiddle, except you can develop locally using your own text editor with all
-of your personalized plugins instead of having to use an in browser code editor.
 
 ## Usage
 
@@ -23,14 +21,14 @@ the status UI and verify everything is running by first starting up your text ed
 
 To use this on a professional level project that gives you the option to use modules, typescript, and react, I recommend using vite along with
 the plugin [vite-plugin-websocket-text-relay](https://github.com/niels4/vite-plugin-websocket-text-relay). This plugin gives you all the power of vite when developing while also hooking
-the live text updates into Vite's hot module reload system.
+the live text updates into Vite's hot module reload system. See [live-demo-vite](https://github.com/niels4/live-demo-vite) for a complete project setup with Typescript, React, Vite, ViTest, and a simple router.
 
 If you want to use this as a learning tool to play around with UI concepts using simple projects involving 1 html, css, and javascript file,
-then check out this [simple reference project](https://github.com/niels4/wtr-simple-example). This is a great setup for following along with any short and focused web development tutorials.
+then check out [live-demo-vanillajs](https://github.com/niels4/live-demo-vanillajs). This is a great setup for following along with any short and focused web development tutorials.
 
 And finally, the status UI for this project was also created using live updates from websocket-text-relay.
 In addition to giving you live feedback on the status and activity of the application, it is also meant to serve as a
-reference UI project that is more complicated than a single javascript file, but still doesn't use any external dependencies.
+reference UI project that doesn't use any external dependencies.
 
 ## Developing
 

package/changelog.md

@@ -1,3 +1,13 @@
+## 1.1.7 - 2025/12/19
+
+### UI Update
+Allow default websocket port to be overridden with url search param: `?port=38378`
+
+## 1.1.6 - 2025/12/19
+
+### UI Update
+Rewrite the UI to be simpler and fix browser compatibility issues.
+
 ## 1.1.5 - 2025/09/05
 
 Minor UI spacing fix

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "websocket-text-relay",
-  "version": "1.1.6",
+  "version": "1.1.7",
   "description": "An LSP server for sending live file updates from your text editor to the front end via websockets.",
   "bin": {
     "websocket-text-relay": "./start.js"

package/src/ui/js/setup.js

@@ -4,8 +4,10 @@ import { setIsOnline, setSessions } from "./data/wtrStatus.js"
 import { eventSubscriber } from "./setup/eventSubscriber.js" // make sure the eventSubscriber function is available on the __WTR__ object
 import { emitActivity } from "./data/wtrActivity.js"
 
+const searchParams = new URLSearchParams(window.location.search)
+
 const FILE_PREFIX = "websocket-text-relay/src/ui/"
-const WS_PORT = 38378
+const wsPort = searchParams.get("port") ?? 38378
 const { hostname, protocol } = window.location
 const wsProtocol = protocol === "http:" ? "ws" : "wss"
 const CSS_FILE = "css/main.css"
@@ -25,7 +27,7 @@ const jsFiles = [
   "js/components/activityLabels.js",
 ]
 
-const ws = new WebsocketClient({ port: WS_PORT, host: hostname, protocol: wsProtocol })
+const ws = new WebsocketClient({ port: wsPort, host: hostname, protocol: wsProtocol })
 
 const cssElement = document.getElementById("main_style")