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

@nfdi4plants/swate-components

v1.0.6

Published

Customizable React components for ontology annotation, based on Swate and the ARC.

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

kmutagenekmutagenebvennbvennhl_weilhl_weilbfrommerbfrommerfreymaurerfreymaurercmr248cmr248

Keywords

rdmontologytermreact

Readme

Components

Local Dev

Tests

npm test

Playground

npm start

Run Storybook

npm run storybook

Build Storybook

npm run build:storybook

Build Npm Package

npm run build

Build .NET Package

npm run build:net

Release

.NET

  1. Update version in ./src/Components.fsproj
  2. npm run build:net (creates tailwind style css and packs nuget package)
  3. Upload nuget package from ./src/bin/Releases

NPM

  1. Release normally and copy <new_version> from console output.
  2. npm version <new_version> --no-git-tag-version
  3. npm run build (transpiles with fable, creates tsc types, and bundles with rollup)
  4. (Due to #701) replace @layer base with @layer swt-base in dist/swate-components.css
  5. npm publish --access public --tag next (Use --tag next for prerelease)

Publish detailed

  1. go to main branch
  2. ensure latest commit is locally pulled
  3. Open powershell / cmd in swate root
  4. ./build.cmd release pre
  5. Wait for version editting. Write beta.XX where XX is the current beta version
  6. Wait for tests
  7. Confirm force push to nightly
  8. Wait a few minutes and check if gh-actions for release finished successfully: https://github.com/nfdi4plants/Swate/actions
  9. When the release is finished go to the main page of swate (https://github.com/nfdi4plants/Swate), and click on Releases on the left side (https://github.com/nfdi4plants/Swate/releases)
  10. Select the tag of the new release and click "Generate release notes", then click on "Publish release"