Skip to content
Switch branches/tags

Latest commit


Git stats


Failed to load latest commit information.
Latest commit message
Commit time

Labstache: A LabVIEW™ Toolkit for Rendering Logic-Free Mustache Templates

Labstache is a pure LabVIEW library for working with logic-free Mustache templates. Logic-less Mustache templates are a simple format using curly bracket delimiters ({{}}) that works great with any text-based file, especially formats that use a markup language, such as HTML. This library enables LabVIEW developers to interact with and use Mustache templates.

Table of Contents

Example Usage

A VI snippet of compiling, or rendering, a mustache template as a string into a string:

Simple Mustache String Rendering



  • LabVIEW 2014 or newer (All systems)


The Caraya, JKI State Machine, OpenG Array Library, OpenG File Library, and VIPM API dependencies must be installed for all versions of LabVIEW (2014 and 2018) to avoid errors during automated builds.


A VI Package (VIP) is available at The recommended installation instructions are to:

  1. Navigate to the Labstache package at
  2. Click on the Install button to the right. The VI Package Manager (VIPM) (freely available from JKI) will start automatically.
  3. Follow the on-screen instructions to complete the installation.

Alternatively, the toolkit can be installed by: (i) downloading the source code and building the VIP, (ii) downloading a VIP from the releases section of this project, or (iii) manually copying the VIs from the source code into a project.


Each component in the Labstache project has a Source Distribution build specification. The destination of each source distribution build is the builds folder relative to the project root, i.e. same folder as the Labstache.lvproj file. Additionally, the output for the compiled help documentation is also the builds folder. The builds folder should not be included in the version control repository. A script is available in the Scripts.lvlib project library that will build all of the components and the help documentation automatically (VIPM Pro is not needed, but the HTML Help Workshop is needed).

The VI Package Build (.vipb) specification, located in the configs folder relative to the project root, is configured for the package source to be the builds folder. Thus, the Source Distribution for each component must be built before opening the Labstache.vipb file in the VIPM; otherwise, the package configuration will be lost.

Packaging using VIPM Pro (recommended)

Important, if creating a package for LabVIEW 2014 from LabVIEW 2018, the VI Server TCP/IP ports must be different for each version of LabVIEW and verified with the VIPM application before proceeding. An error will occur when the VIPM is started if both LabVIEW 2014 and 2018 are running at the same time. Basically, VIPM will not know which VI server to use if both versions of LabVIEW are using the same TCP/IP port.

If VIPM Pro is available, then open the Labstache.lvproj file in any version of LabVIEW newer than 2014 and run the located in the Scripts.lvlib project library of the Project Explorer window. Ensure all dependencies are installed before running the script.

Note, the version number for the package is set in the configs\Labstache.vipb file. The version number in the VIP build specification file should be modified and saved before running the script.

Packaging using VIPM Free

If VIPM Pro is not available, then the following steps can be executed to do essentially the same thing as the script. Ensure all dependencies, except VIPM Pro and the VIPM API, are installed before completing these steps.

  1. Start LabVIEW 2018 or newer and open the Labstache.lvproj file.
  2. From the Project Explorer window, File>>Save for Previous Version..., a new dialog will appear.
  3. Select 14.0 from the drop down menu.
  4. Click Save.... A new dialog will open.
  5. Create the target\14.0 folder hierarchy in the project root, i.e. the same folder as the Labstache.lvproj file, if it does not already exists.
  6. Click Save.
  7. Close LabVIEW 2018 or newer and the Labstache.lvproj file.
  8. Navigate to <project root>\src.
  9. Copy the Help folder to <project root>\target\14.0\src.
  10. Start LabVIEW 2014.
  11. Open the <project root>\target\14.0\Labstache.lvproj file. Do NOT open the project in any other version of LabVIEW.
  12. Open each Source Distribution build specification under the "Build Specifications" tree item in the Project Explorer and change the Output Destination to <project root>\target\14.0\builds. Save and close each build specification.
  13. Run the in the Scripts project library to build each Source Distribution under the "Build Specifications" tree item and the compiled help documentation file (Labstache.chm). The output of each build will be available in <project root>\target\14.0\builds.
  14. Open the <project root>\target\14.0\configs\Labstache.vipb file in VIPM.
  15. Build the VI package with VIPM. The output will be available at <project root>\target\14.0\packages. Do NOT modify anything in the package build specification, but ensure the "2014" version of LabVIEW is selected in the upper, right-hand corner of the VIPM application window.
  16. Close VIPM.
  17. Close LabVIEW 2014 and the <project root>\target\14.0\Labstache.lvproj file.


See the in-app LabVIEW Help system for more information and documentation about using the library after it has been installed, or visit the web-based documentation. Examples are also available within the LabVIEW development environment using the "Help->Find Examples..." menu item.


Tests are written in LabVIEW using the Caraya unit testing framework and included in the project via the various Tests.lvlib project libraries and the tests on-disk folder. To run the tests, open the Labstache.lvproj file found in the project root in the LabVIEW Development Environment and run the script located in the Scripts.lvlib project library. This will run all of the tests defined in all of the various Tests.lvlib project libraries located in the project.


Labstache is licensed under the MIT license. See the docs folder for all information about licensing and copyright.