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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@international-energy-agency/vue-ui

v2.0.5

Published

Reusable Vue UI components that match IEA.org design system and behaviors.

Downloads

390

Readme

IEA Vue UI Components

[[TOC]]

Using the component library

Installation from GitLab

To install the library from the GitLab NPM registry you first need to set up NPM locally to use it. First set the registry with

npm config set @international-energy-agency:registry https://gitlab.com/api/v4/packages/npm/

Then set your auth token with

npm config set '//gitlab.com/api/v4/packages/npm/:_authToken' "<your_token>"

(Contact your GitLab admin or generate a token with read_registry permissions from Settings -> Repository on GitLab.)

You should now be able to:

npm install @international-energy-agency/vue-ui

Including UI components in your project

import { StyledButton } from "@international-energy-agency/vue-ui";

Including map components in your project

import { MapGetter } from "@international-energy-agency/vue-ui/maps";

(Requires mapbox-gl as peer dependency)

Including Highcharts components in your porject

import { options } from "@international-energy-agency/vue-ui/highcharts";

For now, no peer dependencies as it's just an options object. But in future may require Highcharts. Options can be used with higcharts-vue to provide sensible defaults. @iea/data-charts is now deprecated.

Development

Nodenv

We use nodenv to keep our node version consistent. When it is installed, it should automatically use the correct version. To verify this, you can run nodenv version and verify that it matches the contents of .node-version

If it doesn't match, run:

nodenv update
nodenv install
nodenv version

Project setup

npm install

View storybook locally

npm run storybook

View demo locally

npm run demo

Go to http://localhost:5173

To use the local version of vue-ui in a project using the data browser boilerplate

This can be helpful if you want to test local changes to a component in a project as well as in the storybook.

  1. In the data project, change the vue-ui dependency to point to your local version of this repo. For example, if both repos are cloned into in the same directory:
    "@international-energy-agency/vue-ui": "file:../vue-ui",
  2. In the data project, reinstall dependencies
    npm install
  3. In the data project, in vite.config.js, add "@international-energy-agency/vue-ui" to the array build.rollupOptions.external.
  4. In vue-ui (this project) build the package while watching for changes
    npm run build-watch
  5. In the data project, run the dev server with --force so that vite ignores its cache
    npx vite --force

Note: do not commit these changes to dev or main, since they are only to help with local development.

Releases

On a new branch:

  1. Increment the version number in package.json, following semver.
  2. Reinstall npm packages
    npm install
  3. Update the changelog.
  4. Commit and push your changes.
  5. Make an MR and merge to main