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

@autonolas/frontend-library

v0.4.25

Published

Codebase to common style, components, settings, etc.

Downloads

134

Readme

Autonolas Frontend Library

This repository contains the common UI modules/components for Autonolas frontends.

Tech Stack

  • ReactJS
  • Styled components
  • Ant Design
  • React testing library
  • Jest
  • ethers

Note

  • To avoid multiple react packages please do the following:
  1. In Application: a) cd node_modules/react && yarn link b) cd node_modules/react-dom && yarn link

  2. In Library a) yarn link react b) yarn link react-dom

Working with components in autonolas-frontend-library

When developing changes in the autonolas-frontend-library repo that you wish to see in any other repository, let's take for example autonolas-registry-frontend, follow the yarn linking process to resolve this dependency locally rather than downloading the published library package.

  1. In autonolas-frontend-library, run yarn link. This creates a symlink on your machine pointing to the library. You may require sudo permissions to run this command.
  2. In autonolas-registry-frontend, run yarn link autonolas-frontend-library. This tells yarn to get the library from your symlink instead of downloading the package from GitHub.

Once the package is linked, run yarn run build:watch in the autonolas-frontend-library repo, make changes, and see them hot reloaded into autonolas-registry-frontend.

Once you are done developing in autonolas-frontend-library, you can follow the steps below to unlink the local package. Otherwise, you may see issues if your autonolas-frontend-library repo is not up to date.

  1. In autonolas-registry-frontend, run yarn unlink --no-save autonolas-frontend-library. The --no-save flag is important to ensure that the dependency is not removed from package.json and yarn.lock.
  2. In autonolas-registry-frontend, run yarn install autonolas-frontend-library to fetch the latest published version from GitHub.
  3. In autonolas-frontend-library, run yarn unlink to delete the symlink created by yarn. You may require sudo permissions to run this command.

To run storybook

yarn run storybook