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

@rtcamp/web-components

v1.1.6

Published

Reusable web components library

Downloads

102

Readme

Web Components by rtCamp

A collection of reusable, accessible, and customizable web components built with TypeScript, designed to simplify UI development across projects. This package is developed and maintained by the team at rtCamp and is publicly available for anyone to use and contribute.


✨ Why Use This Package?

Modern front-end development often involves repeated creation of the same UI patterns like accordions, sliders, tabs, modals, etc. This package offers a centralized solution:

  • Reusable: Write once, use across multiple projects.
  • 🧩 Modular: Use only the components you need.
  • ⚙️ Framework-Agnostic: Native web components that work with any JavaScript framework.
  • 💡 Developer-Friendly: Built with TypeScript and thoughtfully documented.
  • 🌍 Public & Open Source: Available on npm and GitHub for transparency, collaboration, and contribution.

📦 Installation

npm install @rtcamp/web-components

🚀 Usage

Importing Components

// Import a specific component (e.g., Accordion)
import '@rtcamp/web-components/build/accordion';

// Import global styles
import '@rtcamp/web-components/build/style.css';

// TypeScript usage
import { Accordion } from '@rtcamp/web-components';

You can now use the component as a custom HTML tag:

<rt-accordion></rt-accordion>

🧩 Available Components

We are continually expanding our collection. Current components include:

  • Accordion
  • Slider
  • Tabs
  • Modal
  • Lightbox
  • ...and more

Each component is designed with accessibility and customizability in mind.


📂 Component Structure

Each component is organized with the following conventions:

  • 📄 Each component folder contains a README.md file that explains:
    • Component usage
    • Code examples
    • Component's Attributes, Events and Methods
  • 🧪 A index.html file is included to demonstrate the working demo of the component.
  • 🧱 If a component has multiple elements, those are stored inside an elements/ subfolder for clarity and modularity.
  • 🧩 Each component folder has its own index.ts file, which should define and register custom elements via customElements.define(...).

🧩 Creating a New Component

If you're building a new component, please follow these steps:

  1. Export the main component class in the root index file:
    src/index.ts

  2. Import your component-specific styles into the main stylesheet:
    src/style.scss

  3. Test thoroughly to ensure it works across use cases and devices.

  4. Keep styles minimal: The component should only include styles essential for functionality (like layout, visibility toggles, etc.). Avoid opinionated visual styles, as each project may override styles to match its design system.

  5. Test thoroughly to ensure the component behaves correctly and is accessible across browsers and screen sizes.

  6. Once verified, contact a team member to publish the updated package so it's available for all users.

If in doubt, reach out to our team members actively working on this project for guidance.


🛠️ Local Development

Want to contribute or customize the components?

Getting Started

  1. Clone the repository:

    git clone https://github.com/rtCamp/web-components.git
    cd web-components
  2. Install dependencies:

    npm install
  3. Start the development server:

    npm run dev
  4. Build for production:

    npm run build
  5. Preview any component using a local server. Example:

    php -S localhost:3000
    # Now open http://localhost:3000/src/slider

🤝 Contributing

We welcome community contributions!

How to Contribute

  • 🐞 Report issues or suggest features via GitHub Issues.
  • 🛠️ Submit a pull request if you'd like to add or improve a component.

Contribution Guidelines

  • Follow existing coding conventions and folder structure.
  • Include TypeScript types and JSDoc comments.
  • Make sure the component works across browsers and is accessible.
  • Test before submitting a pull request.

📄 License

This project is licensed under the GPL-3.0-or-later. See LICENSE for more details.


💼 BTW, We're Hiring!