Git Product home page Git Product logo

yamada-ui / yamada-components Goto Github PK

View Code? Open in Web Editor NEW
12.0 12.0 11.0 1.77 MB

A collection of React UI components of the Yamada, by the Yamada, for the Yamada, built with Yamada UI.

Home Page: https://yamada-components.com

License: MIT License

Shell 0.26% JavaScript 1.96% TypeScript 97.78%
animation animation-css dark-mode emotion framer-motion reaactjs react responsive-design ui ui-components ui-design ui-library uikit yamada-ui

yamada-components's Introduction

Yamada UI

NPM Minzip MIT License NPM Downloads MIT License Github Stars MIT License

English | 日本語

Yamada UI is a React UI component library that streamlines the development of cutting-edge web applications and websites. This library offers a diverse range of components that can be easily combined to construct complex user interfaces, incorporating various features such as color modes and animations, which are not typically supported by other React UI component libraries.

Contents

Respect

Yamada UI has drawn a lot of inspiration from Chakra UI, MUI and Mantine UI. This has brought me wonderful experiences in my life. I am deeply grateful to Segun Adebayo and all the gods who have given me such experiences. And I love them.

Documentation

It's the https://yamada-ui.com website for the latest version of Yamada UI.

Features

  • Ease of Styling: Yamada UI contains a set of layout components like Box and Stack that make it easy to style your components by passing props.
  • Flexible & composable: Yamada UI components are built on top of a React UI Primitive for endless composability.
  • Animation: Yamada UI provides hooks that allow for easy declaration of animations. These hooks can be written similar to CSS animations and are supported by all components.
  • Color mode: Yamada UI makes it easy to set values for each color mode in the props of all components.
  • Theme switching: Yamada UI allows users to switch themes. Users can adapt their own themes and use web applications and websites.
  • Other features: Yamada UI comes with essential loading and notification features that are considered crucial for modern web applications and websites. This means you don't have to define them individually yourself.

Installation

To use Yamada UI components, all you need to install the @yamada-ui/react package.

$ pnpm add @yamada-ui/react

# or

$ yarn add @yamada-ui/react

# or

$ npm install @yamada-ui/react

@yamada-ui/table and @yamada-ui/calendar, among others, are not included with @yamada-ui/react. You will need to install them separately.

# Provide a convenient Table component using `@tanstack/react-table`.
$ pnpm add @yamada-ui/table

# Provide a convenient Calendar and datePicker, MonthPicker component
$ pnpm add @yamada-ui/calendar

# Provide a convenient Carousel component using `embla-carousel-react`.
$ pnpm add @yamada-ui/carousel

# Provide a convenient Dropzone component using `react-dropzone`.
$ pnpm add @yamada-ui/dropzone

# Provide a convenient Chart component using `recharts`.
$ pnpm add @yamada-ui/charts

# Provide a convenient Markdown component using `react-markdown` and `react-syntax-highlighter`.
$ pnpm add @yamada-ui/markdown

# Provide a convenient Icon component using `Lucide`.
$ pnpm add @yamada-ui/lucide

# a package for conveniently using `Font Awesome`.
$ pnpm add @yamada-ui/fontawesome

Usage

To get started with using the components, please follow the steps below:

  1. Wrap your application with the UIProvider provided
import { UIProvider } from "@yamada-ui/react"

const App = ({ children }) => {
  return <UIProvider>{children}</UIProvider>
}

export default App

Yamada UI supports light and dark modes by default

  1. Now you can start using components like so
import { Box, Text } from "@yamada-ui/react"

const Example = () => {
  return (
    <Box>
      <Text>ギャルのパンティーおくれーーーっ!!!!!</Text>
    </Box>
  )
}

CodeSandbox

Support

Please support this project with you or your organization. Your logo will appear here with a link to your website. We'll appreciate some support. [Contribute]

Organizations

Individuals

Contributing

Wouldn't you like to contribute? That's amazing! We have prepared a contribution guide to assist you.

If you're interested in contributing to the documentation, please refer to this contribution guide.

License

MIT © Hirotomo Yamada

yamada-components's People

Contributors

hirotomoyamada avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar

yamada-components's Issues

Add i18n

Subject

Add i18n

Description

Add i18n

Are you willing to participate in the development of this feature and create a pull request?

None

Add `Headers` Component

Subject

Add Headers Component

Description

Add Headers Component ( category Application UI)

How to create the component?

  1. make directory(lowercase, kebab-case) named by the component and index.ts in the directory
    ex) header > index.ts
  2. Happy Hacking!

please refer to contents directory, like Header > index.ts

Are you willing to participate in the development of this feature and create a pull request?

None

Add: Linter & Formatter

Subject

Add: Liner & Formatter

Description

Add Eslint & Pretter or Biome

Are you willing to participate in the development of this feature and create a pull request?

No

Add `Footer` Component

Subject

Add Footer Component

Description

Add Footer Component ( category Application UI)

How to create the component?

  1. make directory(lowercase, kebab-case) named by the component and index.ts in the directory
    ex) header > index.ts
  2. Happy Hacking!

please refer to contents directory, like Header > index.ts

Are you willing to participate in the development of this feature and create a pull request?

None

Add `Buttons` Component

Subject

Add Buttons Component

Description

Add Buttons Component ( category Application UI)

How to create the component?

  1. make directory(lowercase, kebab-case) named by the component and index.ts in the directory
    ex) header > index.ts
  2. Happy Hacking!

please refer to contents directory, like Header > index.ts

Are you willing to participate in the development of this feature and create a pull request?

None

Fix X icon

Provide the exact quote of the error or issue

The X icon should be X instead of blue bird.

Does the feature already exist? Please link to it.

No response

Are you willing to participate in fixing this issue and create a pull request with the fix?

None

PasswordInputのimport改行修正

Provide the exact quote of the error or issue

PasswordInputのimport文に改行があってコンポーネントがうまく表示されない

Does the feature already exist? Please link to it.

No response

Are you willing to participate in fixing this issue and create a pull request with the fix?

None

Add `Preview Component`

Subject

Add Preview Component

Description

Add Preview Component

Are you willing to participate in the development of this feature and create a pull request?

No

Change the directory structure of category

Subject

ディレクトリ構造

Description

カテゴリページのパスを/category/category-name/の構造に修正して、pageの生成はコンポーネントのディレクトリ構造から読み取って自動で生成

Are you willing to participate in the development of this feature and create a pull request?

yes

Add `Inputs` Component

Subject

Add Inputs Component

Description

Add Inputs Component ( category Application UI)

How to create the component?

  1. make directory(lowercase, kebab-case) named by the component and index.ts in the directory
    ex) header > index.ts
  2. Happy Hacking!

please refer to contents directory, like header > index.ts

Are you willing to participate in the development of this feature and create a pull request?

None

Change the directory structure of components

Subject

ディレクトリ構造

Description

コンポーネントの詳細ページのパスを/component/category-name/component-nameの構造に修正して、pageの生成はコンポーネントのディレクトリ構造から読み取って自動で生成

Are you willing to participate in the development of this feature and create a pull request?

None

Fix `eslint`

Subject

Fix eslint

Description

Fix eslint of current codebase.

Are you willing to participate in the development of this feature and create a pull request?

Yes

Add `Navbars` Component

Subject

Add Navbars Component

Description

Add Navbars Component ( category Application UI)

How to create the component?

  1. make directory(lowercase, kebab-case) named by the component and index.ts in the directory
    ex) header > index.ts
  2. Happy Hacking!

please refer to contents directory, like Header > index.ts

Are you willing to participate in the development of this feature and create a pull request?

None

Fix GitHub links

Provide the exact quote of the error or issue

GitHub links are currently https://github.com/hirotomoyamada/... but they should be https://github.com/yamada-ui/...

Does the feature already exist? Please link to it.

No response

Are you willing to participate in fixing this issue and create a pull request with the fix?

None

Add Hightlight Component

Subject

Add Hightlight Component

Description

Create a component following Hightlight component of yamada-docs.
Replace Preview component with Hightlight Component.
Remove Preview component.

Are you willing to participate in the development of this feature and create a pull request?

None

Add `Card Component`

Subject

Add Card Component

Description

Add Card Component

Are you willing to participate in the development of this feature and create a pull request?

No

Improve `Card` styles

Subject

Improve Card styles

Description

The Card is currently too simple, so I am going to improve it.

Goal:
image

Are you willing to participate in the development of this feature and create a pull request?

Yes

Fix vercel build error

Provide the exact quote of the error or issue

Error occurred prerendering page "/en/component/header". Read more: https://nextjs.org/docs/messages/prerender-error
Error: ENOENT: no such file or directory, open '/vercel/path0/contents/header/index.tsx'
    at Object.openSync (node:fs:596:3)
    at readFileSync (node:fs:464:35)
    at h (/vercel/path0/.next/server/pages/component/[component].js:1:3244)
    at /vercel/path0/node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/next/dist/compiled/next-server/pages.runtime.prod.js:25:4076
    at /vercel/path0/node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/next/dist/server/lib/trace/tracer.js:131:36
    at NoopContextManager.with (/vercel/path0/node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/next/dist/compiled/@opentelemetry/api/index.js:1:7062)
    at ContextAPI.with (/vercel/path0/node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/next/dist/compiled/@opentelemetry/api/index.js:1:518)
    at NoopTracer.startActiveSpan (/vercel/path0/node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/next/dist/compiled/@opentelemetry/api/index.js:1:18093)
    at ProxyTracer.startActiveSpan (/vercel/path0/node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/next/dist/compiled/@opentelemetry/api/index.js:1:18854)
    at /vercel/path0/node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/next/dist/server/lib/trace/tracer.js:120:103
Error occurred prerendering page "/en/component/navbar". Read more: https://nextjs.org/docs/messages/prerender-error
Error: ENOENT: no such file or directory, open '/vercel/path0/contents/navbar/index.tsx'
    at Object.openSync (node:fs:596:3)
    at readFileSync (node:fs:464:35)
    at h (/vercel/path0/.next/server/pages/component/[component].js:1:3244)
    at /vercel/path0/node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/next/dist/compiled/next-server/pages.runtime.prod.js:25:4076
    at /vercel/path0/node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/next/dist/server/lib/trace/tracer.js:131:36
    at NoopContextManager.with (/vercel/path0/node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/next/dist/compiled/@opentelemetry/api/index.js:1:7062)
    at ContextAPI.with (/vercel/path0/node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/next/dist/compiled/@opentelemetry/api/index.js:1:518)
    at NoopTracer.startActiveSpan (/vercel/path0/node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/next/dist/compiled/@opentelemetry/api/index.js:1:18093)
    at ProxyTracer.startActiveSpan (/vercel/path0/node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/next/dist/compiled/@opentelemetry/api/index.js:1:18854)
    at /vercel/path0/node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/next/dist/server/lib/trace/tracer.js:120:103

   Generating static pages (26/35) 
Error occurred prerendering page "/en/component/password-input". Read more: https://nextjs.org/docs/messages/prerender-error
Error: ENOENT: no such file or directory, open '/vercel/path0/contents/passwordinput/index.tsx'
    at Object.openSync (node:fs:596:3)
    at readFileSync (node:fs:464:35)
    at h (/vercel/path0/.next/server/pages/component/[component].js:1:3244)
    at /vercel/path0/node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/next/dist/compiled/next-server/pages.runtime.prod.js:25:4076
    at /vercel/path0/node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/next/dist/server/lib/trace/tracer.js:131:36
    at NoopContextManager.with (/vercel/path0/node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/next/dist/compiled/@opentelemetry/api/index.js:1:7062)
    at ContextAPI.with (/vercel/path0/node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/next/dist/compiled/@opentelemetry/api/index.js:1:518)
    at NoopTracer.startActiveSpan (/vercel/path0/node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/next/dist/compiled/@opentelemetry/api/index.js:1:18093)
    at ProxyTracer.startActiveSpan (/vercel/path0/node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/next/dist/compiled/@opentelemetry/api/index.js:1:18854)
    at /vercel/path0/node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/next/dist/server/lib/trace/tracer.js:120:103

 ✓ Generating static pages (35/35) 
> Export encountered errors on following paths:
	/component/[component]: /en/component/header
	/component/[component]: /en/component/navbar
	/component/[component]: /en/component/password-input
 ELIFECYCLE  Command failed with exit code 1.
Error: Command "pnpm run build" exited with 1

Does the feature already exist? Please link to it.

No response

Are you willing to participate in fixing this issue and create a pull request with the fix?

None

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.