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

ahg-ui

v0.0.82

Published

React Components

Downloads

162

Readme

pipeline status coverage report

Primeiros passos

  • Entrar na pasta do ahg-ui
  • Instalar npm caso nao tenha
npm i
  • Caso acuse nos warning sobre libpng
  • Instalar com:
sudo apt install libpng-dev
  • Apos instalar a libpng, na pasta do ahg-ui dar os seguintes comandos:
rm -rf node_modules
rm -rf package-lock.json 
npm i
npm start

nao instalar o latest node

Adicionando o projeto

❯ npm i -D git+https://npm:[email protected]/git/ahg-ui#master
❯ npm i -D mini-css-extract-plugin

or add to package.json

  ...
  "devDependencies": {
    ...
    "ahg-ui": "git+https://npm:[email protected]/git/ahg-ui#master",
    "mini-css-extract-plugin": "^0.9.0",
    ...
  }
  ...

to use ahg-ui css files configure your webpack

...
const MiniCssExtractPlugin = require('mini-css-extract-plugin');
...
module.exports = {
    ...
    entry: {
      'output/folder/AhgUi': 'ahg-ui/build/AhgUi.css'
    },
    ...
    module: {
      ...
      rules: [
        ...
        {
            test: /\.css$/i,
            exclude: /(node_modules(?!(\/|\\)ahg-ui)|bower_components)/,
            use: [MiniCssExtractPlugin.loader, 'css-loader'],
        },
        ...
      ],
      ...
    },
    ...
    plugins: [
        new MiniCssExtractPlugin()
    ],
    ...
};

then

<link rel="stylesheet" type="text/css" href="output/folder/AhgUi.css" />

and

import { AhgTable, ... } from 'ahg-ui';

Uso

Documentação

Para ver a documentação dos componentes use:

❯ npm run styleguide:start
  • Styleguidist vai rodar em: (http://0.0.0.0:6060)

  • Temos por padrão onde sempre que um componente for criado, deve ser documentado, nesse espaço temos como documentar a funcionalidade, props que aceita, exemplos de uso e interações com outros componentes

Desenvolvimento

  • Para começar a trabalhar no projeto você vai usar:
❯ npm i && npm start
  • Apartir do npm start, o servidor de desenvolvimento estará rodando em http://localhost:5000

  • Para testar um componente novo criado, ou conhecer as funcionalidades em alguns componentes que já existem, estarão todos no showcase, disponível em: -> ahg-ui/src/showCase/ShowCase.js

  • Após alterar ou criar um componente, adicione suas alterações com: git add .

  • Registre suas alterações: git commit -m "DSW-XXXX - create a new beautiful component"

  • É necessário criar o build do projeto antes de enviar para a branch as alterações, você pde fazer isso dessa forma:

Build

❯ npm run build
  • Após o build, envie suas alterações para a branch de trabalho: git push origin DSW-XXXX