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

@ifrc-cbs/reporting

v0.0.4

Published

CBS Reporting frontend React component

Downloads

17

Readme

CBS - Reporting

Standalone webapp running the Reporting bounded context in development mode. An NPM package will externally be published and added in the Navigation module, together with the rest of the bounded contexts.

Building and running

Install dependencies

$ npm install

Run locally

This will start a development server, using Parcel bundler, a faster and no-config alternative to Webpack.

$ npm start

Running NodeJS API server

The NodeJS API server (under development) provides a more fluent Restful API and also makes it much easier to write frontend end-to-end tests (using Nightwatch.js).

To start the server:

$ npm run node:server

Development

...

End-to-end Testing

This project has support for writing automated UI tests using Nightwath.js - an easy to use Node.js based end-to-end testing framework using the Webdriver API or Selenium.

Running the tests

The tests by default will run in Chrome (headless mode). Nightwatch will start/stop ChromeDriver automatically and also start/stop the Parcel development server and NodeJS API server as needed.

The NodeJS API server mocked the calls to the backend and returns JSON output directly, for convenience.

$ npm test

Writing tests

New UI tests should be added to test/src. For more information about writing tests using Nightwatch, please refer to the [Nightwath docs(http://nightwatchjs.org/guide).

Troubleshooting build issues

npm install fails

Sometimes running npm install will fail with unexpected, inexplicable error conditions. The errors are mostly related to babel-cli or npm itself. If this occurs, try the following:

  1. open package.json and delete the line which contains the @ifrc-cbs/common-react-ui dependency (make sure to delete the comma which precedes it);
  2. run npm install;
  3. add the line containing the @ifrc-cbs/common-react-ui dependency back and run npm install again.

Parcel bundler errors

Sometimes, particularly when changes in external components occur, running the development server (with Parcel) can produce errors. You can try:

  1. remove the .cache folder (this is where Parcel keeps its data for faster processing)
  2. restart npm run dev process.