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

vues

v0.5.20

Published

The quickest way to run vuejs client side (inspired by next.js, nuxt.js and vbuild).

Downloads

112

Readme

The quickest way to run vuejs client side (inspired by next.js, nuxt.js and vbuild).

Introduction

Quickstart

$ yarn global add vues
$ vues init project
$ cd project
$ yarn dev

Done!!! You're now running vuejs.

Folder Structure

projectDir/
|
|-- filters/
|
|-- layouts/
|
|-- stores/
|
|-- views/

vues.config.js (click to toggle)

{
  title: 'My App'
}

{{ title }} will be replaced by the title in your vues.config.js and {{ viewTitle }} will be replaced by the title option in your /views .vue file.

{
  titleTemplate: '{{ title }} | {{ viewTitle }}'
}
import { resolve } from 'path'

{
  srcDir: resolve('./src')
}

Some node modules may require the need to be processed by babel-loader.

{
  include: ['some-node-module']
}

Vues will load environment variables from .env and .env.[process.env.NODE_ENV] files. If you want access to them via process.env inside your vuejs project just and them to your envs array.

{
  envs: ['PUBLIC_KEY']
}

You will now have access to process.env.PUBLIC_KEY inside your vuejs project.

You can completely customize vue-router using any of the options available at https://router.vuejs.org/en/. If you make the router option a function, you will be able to access the context of the router file.

{
  router () {
    return {
      history: null, // cordova can't handle html5 browser history
      routes: [
        { name: 'index', path: '/', component: require('~/views/login') },
        // You have access to LoginView due to this being executed in the context of the router file.
        { name: 'logout', path: '/logout', component: LoginView }
      ],
      // You even have the option to use the routers beforeEach method.
      beforeEach (to, from, next) {
        // some code
      }
    }
  }
}

Just like the router you can use this to completely customize vuex. It may also be turned into a function, which will the get executed in the context of the store.js file.

{
  store: {
    plugins: [require('vuex-persistedstate')]
  }
}

We use core-js under the hood, the following are used by default:

{
  polyfills: ['promise', 'array/includes', 'string/includes', 'object/entries']
}

Default babel config used:

{
  babel: {
    presets: ['vue-app']
  }
}
{
  meta: [
    { name: 'mobile-web-app-capable', content: 'yes' }
  ]
}