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

@frekuy_inriver/html-templates-vue

v1.0.35

Published

This library is distributed as a NPM package: @frekuy_inriver/html-templates-vue

Readme

HtmlTemplatesVue

This library is distributed as a NPM package: @frekuy_inriver/html-templates-vue

This library contains visual components coded in Vue.js, as well as some useful code that makes interaction with Vuex smoother.

What belongs here

Visual components generic enough to be useful to many HTML templates. These may not contain any logic beyond what contributes to the UI, instead being extendable to fit any situation. (Components like this belong in the "Components"-folder)

More specialized components for common use-cases, including some domain logic. These should be modularly defined and rely on generic visual components as much as possible. (Components like this belong in the "DomainModules"-folder)

Things relating to Vuex that makes development easier. (Code like this belong in the "StateManagement"-folder)

What doesn't belong here

Code unique to a very specific scenario.

How do I build it?

Please see the ASP.NET application named "Workbench", located in the same solution, which consumes these scripts directly. There you may debug your code during development and try out new things, without worrying about breaking things. The workbench is the developers playground and will/should never contain production code.

How to I release a new version

First of all, alter the version number in package.json. Then, run the NPM script called "npm-publish". You may also perform a dry run using "npm-publish-dry-run". If you are using Visual Studio, consider using the "Task Runner Explorer" for easy interaction.