npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

vuepress-plugin-dynamic-base

v0.1.1

Published

Retrieve the time and space cost of using a dependency

Downloads

2

Readme

vuepress-plugin-dynamic-base

NPM version NPM downloads Node.js CI

Feature

  • Dynamic public path.
  • Dynamic route base.

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
# OR npm install -D @vuepress/plugin-schema2md

Usage

  • Simple usage:
// .vuepress/config.js
module.exports = {
  plugins: [
    [
      'dynamic-base',
      {
        publicPath: 'your/custom/public/path',
        routeBash: 'your/custom/router/base',
      }
    ]
  ]
}
  • Advanced usage:
// .vuepress/config.js
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

  • Type: string
  • Description: public path of webpack under the hood.

routeBash

  • Type: string | { [host: string]: string }
  • Description: base of vue router under the hood.

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