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

brightspots-app

v0.0.7

Published

Main App Shell for the Brightspots Webapp

Downloads

2

Readme

Brightspots App - web

This project is the build using Piral. Thus, this is the app container that hosts Brightspots pilets that provide the actual application content to the end user.

Today, the pilets are:

  • Chat Pilet: Main app where all communication flows between the community.
  • Provider Admin Pilet: Admin portal for providers on the platform.

Development

Pre Requisites

  • node & npm
  • Firebase CLI: 7.12.1
  • Piral CLI: 0.10.2

Quickstart

When you are ready to develop a new feature, follow these steps:

  1. git checkout -b <NEW_FEATURE_BRANCH_NAME>. See feature branch naming conventions below.
  2. Write new code and test locally: piral debug
  3. Add your changes to git: git add .
  4. Commit your changes to the branch: git commit -m "[Gitlab Issue ID] Meaningful Message"
  5. Push your changes to your branch: git push
  6. Once you are done with your feature, open a merge request to the develop branch

Merge Requests

Please follow these steps to create a merge request. Always merge into the develop branch. The master branch is managed by the maintainers.

Feature Branch Naming Conventions

In order to maintain clarity on what is being worked on, please follow these conventions:

  • Identify the Gitlab Issue associated to the feature, if there is no issue create, create one first.

  • Use the Gitlab Issue ID as the start of the branch name, followed by a one to three word descriptor of the work.

    Example) "1-gitlab-ci-build": This means that it is Gitlab Issue #1 and that I am working on the gitlab ci build job for this work item.