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

vue2-sub-app

v1.0.2

Published

Make any component can be used as the Root-like component.

Downloads

5

Readme

Vue2-Sub-App

English | 简体中文

When I was developing a company project using Vue2, because of the card-style development, each component can be individually packaged into a JS resource that is loaded into the current page via the card loader. When the card functionality is particularly complex (so complex that it can stand alone as an application), I want to get the current card root component instance in the descendant component of the current card (Similar to $root attribute), and components like RouterLink and RouterView have to take a different approach. Of course, these can be completely simulated by provide + inject, v-if, etc. However, I wanted to make it simpler, so here it is!

Install

# npm
npm install vue2-sub-app --save

# yarn
yarn add vue2-sub-app

# pnpm
pnpm install vue2-sub-app

Usage

Full Import

// main.js
import Vue from 'vue'
import Vue2SubApp from 'vue2-sub-app'

Vue.use(Vue2SubApp)

new Vue({
  /* ... */
})

Manually Import

<script>
import { defineSubRoot, SubRouterLink, SubRouterView } from 'vue2-sub-app'

export default defineSubRoot({
  components: { SubRouterLink, SubRouterView },
  props: {},
  data() {
    return {
      /* ... */
    }
  },
  methods: {},
})
</script>

APIs

defineSubRoot(config)

config: component option object.

The current component is defined as a child-root component, and all descendant components of the component can get an instance of the current component through this.$subRoot.

<!-- Parent.vue -->
<template>
  <Child />
</template>
<script>
  import Child from 'Child.vue'

  export default defineSubRoot({
    components: { Child },
    props: {},
    data() {
      return {
        /* ... */
      }
    },
    methods: {},
  })
</script>
<!-- Child.vue -->
<script>
  export default {
    created() {
      console.log(this.$subRoot) // this.$subRoot == the instance of Parent.vue
    },
  }
</script>

Options

isSubRoot

type: boolean

If Manually Import is used, configure this property in the exported component options to make the current component a child-root component.

export default {
  isSubRoot: true, // <---
  components: {},
  props: {},
  data() {
    return {}
  },
  methods: {},
}

subRoutes

type: Array<{ path: string, component: VueComponent }>

Configure subrouting information in the exported component options.

export default defineSubRoot({
  subRoutes: [
    {
      path: '/child-one',
      component: () => import('./components/ChildOne.vue'),
    },
    {
      path: '/child-two',
      component: () => import('./components/ChildTwo.vue'),
    },
  ],
  props: {},
  data() {
    return {
      /* ... */
    }
  },
  methods: {},
})

Instance

$subRoot

type: VueComponent

The child-root component instance closest to the current component.

$subRoute

type: SubRoute

The current subroute.

Props

$subRoute.path

Location of the current subroute.

$subRoute.params

Parameter of the current subroute.

$subRouter

type: SubRouter

The subrouter instance.

Methods

$subRouter.push(path, params?)

Navigate to the new subrouting location.

$subRouter.replace(path, params?)

Replace the current subroute location.

$subRouter.pop()

Back up to the next subroute.

Components

SubRouterLink

Props

to

type: string

The location of the target subroute.

tag

type: string

default: "a"

Specify which tag <SubRouterLink> is rendered to.

SubRouterView

Renders the component corresponding to the current subroute.