React based frontend only extension sample that leverages Configuration Service
Switch branches/tags
Nothing to show
Clone or download
Leadbetter fixing issue #1
Latest commit 3fb0e50 Oct 11, 2018
Failed to load latest commit information.
__mocks__ initial commit Oct 8, 2018
bin initial commit Oct 8, 2018
public initial commit Oct 8, 2018
src fixing issue #1 Oct 11, 2018
test initial commit Oct 8, 2018
.babelrc initial commit Oct 8, 2018
.gitignore initial commit Oct 8, 2018 spelling Oct 8, 2018
index.js initial commit Oct 8, 2018
package.json initial commit Oct 8, 2018
template.html initial commit Oct 8, 2018
webpack.config.js initial commit Oct 8, 2018
yarn.lock initial commit Oct 8, 2018

Bot Commander Config Service Example


This is a quick example of the new config service, and how to build an extension with the service that does not rely on a backend server (EBS).


There is only one requirement to use this example.

  • Node.JS LTS or greater.

You may also find that using yarn is easier than npm, so we do recommend installing that as well by running:

npm i -g yarn

in an elevated command line interface.

First time Usage

To use this, simply clone the repository into the folder of your choice.

Next, do the following:

  1. Change directories into the cloned folder.
  2. Run yarn install to install all prerequisite packages needed to run the template.
  3. Run yarn cert to generate the needed certificates. This allows the server to be run over HTTPS vs. HTTP.
  4. Run yarn start to run the sample.


To build your finalized React JS files, simply run yarn build to build the various webpacked files.

File Structure

The file structure in the template is laid out with the following:


The /bin folder holds the cert generation script.


The /conf folder holds the generated certs after the cert generation script runs.


/dist holds the final JS files after building.


/public houses the static HTML files used for your code's entrypoint.


This folder houses all source code and relevant files (such as images). Each React class/component is given a folder to house all associated files (such as associated CSS).

Below this folder, the structure is much simpler.

This would be:

components -\App --\App.js --\App.test.js --\App.css -\Authentication --\Authentication.js ...

Each component is under the components folder.