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

@electronioncollider/epic-widgets

v0.1.1

Published

EIC EPIC widgets collection

Downloads

7

Readme

epic-widgets

Build Status codecov

EIC EPIC widgets collection

Installation

You can install using pip:

pip install epic_widgets

Or if you use jupyterlab:

pip install epic_widgets
jupyter labextension install @jupyter-widgets/jupyterlab-manager
jupyter labextension install @electronioncollider/epic-widgets

If you are using Jupyter Notebook 5.2 or earlier, you may also need to enable the nbextension:

jupyter nbextension enable --py [--sys-prefix|--user|--system] epic_widgets

Development

This plugin initially created with:
https://github.com/jupyter-widgets/widget-ts-cookiecutter

# First install the python package. This will also build the JS packages.
pip install -e ".[test, examples]"

# Run the python tests. This should not give you a few sucessful example tests
py.test

# Run the JS tests. This should again, only give TODO errors (Expected 'Value' to equal 'Expected value'):
npm test

When developing your extensions, you need to manually enable your extensions with the notebook / lab frontend. For lab, this is done by the command:

jupyter labextension install .
#or 
jupyter labextension install @electronioncollider/epic-widgets

For classic notebook, you can run:


jupyter nbextension install epic_widgets --py --symlink --sys-prefix 
jupyter nbextension enable epic_widgets --py --sys-prefix

Note that the --symlink flag doesn't work on Windows, so you will here have to run the install command every time that you rebuild your extension. For certain installations you might also need another flag instead of --sys-prefix, but we won't cover the meaning of those flags here.

Releasing your initial packages:

Prepare publishing tools for the first time:

pip install --upgrade pip
pip install setuptools wheel twine
  • Add tests
  • Ensure tests pass locally and on CI. Check that the coverage is reasonable.
  • Make a release commit, where you remove the , 'dev' entry in _version.py.
  • Update the version in package.json
  • Relase the npm packages:
    npm login
    npm publish --access=public
  • Bundle the python package:
    python setup.py sdist bdist_wheel
  • Publish the package to PyPI:
      
    twine upload dist/epic_widgets*
  • Tag the release commit (git tag <python package version identifier>)
  • Update the version in _version.py, and put it back to dev (e.g. 0.1.0 -> 0.2.0.dev). Update the versions of the npm packages (without publishing).
  • Commit the changes.
  • git push and git push --tags.