0.0.17 • Public • Published

    npm version


    This is a Vue application example used as NPM package in single-spa-login-example-with-npm-packages in order to register an application. See the installation instructions there.

    ✍🏻 Motivation

    This is a vue application built as library which only contains the navbar and sidebar menus displayed after the user performs the required login.

    How it works

    There are several files for the right working of this application and they are:

    • src/singleSpaEntry.js
    • package.json
    • vue.config.js


    /* eslint-disable import/no-unresolved */
    import Vue from 'vue';
    import singleSpaVue from 'single-spa-vue';
    import { BootstrapVue } from 'bootstrap-vue';
    import { library } from '@fortawesome/fontawesome-svg-core';
    import { faGithub } from '@fortawesome/free-brands-svg-icons';
    import { faHome } from '@fortawesome/free-solid-svg-icons';
    import { FontAwesomeIcon } from '@fortawesome/vue-fontawesome';
    import App from './App.vue';
    Vue.component('font-awesome-icon', FontAwesomeIcon);
    Vue.config.productionTip = false;
    const vueLifecycles = singleSpaVue({
      appOptions: {
        el: '#layout-app',
        render: (h) => h(App),
    export const { bootstrap } = vueLifecycles;
    export const { mount } = vueLifecycles;
    export const { unmount } = vueLifecycles;

    The eslint comments are indicated due to webpack external dependencies. Without the eslint comments the build process will fail.
    The vueLifecycles object contains all single-spa-vue methods for the single-spa lifecycle of this app. All used config is default one but the custom config of the el option. It's assumed that an element with layout-app id is defined in the index.html where this application will be mounted.


      "name": "single-spa-layout-app",
      "version": "0.2.5",
      "description": "Vue application with header, navbar and footer for be included in a single-spa application as registered app.",
      "main": "dist/single-spa-layout-app.umd.js",
      "scripts": {
        "build": "vue-cli-service build --target lib --formats umd --name single-spa-layout-app src/singleSpaEntry.js",
        "lint": "vue-cli-service lint"
      "devDependencies": {
        "@vue/cli-plugin-babel": "4.1.0",
        "@vue/cli-plugin-eslint": "4.1.0",
        "@vue/cli-service": "4.1.0",
        "babel-eslint": "10.0.3",
        "core-js": "3.4.4",
        "eslint": "5.16.0",
        "eslint-config-airbnb-base": "14.0.0",
        "eslint-plugin-import": "2.20.0",
        "eslint-plugin-vue": "5.0.0",
        "sass": "1.24.4",
        "sass-loader": "8.0.2",
        "vue-cli-plugin-single-spa": "1.1.0",
        "vue-template-compiler": "2.6.11",
        "webpack": "4.41.5"
      "browserslist": [
        "> 1%",
        "last 2 versions"
      "license": "MIT",
      "repository": {
        "type": "git",
        "url": ""
      "keywords": [
      "author": "Juan Manuel López Pazos",
      "bugs": {
        "url": ""
      "homepage": ""

    There are only two scripts in this project:

    • build: for compile the application and build it as a libray in umd format
    • lint: for run eslint in all project

    There are only devDependencies because the application dependencies are defined as webpack externals.


    const path = require('path');
    const webpack = require('webpack');
    module.exports = {
      devServer: {
        writeToDisk: true,
      configureWebpack: {
        output: {
          library: 'single-spa-layout-app',
          libraryTarget: 'umd',
          filename: 'single-spa-layout-app.js',
          path: path.resolve(__dirname, 'dist'),
        plugins: [
          new webpack.optimize.LimitChunkCountPlugin({
            maxChunks: 1,
      chainWebpack: (config) => {

    The needed options for the right build of the application as library are defined in the configureWebpack.output field.
    The LimitChunkCountPlugin is used for disable chunks for build process. It's not necessary but I prefer keep whole application in one chunk as it will be embedded in another one.
    Finally, in the chainWebpack field all common dependencies between single spa registered apps are defined as externals. In that way, all single spa registered apps will use the same dependencies and they will be imported only in the root project.


    npm i single-spa-layout-app-kp

    DownloadsWeekly Downloads






    Unpacked Size

    137 kB

    Total Files


    Last publish


    • khoapham96