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

@crds_npm/crds-components

v1.3.52

Published

Custom Elements for Crossroads Church

Downloads

82

Readme

Built With Stencil Storybook

crds-components

This project contains custom web components developed for Crossroads' Church. See StencilJS for information on the framework.

The following components are made available via this library. Please see the README file for each, for more information on usage, available props, etc.

Environments

You need to export the following variables when building or running the project...

| Variable | Description | | ---------------------------- | --------------------------------------------- | | CRDS_ENV | Vault Environment (int for development) | | VAULT_ROLE_ID | Vault role ID - Obtain from DevOps | | VAULT_SECRET_ID | Vault secret ID - Obtain from DevOps |

To add new variables, please seek the help of DevOps if you are unfamiliar with the process.

Testing

If any new environment variables are introduced please add it to the secrets list in the settings for crds-components.

Run all

npm run test

Watch all

npm run test.watch

Individual spec/e2e (VS Code)

This will allow you to use standard VSCode breakpoints to do debugging of your spec or e2e test.

  1. Open the spec file you want to run/develop
  2. Select the debug option.
  3. In the drop down select Spec Test Current File or E2E Test Current File
  4. Click green play button

Note: check package.json for other test commands

License

This project is licensed under the 3-Clause BSD License