[ bsd3, program, visualization ] [ Propose Tags ]

Please see the README on GitHub at

[Skip to Readme]
Versions [faq],,,,,,,,,,,,,,,
Change log
Dependencies aeson (>=1.1 && <1.5), base (>=4.7 && <5), blaze-html (>=0.7 && <0.10), bytestring (==0.10.*), directory (>= && <1.4), filepath (==1.4.*), http-types (>=0.9 && <0.13), scotty (==0.11.*), text (==1.2.*), unordered-containers (==0.2.*) [details]
License BSD-3-Clause
Copyright 2019 Douglas Burke
Author Douglas Burke
Home page
Bug tracker
Source repo head: git clone
Uploaded by DouglasBurke at Sun Sep 8 19:40:18 UTC 2019
Distributions NixOS:
Executables vegaview
Downloads 1812 total (578 in the last 30 days)
Rating 2.0 (votes: 1) [estimated by Bayesian average]
Your Rating
  • λ
  • λ
  • λ
Status Hackage Matrix CI
Docs not available [build log]
Last success reported on 2019-09-08 [all 2 reports]


Maintainer's Corner

For package maintainers and hackage trustees

Readme for vega-view-

[back to package description]


I am not 100% convinced this is a worthwhile project, but let's see how it goes. You can think of it as "I want vega desktop but don't want to install an electron application, so decided to write an inferior product" project.

The aim is to make it easy to view Vega and Vega-Lite specifications - i.e. the JSON representing a visualization - as a visualization. It relies on Vega Embed to do all the hard work, and just provides a basic web server that will list the files in a given directory and, when selected, create the call to Vega Embed.


This is released under a BSD3 license.


The server - called vega-view - should be run from the directory containing the specifications to view. It then provides a web server on port 8082 that can be used to view them at the URL


Visualizations can either be viewed as their own "page", or inline, which may be more useful when you have multiple plots to view.

The aim is to be run in a a directory structure where most, if not all, the files are Vega or Vega-Lite specifications. This means that the web server tries to parse each file as JSON, which could cause memory- or time- issues if there are large non-JSON files in the directory tree.

GHC support

This is currently a very basic application, so will hopefully build against a wide variety of GHC installations. There has been /no/ testing on Windows.

Bugs and Issues

Please use the issues list to report any problems.