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

@d4sd/components

v3.1.8

Published

D4SD Component Library, extended from Ant-Design

Downloads

320

Readme

d4sd-components

This is the component library for D4SD

It is an extension of Ant Design, so all non-overided components remain purely Ant Design components

To see/test our components, go to master branch and run npm run storybook

How to publish components library

First, make your components in the components folder

Then, in index.tsx in the root folder, add a

export { YourComponent } from "./components/YourComponent";

before the export * from "antd"

Then, running

npm run storybook

Will load the current code and show your components in stories on a locally hosted website that will eventually automatically open.

Then run the following to prepare/build the component library for publishing

npm run build

This essentially removes the old package and then runs webpack to pack our code into a library.

This will eventually open a website displaying the contents of the package just built and its size, you can quit this process anytime. The package contents should contain index.js and main.css.

After running the build, make sure to commit all changes and push them to the remote (GitHub) and then update the package version

npm version patch

Then we finally publish the library with

npm publish

Once published, make sure to run

npm install @d4sd/components

in whichever repository is using our components to update it.

Development Workflow / Tips

The master branch should always be in sync with what is published. E.g, if you ran npm run build, the built package is the same as what is being hosted on npm.

With this in mind, make changes by branching off of master and test those changes using npm run storybook. Commit/push those changes to your branch and merge your branch into master once it is ready. After each merge, make sure to follow the publishing steps above.