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

test-styles

v1.0.1

Published

TeamCore Commons Styles library

Readme

Styles

Proyecto que contiene los estilos de TeamCore reutilizables en diferentes aplicaciones

Project Architecture

El proyecto sigue la metodología ITCSS que indica se debe seguir una estructura de directorios basada en una pirámide invertida.

  • Settings: Declararemos las variables y los preprocesadores, y las situaremos en esta carpeta.
  • Tools: Los mixins y funciones, junto con los preprocesadores, irán en esta carpeta.
  • Generic: El código genérico del proyecto, el reset de CSS, el Normalize o tus propios estilos, son los que incluiremos en esta carpeta.
  • Element: Para los estilos que afectan a los elementos del HTML. No incluiremos el estilo para las clases.
  • Object: Aquí sí, incorporaríamos las clases y colocaríamos todo lo relacionado con el layout.
  • Components: Todo lo que afecte a los diferentes bloques de nuestro documento, navegador, botones, recuadros de utilidades, migas de pan, cabecera, buscador, botones sociales, etc., debería de ir en esta carpeta. Dependiendo de las necesidades que tenga el proyecto, la carpeta Components tendrá más o menos ajustes, como es lógico
  • Utilities: Para finalizar, en esta carpeta colocaríamos utilidades que sobrescriban estilos significativos (incompatibilidades con navegadores, por ejemplo).

Build

Run ng build styles to build the project. The build artifacts will be stored in the dist/ directory.

Publishing

npm publish

DOCUMENTACION (SASSDOC)

Para la generacion de documentacion

Run npm install sassdoc -g para intalar de manera global. Luego ejecute sassdoc ./src donde src seria la carpeta donde se encuentran nuestros styles.