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

access-watch-ui

v2.3.4

Published

The Access Watch User Interface

Downloads

40

Readme

Build Status Greenkeeper badge

Usage

  • npm start: Runs a webpack dev server. Point browser to http://localhost:8080/main.
  • npm run lint: Runs eslint. This has to pass for CI to be successful.
  • npm test[:watch]: Runs tests. This has to pass for CI to be successful.
  • npm run build[:staging]: Builds for production, :staging is unminified
  • npm run prettier[|:watch]: Runs prettier

Environment variables

Environment variables are read during build time and injected by webpack.

  • API_BASE_URL=http://127.0.0.1:8000/1.0/etc: API base url (default: "http://localhost:3000")
  • NODE_ENV=production: (default: "")
  • WEBSOCKET_BASE_URL=ws://access.watch:8888: (default: "ws://localhost:3000")

Development

If you are developing on the project, you may find yourself wanting to modify some components coming from the shared components library access-watch-ui-components. To install node_modules for both projects, you can lerna bootstrap. You can easily link the dependency with lerna (lerna link) to see your modifications in the main ui.

Publishing

To publish a new version to npm, you should use lerna publish. Though in most cases, you will only have modified the UI itself, not the access-watch-ui-components package. In such case, you want to only publish this package. You can do so with lerna publish --scope access-watch-ui.