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 🙏

© 2025 – Pkg Stats / Ryan Hefner

grasia-dash-components

v0.3.5

Published

Dash UI component suite

Readme

grasia-dash-components

Dash UI component suite for GRASIA projects.

Use it

If you just want to use any of the components offered by this suite, add it to your system with pip install grasia-dash-components and import it with import grasia_dash_components.

You can see a very basic example of its usage in usage.py or in https://github.com/Akronix/test_grasia_dash_components.

Hack it

If you want to hack with the code, keep reading.

# Install dependencies
$ npm install

# Watch source for changes and build to `lib/`
$ npm start

Go to this link to learn more about Dash plugins.

Play with the components

If you just want to play around with the available components that grasia-dash-components offers you, just follow the instructions below:

# clone git repo and enter there
$ git clone https://github.com/Grasia/grasia-dash-components && cd grasia-dash-components
# create a Python3 new virtual environment
$ virtualenv -p python3 venv/
# activate it
$ source venv/bin/activate
# and install dependencies
$ pip install -r requirements.txt
# generate metadata.json of the Components
$ npm run prepublish
# launch the playground
$ python usage.py

Feel free to modify usage.py source file and play with the different options of the components.

React demo server

For easy developing and testing of the react components, you can start up a demo development server:

$ npm run demo
$ open http://localhost:9000

You have to maintain the list of components in demo/Demo.react.js.

Code quality and tests

To run lint and unit tests:

$ npm test

To run unit tests and watch for changes:

$ npm run test-watch

To debug unit tests in a browser (Chrome):

$ npm run test-debug
  1. Wait until Chrome launches.
  2. Click the "DEBUG" button in the top right corner.
  3. Open up Chrome Devtools (Cmd+opt+i).
  4. Click the "Sources" tab.
  5. Find source files
  • Navigate to webpack:// -> . -> spec/components to find your test source files.
  • Navigate to webpack:// -> [your/repo/path]] -> grasia-dash-components -> src to find your component source files.
  1. Now you can set breakpoints and reload the page to hit them.
  2. The test output is available in the "Console" tab, or in any tab by pressing "Esc".

To run a specific test

In your test, append .only to a describe or it statement:

describe.only('Foo component', () => {
    // ...
})l

Testing your components in Dash

  1. Build development bundle to lib/ and watch for changes

     # Once this is started, you can just leave it running.
     $ npm start
  2. Install module locally (after every change)

     # Generate metadata, and build the JavaScript bundle
     $ npm run install-local
    
     # Now you're done. For subsequent changes, if you've got `npm start`
     # running in a separate process, it's enough to just do:
     $ python setup.py install
  3. Run the dash layout you want to test

     # Import grasia-dash-components to your layout, then run it:
     $ python my_dash_layout.py

Installing python package locally

Before publishing to PyPi, you can test installing the module locally:

# Install in `site-packages` on your machine
$ npm run install-local

Uninstalling python package locally

$ npm run uninstall-local