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

mui-clone

v1.8.8

Published

this is a recreation of material ui using atomic-library-core

Downloads

39

Readme

Mui Clone

this is a "clone" of material ui using atomic-library-core. it's a recreation of the most components

differences

in this package you need to replace "variant" with "type" and "color" with "subType". for instance

    <Btn type="filled" subType="primary">Click here</Btn>
    <Btn type="ghost" subType="success">Click here</Btn>

types

sub types

Note: if the component is an input, you can use inputType to set the type of the input

<Btn component="H1" >click</Btn>
//instead of using
<Btn component="h1" >click</Btn>
//or
<Avatar component="Button" >click</Avatar>
//instead of using
<Avatar component="button" >click</Avatar>

Examples

import { Btn, BtnGroup, Checkbox, ...rest } from "mui-clone"

    <Btn>default</Btn>
    <Btn type='filled' subType='primary'>Click here</Btn>
    <Btn type='ghost' subType='success'>Click here</Btn>
    <Btn type='smooth' subType='danger'>Click here</Btn>
    <Btn type='text' subType='secondary'>Click here</Btn>

    <BtnGroup>
        <Btn>Click here</Btn>
        <Btn type='ghost' subType='success'>
            Click here
        </Btn>
        <Btn type='smooth' subType='danger'>
            Click here
        </Btn>
        <Btn type='text' subType='secondary'>
            Click here
        </Btn>
    </BtnGroup>
    <BtnGroup fullRounded mT='10px' type='text' subType='success' >
        <Btn>Click here</Btn>
        <Btn>Click here</Btn>
        <Btn>Click here</Btn>
    </BtnGroup>

    <Checkbox />
    <Checkbox defaultChecked />
    <br />
    <Checkbox disabled />
    <Checkbox disabled checked />
    <br />
    <Checkbox label='label' />
    <Checkbox>label</Checkbox>
    <br />
    <Checkbox subType='success' />
    <Checkbox subType='danger' />
    <br />
    <Checkbox colorCheck='orange' />
    <Checkbox colorCheck='brown' />
    <br />
    <Checkbox flowRowReverse>Terms</Checkbox>

    <RadioGroup
        value={radioValue}
        onChange={(e) => setRadioValue(e.target.value)}
        subType='success'
    >
        <Radio value='label 1' label='label 1' />
        <Radio value='label 2'>label 2</Radio>
    </RadioGroup>

Status of components

in the following tables i expose information about the components with the categories: component, status and description.

Note: although many of them have the status "done", this being the first version, the components are not perfect and with some missing functionalities.

Note: the "not necessary" state means the component can be easily recreated by atomic-library-core components

Inputs

data display

feedback

surfaces

navigation

layout

utils

this section is different to the original, and is stil in process