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 🙏

© 2025 – Pkg Stats / Ryan Hefner

vue-sass-cli

v0.1.3

Published

vue-sass-cli 脚手架

Readme

vue-sass-cli scaffold

vue-sass-cli 脚手架

usage:

Generate static-html-sub-compile directory structure.

    vue-sass --template=simple-template.d ${component-name}
    # OR
    vue-sass --template=template.d ${component-name}

    # If you special no template like below line, the template.d was used by default.
    vue-sass ${component-name}

Of couse, you can write your-template.d and, gen folder like this:

    vue-sass --template=your-temp\nlate.d ${component-name}

Directories will be generated:

component-name

componentName.js.js

componentName.js.js is the render js file in dirname webstorm entry;
componentName.js.js will generate a single html with it's own asserts directory in dist folder(configured as default output directory by default.)

component-name.scss

component-name.scss just like this:

    @import "./**/*.sass";

component-name.vue

component-name.vue is the main vue file of this component,
In order to build separate static html with it's assert correctly for every component,
I suggest you to keeping only one vue file in current folder, When any sub component is need to create, just run this, which is very eary:

    vue-sass sub-cpomonent

.stable

All stable file is better to put in this dir, which would be less modifed.

.stable/component-name.sass

component-name.sass would be edit as this component's own style rule.
Of cause, it will follow the sass sytax, which one don't need bracket qoutes (大括号).
If you are interesting in this 'vue-sass-cli', may you like this sytax, too.

.stable/component-name.html

component-name.html will be the template of separate dist entry html.

And component-name.html wouldn't work for the parent (dir's) component, since it's own template html file will be valid.

In order to render vue component correct,
you must make sure the div element in template.html is the same as the component.js mount point.

Everything is easy, isn't it?

Enjoy it !