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

carpet-component-library

v0.1.0

Published

LOOM is a component library for [CARPET](https://github.com/HTW-ALADIN/CARPET). It is built with Vue 3 and Vite.

Downloads

139

Readme

LOOM

LOOM is a component library for CARPET. It is built with Vue 3 and Vite.

GitHub Actions Workflow Status

Component catalog.

The available components are showcased in a Storybook. To run the Storybook locally, clone the repository, install all dependencies with npm i and then run npm run storybook.

Add components.

To add components to the library, create a new sub-directory in the src/components directory with the name of your new component. Eacg component should have its own .vue file for the rendering logic, a .ts file for the business and statemanagement logic (documented with JSDoc-Strings - docs will be built automatically), a .stories.ts file for the visual component documentation in Storybook and a .spec.ts file for unit tests. Vue-components should be written as a SFC (Single File Component) with the composition API. The business logic should be encapsulated in a class that extends from the BaseComponent class in the src/components/BaseComponent.ts. This class provides the component with reactive properties and methods to update them. The entire state of the created component should be handled and exposed via those methods. To include the component in the npm-package, it has to be exported in the index.ts file in the src directory.

Releases and Commit Schema

This repository follows the ConventionalCommits-Schema. This means that every commit should follow this schema:

<type>[optional scope]: <comment>

<long description>

<word-token> #<reference>

Example.

Releases are derived from the commit messages. The versioning is done automatically via Semantic Versioning.

Development

Recommended IDE Setup

VSCode + Volar (and disable Vetur).

Type Support for .vue Imports in TS

TypeScript cannot handle type information for .vue imports by default, so we replace the tsc CLI with vue-tsc for type checking. In editors, we need Volar to make the TypeScript language service aware of .vue types.

Customize configuration

See Vite Configuration Reference.

Project Setup

npm install

Compile and Hot-Reload for Development

npm run dev

Type-Check, Compile and Minify for Production

npm run build

Run Unit Tests with Vitest

npm run test:unit

Lint with ESLint

npm run lint