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 🙏

© 2026 – Pkg Stats / Ryan Hefner

der-componentes

v1.0.16

Published

Bliblioteca de compoenntes React que seguem o design system do DER/RO

Downloads

77

Readme

React - DER/RO Componentes

Bliblioteca de compoenntes React que seguem o design system do DER/RO.


Pré-requisitos

Possuir um projeto React; Ter instalado e configurado Tailwindcss;

1. Instalação

Instale a biblioteca no seu projeto utilizando o seguinte comando:

    npm install der-componentes

2. Configuração

No seu arquivo principal .css (main.css, app.css, index.css, etc), adicione:

    @import "tailwindcss";

    @source "../node_modules/der-componentes";

    ...

Isto faz com que o tailwind reconheça as classes utilitárias utilizadas nos componentes da biblioteca e aplique a estilização corretamente.

3. Uso

Em qualquer arquivo .js, .ts, .jsx ou .tsx, basta importar o componente ou hook que deseja utilizar.

Ex.:

    import { PrimaryButton, useData } from "der-componentes";
    const [data, setData] = useData({
        foo: "bar"
    });

    return (
        <PrimaryButton onClick={() => setData("foo", "bar2")}>Enviar</PrimaryButton>
    )

4. Componentes

Botões:

  • PrimaryButton
  • SecondaryButton
  • DeleteButton

Inputs:

  • Checkbox
  • InputLabel
  • InputText
  • Select

Icons:

  • MapPinIcon
  • PhoneIcon
  • ClockIcon
  • XIcon
  • ArrowLeftIcon
  • ArrowRightIcon
  • ArrowDownIcon
  • ListIcon

Hooks:

  • useData
  • useBreadcrumbs

Interface:

  • Header
  • Footer
  • Card
  • Modal
  • Table
  • TableHead
  • TabelaRow
  • TableData
  • TableFoot
  • Menu
  • Sidebar

5. Contribuindo

Para realizar contribuições, alterações, melhorias ou adição de novos componentes na biblioteca, recomenda-se que utilize o padrão de desenvolvimento sugerido.

  1. Clone o projeto no seu ambiente local
  2. Abra uma nova Issue no Gitlab do projeto
  3. Crie uma nova Branch apartir da Issue criada
  4. Inicie o desenvolvimento
  5. Teste suas alterações
  6. Commite seu código
  7. Publique as alterações no npm

6. Publicando

Para publicar uma nova versão da biblioteca:

  1. Tenha certeza que os seus componentes estão sendo devidamente exportados no src/index.ts

  2. Realize o build do código TypeScript com o comando:

        npm run build
  3. Altere a propriedade "version" no arquivo package.json de forma semântica, seguindo os padrões de Major, Minor, Path, etc. (siga o padrão KeepAChangeLog)

  4. Publique as alterações no npmjs.com com o comando:

        npm publish