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

@byu-oit/sim-vue-lib

v1.1.1

Published

SIM Vue Component Library

Downloads

1

Readme

Welcome to the Vue Component Library Starter Template

A template project for creating more vue component libraries

Introduction

It is highly recommended that you understand the material in the References section below before contributing to this component library.

In the menu to the left (click the menu icon), you will notice a few headings. These headings organize our components according to the Atomic Design pattern.

Atomic Design splits components in several categories among which are atoms, molecules, & organisms.

  • Atoms are the smallest of components in an application. They cannot be split into smaller pieces. This could be things like buttons, input fields, or text areas, etc. An atom on its own can't do anything but display information.
  • Molecules are built out of our atoms and perform some extended functionality. For example: an input and label atom may be combined into an "input molecule". The atoms may now interact with some functionality that the "molecule" component provides (e.g. clicking on the label focuses on the input field).
  • Organisms are composed of molecules and may provide functionality to the end user. For example: our input molecule combined with a button may provide a login feature which becomes the "login organism".

While building components:

  • DO NOT ask "How can I break make this component more abstract?"
  • DO ask "What features does my project/team require?"
  • DO ask "Where are the overlaps in the components we will provide?"

In summary, it can be easy to try to abstract too much and end up creating a feature that is never used

Getting Started

IMPORTANT: If you are just starting a new library, make sure to do the following:

  1. Change the name & description in the package.json file
  2. Update the .dependabot/config.yml with the right maintainer configuration.
  3. (Optional) Update the README title.

Adding Components

  1. Create a demo page in the pages directory. This page will show-off your new component and make it testable.
  2. Add the demo page to the layout/default.vue page (follow the example that's already there). This will make your demo page visible in the menu.
  3. Create a new component in the components directory under the respective category (see Atomic Design for more).
  4. Add a test file for the new component in the test/unit directory.
  5. Start Test Driven Development! You can run tests by first starting the development server (npm run dev) and then by running the cypress tests:
    • Headless: npm test
    • Cypress: npm test:open

NOTE: If you are unsure how to create any of the files mentioned above, try understanding/copying from the example test, demo, and component files already in this library.

Publishing & Consuming Components

Before publishing your components to NPM, you'll need to run the build process, which will cleanly copy only the relevant Vue files to the dist directory. Running NPM publish will only publish this directory and metadata files.

To consume components after publishing them, install the package in your project (npm i <package name>) and then import the components you need:

import Example from '@byu-oit/vue-component-lib-starter/dist/Example.vue'
@Component({ components: { Example } })
export default class MyPage extends Vue {}

References

Nuxt Documentation

Nuxt TypeScript Property Decorators

Atomic Design Book

Atomic Design Overview

Test Driven Development

Testing with Cypress

Cypress Documentation