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

itbid-two-ui-kit

v0.0.3

Published

Librería de componentes vue para itbid

Downloads

5

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

itbid-desarrolladoresitbid-desarrolladores

Keywords

two-ui-kititbidvue

Readme

Itbid UI Kit

Introducción

En este documento vamos a intentar explicar de la forma más clara posible la estructura que tiene el proyecto y la forma de instalarlo en un proyecto externo.

Estructura de ficheros

La estructura de este proyecto debe cumplir ciertos requisitos.

  1. El código fuente del proyecto debe ir dentro de la carpeta src.
  2. Los componentes deben ir dentro de la carpeta components y cada uno debe tener su propia carpeta
  3. Todos los componentes deberán tener el mismo prefijo ib (ej. ibInput, ibAlert, ibDatepicker).
  4. Toda la documentación deberá ir dentro de la carpeta docs y su formato será Markdown
  5. Todos los componentes serán vue nativos y no se podrán utilizar librerías de terceros.