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

grafana_impex

v0.0.3

Published

Grafana import/export cli tool

Readme

grafana_impex

This is a grafana import/export tool that supports currently grafana v7.1.4 (82a235b54c) And the following resources:

  • Folders
  • Datasources
  • Dashboards

Can be used also with grafonnet to first compile json resources, then proceed and import them to grafana.

1. Requirements

1. Bash shell or NodeJS based on version used

2. Only If you want to use grafonnet

If you want to use grafonnet for generating grafana json based on templates, then have to do the following steps

  1. Clone in this dir the library grafonnet-lib, git clone https://github.com/grafana/grafonnet-lib.git --depth=1

  2. install jsonnet

2a. How To Use (NodeJS Required)

First install the node package globally:

npm install -g [email protected]

This will make available the command gimpex from all paths.

Then create a directory where you will store your grafana provisioning project.

mkdir grafana_provision
cd grafana_provision

Copy .env.dist in this github repository to .env in your created dir above, and adjust the credentials for grafana connection and auth.

  1. To export all resources like datasources, folders, dashboards from grafana instance:
gimpex export

Demo

  1. To import all resources to the instance specified in .env
gimpex import default

Instead of default you can specify the environment which you used to export.

For example ENV=prod gimpex export will use env file .env.prod and export at exported/prod instead of exported/default

Then you can import from prod exported to current connection (specified in .env) like

gimpex import prod

For adding secrets to datasources so they are fully configured during import see point 3.

2b. How To Use Only With Bash

See USE-WITH-BASH.md

3. Importing datasources with filled auth secrets

For this reason jsonnet is being used to compile templates to json files

See templates/datasources-credentials/example.jsonnet and templates/secrets.example.json

Very easy and straightforward, the json you specify in datasource-credentials folder should have json format with name of datasource you want to fill with credential (you can check that form exported folder, exported/datasources), then based on the datasource type fill the secrets which are read from the secrets.json file that you can generate however you want and do not store in git or anywhere.

4. Contributing/Local Development

See LOCAL-DEVELOPMENT.md

5. License

@Kristi Jorgji MIT Released under the MIT Licence. See the bundled LICENSE file for details.