From e768f9519bd1b1eae1a22972a4f9d966016a256d Mon Sep 17 00:00:00 2001
From: Kyle Machulis <kyle@nonpolynomial.com>
Date: Thu, 31 Dec 2020 13:27:51 -0800
Subject: [PATCH] chore: Add JS device control example

---
 .../writing-buttplug-applications/device-control.md         | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/developer-guide/writing-buttplug-applications/device-control.md b/developer-guide/writing-buttplug-applications/device-control.md
index dc6eaa2..09d6171 100644
--- a/developer-guide/writing-buttplug-applications/device-control.md
+++ b/developer-guide/writing-buttplug-applications/device-control.md
@@ -22,7 +22,7 @@ You'll usually interact with devices with Device instances, which will be differ
 
 As a user of a Buttplug Client API, you should never be expected to send raw Buttplug Messages. Most Client APIs will provide message sending functions for you, usually attached to device objects or structures. If the device accepts the message type represented by the function you call, it should be sent to the device. Otherwise, you'll receive an error about message compatibility.
 
-<CodeSwitcher :languages="{rust:'Rust', csharp:'C#'}">
+<CodeSwitcher :languages="{rust:'Rust', csharp:'C#', js: 'Javascript'}">
 <template v-slot:rust>
 
 <<< @/examples/rust/src/bin/device_control.rs
@@ -32,5 +32,9 @@ As a user of a Buttplug Client API, you should never be expected to send raw But
 
 <<< @/examples/csharp/DeviceControlExample/Program.cs
 
+</template>
+<template v-slot:js>
+
+<<< @/examples/javascript/device-config-example.js
 </template>
 </CodeSwitcher>