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

@bequestinc/wui

v5.2.9

Published

1. Be sure to run yarn install and then yarn dev to spin up the project and be sure there aren't any errors. 2. When changing the version for release, you should change the version in the `package.json`. Then be sure to update both the `peerDependencies`

Downloads

2,909

Readme

Instructions on updating the version for this repo

  1. Be sure to run yarn install and then yarn dev to spin up the project and be sure there aren't any errors.
  2. When changing the version for release, you should change the version in the package.json. Then be sure to update both the peerDependencies as well as the devDependencies.

Local Testing Instructions

  1. Make whatever changes that you need to make.
  2. Download and install pnpm. Once installed run pnpm install and then pnpm build.
  3. Download and install yalc. Inside this repo run yalc publish. Take note of the package-name published to the store
  4. cd into the frontend directory of the repo that you are testing WUI with.
  5. Run yalc add package-name, this will create a .yalc directory with the package contents. Your package.json file should have been updated and have something like this: "@bequestinc/wui": "file:.yalc/@bequestinc/wui"
  6. We need to copy the contents of the local .yalc directory into our container. To do this add COPY .yalc /code/.yalc before the yarn install command is called inside of the frontend/Dockerfile.local file.

Troubleshooting Testing

There is a chance that you did everything correctly but you do not see the changes you made reflected. If that's the case you may need to clear any caching that docker has performed. This can be done by deleting the volume that contains the node_modules. To do that we need to do a few things, first you need to get the hash of the frontend container by running docker container ls. Once your have the name, run the following command and looks for the Mounts section: docker container inspect yourhash. Look at the entries in the Mounts section and find the entry that has a destination containing node_modules, note the name of this entry. Run docker volume rm volumehash. Rebuild your image docker compose build --no-cache, and run your containers, docker compose up, your changes should now be present