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

@bambulabs/finedine-mobile-core-ui-kit

v1.9.17

Published

finedine mobile menu ui kit project

Downloads

292

Readme

FD-UI-KIT

A web development ui kit library for reactjs by finedinemenu's devteam

Please read this section before start to development.

First of all you have to install these plugins to your editor (vscode), but if you are using it another code editor or IDE install them for your them.

If you don't use one of these Code Editor/IDE please check is your EDITOR/IDE exist or not please install Editor Config plugin for your Code Editor/IDE.

Linter / Commit Messages

While developing this library you should take an attention to linter rules, all of your codes and commit messages, because you can't do any development without checking by rules.

Notice: Before commit to changes, HuskyJs checking these commit messages / linter rules

If you get a lint's error when you commiting a message, you can check for eslint linter rules or if you get an error because of your commit message you can check below commit message types and examples or you can check from Conventional Commits.

Commit-lint Types

Examples:

git commit -m "feat: button component added"
git commit -m "docs(readme): server link added"
  • build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
  • ci: Changes to our CI configuration files and scripts (example scopes: Circle, BrowserStack, SauceLabs)
  • chore: Updating packages,build project etc. (no production code change)
  • docs: Documentation only changes
  • feat: A new feature
  • fix: A bug fix
  • perf: A code change that improves performance
  • refactor: A code change that neither fixes a bug nor adds a feature, when refactoring a production code, eg. renaming a variable.
  • revert: A commit revert message
  • style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
  • test: Adding missing tests or correcting existing tests

For Documentation

We are using storybook to document the our ui kit

How to start development on this repo

To get this repo to your local development enviroment, run the below script in your terminal

git clone https://github.com/finedine/finedine-mobile-core-ui-kit && cd finedine-mobile-core-ui-kit && npm install && npm start

How to publish package on NPM

Before to publish package you should add NPM_TOKEN (access token) env to your local terminal or bash file.

For minor version

  npm run pub:minor

For patch version

  npm run pub:patch

For major version

  npm run pub:major