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

chrome-extension-react-typescript-boilerplate

v1.0.3

Published

## Getting started - `make init` - Dev env auto refresh on change: `yarn run start` - Build : - `yarn run build:walletlink` (just need to do this once and whenever walletlink changes) - `yarn run build:dev` - `yarn build:prod` - `yarn start` : to start d

Downloads

10

Readme

Coinbase Wallet extension

Getting started

  • make init
  • Dev env auto refresh on change: yarn run start
  • Build :
  • yarn run build:walletlink (just need to do this once and whenever walletlink changes)
  • yarn run build:dev
  • yarn build:prod
  • yarn start : to start dev and watch changes

To load local extension into browser:

  • File a request at go/securityops for an exception to load unpacked extensions into chrome
  • While that request is being processed, Install and run Brave browser
  • navigate to brave://extensions
  • Turn on Developer mode
  • hit "Load unpacked" button, then select folder: wallet-extension/dist

Testing

Runs on Jest with React Testing Library

  • yarn test

I18N

Uses the react-intl library.

/i18n contains the translation property files, the English property file can be generated from the code via i18n:extract and translated files in other languages would be included here as well.

The property files are compiled via i18n:compile into JSON files in /src/i18n. These are the files that are actually read by react-intl and need to be bundled in the extension package.

  • yarn i18n:extract - Extracts all i18n.formatMessage as a new {root}/i18n/en.json file that other translations are based off of.
  • These files should be translated and named after their appropriate locale translations.
  • yarn i18n:compile - Compiles translation files from {root}/i18n/en.json into src/i18n.
  • These files are what is imported and read by the react-intl library.

Error reporting

  • Tool used: Bugsnag
  • Usage: this function can be used anywhere in the app:
import { reportError } from './init/reportError
reportError(ErrorData)
  • ErrorData type:
export type ErrorData = {
  error: Error;
  errorInfo?: React.ErrorInfo;
  metadata?: Record<string, string | number | boolean | string[]>;
  context?: string;
  severity?: 'info' | 'warning' | 'error';
};
  • In dev env, it will be console.log and not appear in bugsnag dashboard

Generating and uploading production source maps to Bugsnag

  • Update the appVersion in webpack.sourcemaps.js as needed.

  • yarn build:sourcemaps

  • This will automatically generate Source Maps to the /dist folder and upload them to Bugsnag