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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@tagaddod/t-core-ui-kit

v1.0.19

Published

This is the core UiKit that should be used across all web apps in TAGADDOD

Downloads

4

Readme

tagaddod logo WEB-CORE-UI-KIT

This is the core UiKit that should be used across all web apps in TAGADDOD


Preview

visit StoryBook


How To Use

  1. In app root styles (index.css) import:

    • @import "@tagaddod/t-core-ui-kit/styles";

    • @import "@tagaddod/t-core-ui-kit/tailwindStyles";

  2. Import tailwindCSS Configs as follows:

    • export * as default from "@tagaddod/t-core-ui-kit/tailwindConfig";
  3. Import components as following:

    • import { Button } from "@tagaddod/t-core-ui-kit";

FOR TAGADDODIANS ; )

In case you are a TAGADDOD developer first of all welcome on-board 🥳. The following part should help you in enhancing, maintaining and developing new features, so please read carefully.

Create new Component Guide

  1. under lib/components create a folder with the name of your component and create the following files:

    • [_ComponentName_].tsx EX: Button.tsx

    • [_ComponentName_].test.tsx EX: Button.test.tsx

    • [_ComponentName_].stories.ts EX: Button.stories.ts

  2. To add custom styles

    You should build a custom tailwind plugin so follow the steps below:

    1. create new file uder lib/styles and name it tailwind.[_ComponentName_].js EX: tailwind.Button.js

    2. Then add the file to plugins array EX: plugins: [require("./tailwind.Button.js"), ...etc],

    *For more information about tailwindcss plugins read this blog post

  3. sds


$${React + TypeScript + Vite}$$

This template provides a minimal setup to get React working in Vite with HMR and some ESLint rules.

Currently, two official plugins are available:

Expanding the ESLint configuration

If you are developing a production application, we recommend updating the configuration to enable type aware lint rules:

  • Configure the top-level parserOptions property like this:
export default {
  // other rules...
  parserOptions: {
    ecmaVersion: "latest",
    sourceType: "module",
    project: ["./tsconfig.json", "./tsconfig.node.json"],
    tsconfigRootDir: __dirname,
  },
};
  • Replace plugin:@typescript-eslint/recommended to plugin:@typescript-eslint/recommended-type-checked or plugin:@typescript-eslint/strict-type-checked
  • Optionally add plugin:@typescript-eslint/stylistic-type-checked
  • Install eslint-plugin-react and add plugin:react/recommended & plugin:react/jsx-runtime to the extends list