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

@rolyp/fluid

v0.2.10

Published

Fluid

Downloads

15

Readme

Transparent, self-explaining data visualisation

purescript

Recent activity

(W indicates a Wrattler issue.)

| When | Activity | Issue(s) | | --- | --- | --- | | 15 May 2020 | Update f.luid.org | 289 | | 2 April 2020 | Fluid plugin running in Binder | W279 | | 10 March 2020 | Start on PureScript migration | 279 | | 22 February 2020 | Make repository public | | 17 February 2020 | Host demo online at f.luid.org | 127 | | 30 January 2020 | Display image in Wrattler output pane | W222 | | 21 January 2020 | Initial meeting with Meng Wang and Minh Nguyen at Bristol || | 26 November 2019 | Demo for Wrattler workshop for DSTL || | 25 November 2019 | First pass over nested coordinate frames and “domain units” | 183, 121, 180, 112 | | 19 November 2019 | Stacked bar, grouped bar and multiline chart examples | 110, 250 | | 4 November 2019 | Merge with Wrattler develop | 247 | | 25 October 2019 | “Swap node” proof-of-concept | 237 | | 21 October 2019 | Basic delta-visualisation for IC 2019 presentation | 220, 225, 230, 232, 235, 238 | | 5 October 2019 | Reinstate execution indexing | 213, 214 | | 20 September 2019 | Import data from another Wrattler cell | 193 | | 15 September 2019 | Moved slicing annotations from values to traces | 204 | | 31 August 2019 | Preliminary Wrattler integration | 192 | | 30 August 2019 | Publish as npm library | 192 || 20 August 2019 | Demo to Luke Marsden of Dotscience || | 20 August 2019 | Demo to Luke Marsden of Dotscience || | 18 July 2019 | Demo to REG interview panel || | 17 July 2019 | Demo to Prodo || | 29 June 2019 | Migrate to Nearley parser for improved error-reporting | 190 | | 25 June 2019 | Demo for HPI Software Architecture Group|| | 18 June 2019 | Preliminary design for linking visualisations | 164, 188 | | 10 June 2019 | Library code for axes | 53, 111 |

In progress/forthcoming

| When | Feature/change | Issue(s) | | --- | --- | --- | | March | List comprehensions, arrays | 277, 276 | | March | Table view | 121, W269 |

Possible submissions

| Deadline | Venue | | --- | --- | | 2 Aug 2019 | LIVE 2019 | | 2 Aug 2019 | IC 2019 :heavy_check_mark: | | 5 Dec 2019 | Eurovis 2020 | | 3 Mar 2020 | ICFP 2020 | | 15 Apr 2020 | OOPSLA 2020 | | ~10 July 2020 | POPL 2021 |

Installation

  • Ensure you have a recent version of nodejs. Then run yarn install.

  • To run the tests in debug mode with Chrome, run npm run browser-test.

  • To start the UI, run npm start and open a browser at http://localhost:8082/.

LambdaCalc