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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@progress/kendo-themes-html

v12.3.0

Published

A collection of HTML helpers used for developing Kendo UI themes

Readme

Kendo Themes HTML Components

A collection of HTML helpers used for developing Kendo UI themes.

Basic Usage

Authoring Tests

Reference Rendering

Create tests for the reference rendering for components and their features in /src/[component]/tests by using the HTML components to remove repetition:

  • Create the TSX test and use the respective HTML component src/[component]/tests/[component]-[scenario]-[platform].tsx (see reference)
  • Create the HTML template src/[component]/tests/[component]-[scenario]-[platform].html (see reference)
  • Make sure the compiled script is referenced in the HTML page ( see reference)

The output (.html) is updated as part of the CI build and committed automatically. Review the output in PRs for correctness.

Per-Suite Rendering

Follow the process established by your team to create and update reference tests. The test pages are typically created from live examples with some formatting and filtering applied.

The workflow can look like this:

  1. Create a runnable example, either for a new scenario or an existing reference demo.
  2. Wrap the actual example in a <div id="test-area" class="grid"> (see reference).
  3. Copy and reference the styles.css stylesheet in your example.
  4. Run the demo and copy the source code of the page.
    1. Either manually, by using the Pretty HTML tool or an existing page as a template.
    2. Or as part of the E2E test suite of the component using the snapshotMarkup helper from @progress/kendo-e2e.
  5. Create a new file following this name template: packages/html/src/[component]/[component]/[component]-[scenario]-[platform].html
  6. Create a PR and submit the new example.