Lampix Apps API
  • Introduction
  • Application Development
    • Getting Started
      • Up and Running
      • Boilerplate
    • Step by step app
      • What We'll Build
      • Environment Setup
      • Styling
      • HTML Structure
      • NeuralNetworkClassifier
      • MovementBasedSegmenter
      • Final Step
      • Extras
    • LampixJS
      • API Reference
        • Watcher
        • RegisteredWatcher
        • .watchers.add
        • .watchers.remove
        • .watchers.pauseAll
        • .watchers.resumeAll
        • .presets.button
        • .helpers.rectangle
        • getLampixInfo
        • switchToApp
        • exit
        • getApps
        • getAppConfig
        • getAppMetadata
        • writeJsonToFile
        • readJsonFromFile
        • transformRectCoords
        • constants
      • Examples
        • NeuralNetworkClassifier: Buttons
        • MovementBasedSegmenter
        • Counter App
      • Migrating from v0.x.x to v1.0.0-beta.x
      • Ecosystem
    • Deploying
      • Application Structure (production)
      • Local Deploy
    • Standard Watchers
    • Custom Watchers
      • Description
      • Environment Setup
      • Directory Structure
      • End result
      • QRCodeDetector implementation
    • Community
  • Lampix Simulator
    • Installation
    • Usage
      • Basics
Powered by GitBook
On this page

Was this helpful?

  1. Application Development
  2. Getting Started

Boilerplate

PreviousUp and RunningNextStep by step app

Last updated 6 years ago

Was this helpful?

Any modern JavaScript boilerplate (aka "template", "starter", "seed") is fine, and one can develop Lampix applications without any boilerplate. The following are all equally fine:

Depending on your application's needs, your choice of boilerplate may differ. The one thing to keep in mind is what the should look like when deploying the application.

We provide a boilerplate of our own that is meant to facilitate development, but does not assume anything other than your application's source code entry points (index.html and index.js). It is not as mature as the above, but for your consideration, this is why we use it:

  • simple to understand and extend

  • minimal infrastructure only - no non-vanilla technology is assumed

  • HMR

  • build step includes archive creation for my.lampix.com, along with versioned build folders (based on package.json version)

  • build scripts to automatically increase patch, minor or major versions before building, alongside the "just build" script

  • respects the requirements of the

The boilerplate can be found on our .

create-react-app
angular-cli
vue-cli
production application structure
production application structure
GitHub