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

kf-kit

v1.0.8

Published

This template should help get you started developing with Vue 3 in Vite with Alkfaeel Module Federation.

Downloads

18

Readme

KF_UI_KIT Template

This template should help get you started developing with Vue 3 in Vite with Alkfaeel Module Federation.

How To Start

First You Should Change The Name Property Inside The package.json File Into Your Current Feature Name

	//package.json
{
	//From
	"name": "template",
	//TO
	"name": "feature_1",
    //..
    //other props
}

Second You Must Also Do This Inside of The .env File And Change The APP_NAME.

Exporting Components

To Export Components. simply go to vite.config.mts and heading to loader variable. and add which component(s) you wish to export. please note this support Wildcard characters * ex to load every vue component inside the src folder and excluding tests

	const exported = await Loader([
		"./src/**/*.vue",
	],
		[
			"./src/components/__tests__/*",
		])

Exporting Routes

There's 2 files that need to be changed when it come to exporting your routes. src/router/routes.ts and src/router/nav.ts. you most export a single route in routes.ts and have Passthrough.vue as its component and have child routes as feature routes. There will be NO empty path child. Use "home" Instead

ex:

import PassThrough from "@/components/PassThrough.vue";

const routes = {
	// Name will be used in 18n. ensure proper naming scheme
	name:"feature1",
	path:"feature1",
	component:PassThrough,
	children:[{
		//child route names Should Also be 18n Friendly
		//feature1/home
		name:"feature1-home",
		path:"home",
		component:HomeView
	},
	{
		//feature1/about
		name:"feature1-About",
		path:"about",
		component:AboutView
	}]
} as RouteRecordRaw
export default routes;

And for the nav.ts file. it should serve as application catalog. with one SideBarNav Object with every feature section present as SideBarNavChild ex

import type { SideBarNav } from "@t/routeTypes";
export default {
	//Title Name will be used in 18n. ensure proper naming scheme
	title: "feature1.title",
	//Only Add if There's no child sections. 
	route: "/feature1/home",
	icon: "mdi-star-circle-outline",
	children: [
		//child nav bar object title Should Also be 18n Friendly 
		{ title: 'feature1.home', route: "/feature1/home", icon: "mdi-bullet-point" },
		{ title: 'feature1.home', route: "/feature1/about", icon: "mdi-bullet-point" }
	],
} as SideBarNav

I18n

Ensure every language locale file have a root element for the name of the feature you working on.

ex

{
	"feature1":{
		"home":"ميزة رقم واحد",
		"about":"عنا",
	}
}

Settings

Ensure You Have A Keybinding for typescript.restartTsServer So Whenever You Add New Types You Referesh With The Hotkey Instead of Closing and Re-Opening VSCODE.