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

claims-ui1

v1.0.14

Published

A UI application for the Holista project, bootstrapped with [Vite](https://vitejs.dev/) following React TS template.

Downloads

18

Readme

Claims Form UI with React

A UI application for the Holista project, bootstrapped with Vite following React TS template.

Prerequisites

  • Node.js v20.11.0 or higher
  • npm v10.3.0 or higher
  • ESLint and Prettier extensions in your code editor of choice

Getting Started

Instructions on how to install, configure and run the project.

  1. Clone the repository.
  2. Make sure, you have the correct version of node and npm installed in your system. The versions are specified in the engines in package.json.
    We recommend using nvm for switching node versions. If you have nvm installed on your system, you can make use of nvm use command to switch the correct node version. It'll read the version set in .nvmrc file. (Note: nvm use cmd does not work on a windows machine. You may need to do it manually with nvm use <version>)
  3. Install the dependencies with npm install.
  4. Configure the environment variables.
  5. Start the server with npm run dev.

Environments

Create a folder named environments in the root directory. All the env files are to be kept inside this folder.

To run the app locally pointing local API server, copy the contents from .env.sample file into a new file env.localdev (placed inside /environments) and fill the values (Get the values from your peer devs) and run the following command.

npm run localdev

Similarly, to run the app locally pointing DEV server, you need to populate .env.dev file and run the following command.

npm run dev.

This app supports five enviroments: local, dev, qa, uat and prod.

Building the app:
npm run build:dev -> builds the app for DEV env (.env.dev)
npm run build:qa -> builds the app for QA env (.env.qa)
npm run build:uat -> builds the app for UAT env (.env.uat)
npm run build:prod -> builds the app for PROD env (.env.prod)