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

@fighting-design/fighting-theme

v1.1.0

Published

Fighting Design all style are settled here

Downloads

4

Readme

@fighting-design/fighting-theme

English | Chinese

🐳 Introduction

Theme style directory of fighting-design

🦩 Catalog Description

├── config                Some style definitions common to components, such as type, etc
├── src                   Main style sheet storage directory of each component
├── index.scss            The main style entry file is also a package entry file
├── package.json          package.json
├── README.en-US.md       README.en-US.md
└── README.md             README.md

🚧 Rule

  • Create a new *.scss with the same component name in the src directory file to develop component style sheets
  • At the main entrance index.scss You need to import your new *.scss files are provided for use
  • Is not allowed in the style !important
  • The file names are connected by a short horizontal bar, and no uppercase letters are allowed
  • In the src/* directory, it is the *.scss file
  • In the config/* directory, there are some configuration variable files of components. The configuration files of components are all named var-component-name.scss. The global configuration file uses const-***.scss Naming

🐿️ Unique Style

Each component will have a unique style, such as f-button,f-icon, etc. In order to avoid style conflicts, you need to strictly restrict the pollution of its internal style or peer style to other components.

For example, in the FButton component, the round corner attribute can be configured through the round attribute. The pseudo code is as follows:

<button
  :class="[
  'f-button',
  { 'f-button-round': round }
  ]"
>
  按钮组件
</button>

Because there will be a unique class in a component, that is,f-button, then f-button should also be added in front of the f-button__round attribute to prevent style pollution.

Negative example:

.f-button {
  /*  */
}
.f-button__round {
  border-radius: 4px;
}

Positive examples:

.f-button {
  /*  */
}
.f-button.f-button__round {
  border-radius: 4px;
}

🦄 Import

The following methods can be used anywhere in the world

import '@fighting-design/fighting-theme'