A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://npmjs.com/package/vuepress-plugin-dynamic-base below:

vuepress-plugin-dynamic-base - npm

vuepress-plugin-dynamic-base

Feature Motivation

The base of VuePress assumes that the user's website will always have the same public path with router base. but it's very likely that we need to set them separately. For example, you'd deploy HTML and assets on different servers.

See also:

Install

yarn add -D @vuepress/plugin-schema2md

Usage

module.exports = {

  plugins: [

    [

      'dynamic-base',

      {

        publicPath: 'your/custom/public/path',

        routeBash: 'your/custom/router/base',

      }

    ]

  ]

}

module.exports = {

  plugins: [

    [

      'dynamic-base', 

      {

        publicPath: process.env.NETLIFY_CI

          ? null

          : 'your/custom/public/path',

        routeBash: {

          'hostA': '/',

          'hostB': '/blog/',

        }

      }

    ]

  ]

}

It means that the publc path will be different acccording to the NEV you set, and the router base will be '/' when the host is hostA, and '/blog/' when the host is hostB.

Options publicPath routeBash Contributing
  1. Fork it!
  2. Create your feature branch: git checkout -b my-new-feature
  3. Commit your changes: git commit -am 'Add some feature'
  4. Push to the branch: git push origin my-new-feature
  5. Submit a pull request :D
Author

vuepress-plugin-dynamic-base © ULIVZ, Released under the MIT License.

github.com/ulivz · Twitter @_ulivz


RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4