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

carta-frontend

v4.1.0

Published

The browser-based frontend component of CARTA, a radio-astronomy visualization tool designed for the ALMA, the VLA and the SKA pathfinders.

Downloads

55

Readme

CARTA Frontend

The CARTA frontend is used in conjunction with the CARTA backend, and for general use a pre-built production frontend is usually installed alongside the backend automatically. However, a user may wish to install the frontend component separately in order to test beta versions, for example, or to develop it.

Pre-built production packages

The simplest way to install the frontend component is to use the pre-built production packages from NPM (for any OS with Node.js installed), our PPA (Debian packages for Ubuntu), or our RPM repository (for RHEL based systems).

NPM

Pre-built production frontends can be obtained from the npmjs.com carta-frontend repository.

If you have Node.js and npm already installed on your system, you can install a production frontend using the following command:

npm i carta-frontend

The files will be installed to your node-modules directory. For a system-wide 'global' installation (using the -g flag) this is located at /usr/lib/node_modules, whereas for a local user installation, it is located at $PWD/node_modules.

You can install specific frontend versions by appending @ plus the version number. For example,

npm i [email protected]
npm i [email protected]

The available versions are listed in the npmjs.com carta-frontend versions tab.

Alternatively, the pre-built production frontend can be downloaded directly without npm. For example,

wget https://registry.npmjs.org/carta-frontend/-/carta-frontend-2.0.0.tgz

The standalone tgz archive file extracts as package/build in your current directory.

You can start the CARTA backend with a non-default frontend by specifying its location with the --frontend_folder flag. For example,

./carta-backend --frontend_folder $HOME/package/build

PPA

A Personal Package Archive (PPA) is a third-party package repository for Ubuntu. We supply pre-built production frontends at the CARTAvis-team PPA on the Ubuntu Lauchpad.

To install the latest release version:

sudo add-apt-repository ppa:cartavis-team/carta
sudo apt-get update
sudo apt-get install carta-frontend

The Ubuntu package install location for the frontend is /usr/share/carta/frontend/.

The PPA also provides a carta metapackage which automatically installs the CARTA frontend and backend packages. In addition to the latest release versions, beta versions are provided in a parallel set of packages.

RPM

RPMs are for users of Red Hat Enterprise Linux (RHEL) and other Red Hat-based Linux distributions, e.g. CentOS. To install the latest release version, add the appropriate repository file depending on whether you are using RHEL7 (el7) or RHEL8 (el8):

sudo curl https://packages.cartavis.org/cartavis-el7.repo --output /etc/yum.repos.d/cartavis.repo

or

sudo curl https://packages.cartavis.org/cartavis-el8.repo --output /etc/yum.repos.d/cartavis.repo

Then the frontend component can be installed using yum or dnf :

sudo yum install carta-frontend

The RPM package install location for the frontend is /usr/share/carta/frontend/.

The RPM repo also provides a carta metapackage which automatically installs the CARTA frontend and backend packages. In addition to the latest release versions, beta versions are provided in a parallel set of packages.

Development

If you wish to modify or develop the CARTA frontend, you may build a production or non-production frontend from source. Here are the instructions to do so:

Prerequisites

The build process relies heavily on npm and nodejs, so make sure they are installed and accessible.

We recommend using Docker or Singularity to perform WebAssembly compilation. If neither is available, the Emscripten compiler (emcc version 2.0.14 recommended) needs to be available in the build environment. Installation instructions are available on the Emscripten homepage.

Build process (using Docker/Singularity)

Initialise submodules and install package dependencies:

git submodule update --init --recursive
npm install

WebAssembly libraries can be built with npm run build-libs-docker or npm run build-libs-singularity. Additional build steps (building WebAssembly wrappers, protocol buffer modules and compiling the Typescript code) are performed by npm run build-docker or npm run build-singularity. This produces a production build in the build folder.

To run a development build server, simply run npm run start.

Build process (without Docker/Singularity)

If your build environment does not have access to Docker or Singularity, WebAssembly compilation must be performed in an environment with access to the Emscripten compiler.

Initialise submodules and install package dependencies:

git submodule update --init --recursive
npm install

WebAssembly libraries can be built with npm run build-libs. Additional build steps (building WebAssembly wrappers, protocol buffer modules and compiling the Typescript code) are performed by npm run build. This produces a production build in the build folder.

To run a development build server, simply run npm run start.

Developer documentation

Automatically generated documentation can be found at cartavis.org/carta-frontend.

DOI