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

@dharun235/doc-editor

v9.3.0

Published

Kibana plugin for editing and saving index values through forms.

Readme

docEditor

Kibana plugin for editing and saving index values through forms.

Package

  • npm package name: @dharun235/doc-editor
  • GitHub release artifact: docEditor-9.3.0.zip

Requirements

  • Use Kibana 9.3.0.
  • Keep this plugin on the same Kibana version as the host repo.

Local setup

  1. Clone Kibana.
git clone --filter=blob:none https://github.com/elastic/kibana.git
cd kibana
  1. Fetch the appropriate tag. Here it is 9.3.0
# First, fetch the tags if they aren't visible
git fetch --tags

# Checkout the exact release
git checkout v9.3.0
  1. Verify the version
grep '"version"' package.json
  1. Put this plugin folder inside the Kibana repo at kibana/plugins/docEditor.
  2. From the Kibana repo root, run:
yarn kbn bootstrap
  1. Start Kibana from the Kibana repo root:
yarn start
  1. For plugin UI development, run this in the plugin folder:
yarn dev --watch

Where to change code

  • public/: UI code, forms, components, and client-side feature changes.
  • server/: backend routes, server logic, and data handling.
  • common/: shared types, config, and code used by both public and server.
  • kibana.json: Version control of kibana and required plugins for the docEditor plugin

If you are adding a new feature, first decide whether it belongs in public, server, or common, then update the matching files there.

Build the plugin

Build the distributable zip from the plugin folder:

yarn build

The build output is created under build/ and should match the Kibana version, for example:

build/docEditor-9.3.0.zip

Publish

  • Package: run npm publish --access public from this folder after a successful build.
  • GitHub release: upload build/docEditor-9.3.0.zip as the release asset for the matching tag.

Copy to the remote server

Copy the zip to the remote machine:

scp build/docEditor-9.3.0.zip [email protected]:/tmp/

Then SSH in:

ssh [email protected]

Install the plugin inside the Kibana directory on the server:

sudo bin/kibana-plugin install file:///tmp/docEditor-9.3.0.zip

Restart Kibana:

sudo systemctl restart kibana

Typical change flow

  1. Edit the plugin files.
  2. Run yarn dev --watch while developing.
  3. Rebuild with yarn build.
  4. Copy the new zip to the server.
  5. Reinstall the zip and restart Kibana.

Note

  1. Ensure kibana version, version mentioned inside kibana.json and elasticsearch is same