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

@nextbitlabs/nextbit-ui

v2.3.0

Published

A design system for the Nextbit pages written in React

Downloads

31

Readme

Nextbit UI

This project contains the UI

Usage example: run and develop locally - src-doc

Install and code:

yarn install
yarn start

Build the src-doc (used for gitlab pages):

yarn run build-doc

The compiled HTML SPA contained in src-doc is bundled in public folder used by gh-pages.

Note:

WARNING: the public folder is for gitlab-pages, do not put anything in here! It will be destroyed before each build.

Build an exportable library - src

yarn run build-lib
npm publish

T.L.T.R.

This project is meant to be exported as a library and used into other project. The main entry is src/index.ts file.

To achieve this and produce CJS, UMD and ESM bundles with a single declaration file... I'm doing some workaround/build step.

I'm using microbundle to produce the final dist but it does not actually compiles typescript, only strip types and this is a little bit problematic.

So there are a first compilation step:

  1. compile with tsc into build folder (using tsconfig.json)
  2. actually launch microbundle
  3. bundle d.ts with dts-bundle-generator.

After this step the temporary build folder can be removed.

How to improve

There is big space for improvement writing a custom rollup script that does all this by itself. See those notes:

References