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

barramundi

v3.1.1

Published

[![Build Status](https://codebuild.eu-west-1.amazonaws.com/badges?uuid=eyJlbmNyeXB0ZWREYXRhIjoiQVlqeVZ2cUFjQ3FnMFBhZk5KcG8yTWZkb2hyV0c3TDJ0UEI1eUtjUzZvQndaOEV5NGVtVCtLemlCbmY5N29QbVFYMDlUcjBocW1ZQ0hnRjNnZFlsYVVJPSIsIml2UGFyYW1ldGVyU3BlYyI6IkFON1U5SDZYM2dH

Downloads

477

Readme

Barramundi (web component library)

Build Status npm version

Barramundi

The barramundi (Lates calcarifer) or Asian sea bass, is a species of catadromous fish in the family Latidae of the order Perciformes. The species is widely distributed in the Indo-West Pacific region from Southeast Asia to Papua New Guinea and Northern Australia.

Prized by anglers for their good fighting ability barramundi are reputed to be good at avoiding fixed nets and are best caught on lines and with fishing lures. In Australia, the barramundi is used to stock freshwater reservoirs for recreational fishing.

Before you start

We use a number of packages in private repositories. To support these you'll need to add two environment variables to your shell config (e.g. .bashrc, .zshrc, .bash_profile):

# Fishbrain package registry tokens
export FISHBRAIN_PACKAGE_REGISTRY_TOKEN=XXXXX
export FONT_AWESOME_PACKAGE_REGISTRY_TOKEN=XXXXX

For FISHBRAIN_PACKAGE_REGISTRY_TOKEN the token can be generated by creating a personal access token in your Github account. Make sure to provide repo, write:packages and read:packages scopes for your token. Copy your token and Enable SSO. The token can now be used as the value for FISHBRAIN_PACKAGE_REGISTRY_TOKEN.

For FONT_AWESOME_PACKAGE_REGISTRY_TOKEN the token can be found in 1Password.

Getting started

Runs yarn start to run the app in the development mode. This will start a Storybook instance at http://localhost:9001 which you can user for development.

Run tests with yarn test and linting with yarn lint.

There is a live version of Barramundi Storybook (develop branch) available at http://barramundi.surge.sh/.

Frontend Guidelines

The Frontend Guidelines can be viewed here.

Adding a new components

Components should be exported via src/index.ts. Every component should have a Storybook entry, and ideally some form of unit test.

Developing alongside another JS app

If you want to do parallel development of Barramundi and an app using it (e.g. Mykiss, Ornatus), you can do the following:

  • Run yarn run build:watch
  • Run yarn link - this will set the local build of Barramundi as the package to resolve to.
  • In the other project directory run yarn link "barramundi".

Don't forget to unlink once you're finished.

Releasing

Run yarn release to go through the release process. If sucessful, this will result in a new version of Barramundi being published to NPM. Make sure to use semantic versioning when selecting the release version.

You will need to create a file .env.deploy and add a GITHUB_TOKEN to allow the release script to run. The token can be generated by creating a personal access token in your Github account. The token will need to have "repo" access; no "admin" or other scopes.

Usage

You'll need to wrap your app in the exported theme provider to be able to use any components:

import { DefaultTheme, ThemeProvider, Text } from 'barramundi';

const App = () =>
  <ThemeProvider theme={DefaultTheme}>
    <Text>Hello Barramundi</Text>
  </ThemeProvider>

You can override or replace DefaultTheme with your own theme.