@tugitark/react-widget 1.4.4 → 1.4.5

package/from-scratch.md

@@ -35,7 +35,7 @@ The code below demonstrates the basics of what is going on behind the scenes wit
   
   The details here are partially supplied by Tugi Tark (e.g. the `brandId`), and otherwise customisable by you:
   
-  ```javacript
+  ```javascript
   function initialise() {
       window.tugiWidget.initialize({
           jwtFn: getUserToken,
@@ -61,7 +61,7 @@ The code below demonstrates the basics of what is going on behind the scenes wit
   
   This requires a user that is logged in:
   
-  ```javacript
+  ```javascript
   async function getUserToken() {
       const response = await fetch('/users/current/tugi-token');
       if (response.ok) {
@@ -78,7 +78,7 @@ The code below demonstrates the basics of what is going on behind the scenes wit
   
   If a user logs in after loading the widget tell it so it can update the JWT:
   
-  ```javacript
+  ```javascript
   if (window.tugiWidget?.isInitialized()) {
       window.tugiWidget.refresh();
   }

package/index.md

@@ -10,7 +10,7 @@ Also see [the original integration guide](https://www.tugitark.com/chat-setup) f
 
 This is the smallest number of properties that you can pass to `<TugiWidget>` and have it still operate correctly.  These properties are given to you on signing up with Tugi Tark and must be entered accurately.
 
-```javascript
+```react
 import TugiWidget from '@tugitark/react-widget';
 
 function Component(props) {
@@ -34,7 +34,7 @@ If your server has the standard `/.tugi` endpoints (as provided by our back-end
 
 This is a more extensive widget example, with colour-scheme customisation and an explicit JWT lookup function.  The HTTP and websocket addresses are also specified, though match the defaults.
 
-```javascript
+```react
 import TugiWidget from '@tugitark/react-widget';
 
 interface Props {
@@ -108,7 +108,7 @@ A "proactive" message can be used to detect that a player has a problem and offe
 
 If both `tugiFn` and `user` are missing from the `<TugiWidget>` properties then the widget goes in to the special free mode (more accurately, both must be `null` or `undefined` - if you want a user who isn't logged in pass a `user` of `''`).  In this mode the user cannot send or receive any messages, they can only view a few pre-defined FAQ-style help topics:
 
-```javascript
+```react
 import TugiWidget from '@tugitark/react-widget';
 
 function Component(props) {
@@ -152,7 +152,7 @@ The following optional properties are shared with the full version:
 
 While there can be only one widget on the page there can be multiple `<TugiWidget>` components at once.  Which one will be used is non-deterministic - even if you have one `<TugiWidget>` with `visible={true}` and another one with `visible={false}` this will not guarantee that the visible one is the one that gets shown, the invisible one may be "shown", resulting in neither being seen.  The one selected is based on internal render and update orders.  Further, having two at once may result in the widget being constantly unloaded and reloaded even when nothing has changed as the underlying code flips repeatedly between them.  If you have two versions of the widget shown in different circumstances then make sure that the whole component is conditional:
 
-```javascript
+```react
 return (
 	disabled
 		? <TugiWidget

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@tugitark/react-widget",
-	"version": "1.4.4",
+	"version": "1.4.5",
 	"description": "Wraps the tugitark widget in a React component.",
 	"scripts": {
 		"build": "npx esbuild index.ts --target=es6 --outfile=index.js && sed -i 's/\\bconst\\b/var/g' index.js && sed -i 's/\\blet\\b/var/g' index.js && npx esbuild index.js --allow-overwrite --minify --target=es5 --outfile=index.js && npx tsc --noErrorTruncation --declaration --emitDeclarationOnly --target es6 --module nodenext --moduleResolution nodenext --outDir . index.ts",