Socket
Book a DemoInstallSign in
Socket

@loophq/component-library

Package Overview
Dependencies
Maintainers
21
Versions
166
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@loophq/component-library

## Installation

2.4.4
latest
npmnpm
Version published
Maintainers
21
Created
Source

Loop component library

Installation

npm i -S @loophq/component-library

Usage

Components can be imported by importing the component individually:

import BaseCard from '@loophq/component-library/BaseCard';

This is preferred because it allows for better code-splitting

Other methods

Components can be imported via named imports:

import { BaseCard } from '@loophq/component-library';

To import all and register globally (not recommended), run this in your main.js:

import LoopComponents from '@loophq/component-library';

Vue.use(LoopComponents);

Project setup

npm i

Local component testing

npm run dev

Unit tests

npm run vitest

Compiles and hot-reloads docs for development

npm run storybook

Compiles and minifies component library

npm run library:build

Publishes a new version of the library

npm run library:publish -- <version>

Compiles and minifies docs

npm run build-storybook

Releasing

  • If this is your first time releasing, ask in the engineering team channel to be added to the loop npm organization. Make sure you log in to npm in your terminal as well.

  • On your machine, check out the branch you'd like to release. This can either be a feature branch or a release branch if you have multiple features to package together as a release. This branch should be PRed into main and be approved by a peer before releasing.

  • Compile the component library

    npm run library:build
    

    (Optional) Commit any file changes the build script made. This is not always necessary but when adding new components this will generally be necessary.

  • Figure out the version number this release will be. We follow SemVer, and the general rule of thumb is that if you're adding new components, bump the minor version, everything else should just bump the patch version. Major versions bumps are rare and should be a team decision.

  • Publish the library to npm. Make sure you are on the branch you intend to release, this will modify your package.json and you MUST be on a non-main branch for this to be mergeable.

    npm run library:publish -- <version>
    
  • Push all changes the build and release scripts made to Github.

  • In Github, merge the release branch into main.

FAQs

Package last updated on 05 Jun 2025

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts

SocketSocket SOC 2 Logo

Product

About

Packages

Stay in touch

Get open source security insights delivered straight into your inbox.

  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc

U.S. Patent No. 12,346,443 & 12,314,394. Other pending.