Serves a nice looking map on the detail page of the application.
Azure is used for deploying the bot to the cloud as a fallback to hardware device deployment.
All ES6 was transpiled trough the babel-loader.
CSS was prefixed and minified with postcss-loader.
Images optimized with imageoptim.
Main platform of deployment. This proved to be the easiest with our React + Node stack.
We had the develop branch deployed on a staging subdomain and master on the rootdomain.
Our DBaaS and backend. All database operations run trough Firebase and requests/responses arrive in realtime.
We wrote a lot of flexbox and css that needed prefixing. PostCSS + Webpack was the best option here.
Task runner for building, serving and deploying
Simple assertions in combination with Enzyme.
All frontend logic consisted of a plain React app without state management of some sort.
Component and DOM testing for React integrated with Mocha.
This is the main deployment platform. The bot is deployed on a Rasbperry Pi B+ and runs in a Docker container.
The backbone of the application. Takes care of application logic and bot responses.
Runs on Node v6+ as a standalone server. Optionally uses nodemon for monitoring of server process.
Serves static content. Was added to make it more easy to transition to serverside view templating and API.
Write next generation js
Get notified of build status, deployment status, github changes and internal communication for the team.
Fetching modules from the npm registry in local development
Enforce code-style and non error-prone code for maintaining the module
Transpile a little ES2015+ stuff down to valid ES5/ES6/CommonJS/UMD
Module is published as bpost on the npm registry.
Tasks for the module are also defined as npm run tasks with commit hooks for git