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

lifi-web

v0.0.1

Published

## Setup

Downloads

4

Readme

transferto.xyz powered by LI.FI

Setup

Use nvm to run the app with the latest node version you have installed run: nvm use. Version 16 works great, install it using nvm install 16.

EditorConfig defines basic formatting, use a plugin for your IDE.

# install dependencies
yarn install

# server local development version
yarn start

If you are on windows or if you have problems running the start commands, please try to run yarn windows and create a local .env.local file to define your environment (e.g. if you want to use xpollinate, copy one of the xpollinate files)

The setup includes antd for styled components.

The setup is based on create-react-app.

Environment Variables

All variable names have to start with REACT_APP_ to be available within react.

Use .env for default config variabels used on all environments. Use .env.development and .env.production for environment specific configuration. Create a local .env.local file if you want to test additional settings locally (e.g. run a semi production version).

The .env files are loaded automatically, but changing variables will require you to restart yarn start.

Available Scripts

In the project directory, you can run:

yarn start

Runs the app in the development mode.
Open http://localhost:3000 to view it in the browser.

The page will reload if you make edits.
You will also see any lint errors in the console.

yarn build

Builds the app for production to the build folder.
It correctly bundles React in production mode and optimizes the build for the best performance.

The build is minified and the filenames include the hashes.
Your app is ready to be deployed!

See the section about deployment for more information.

yarn test unit

Executes the unit tests. Unit tests should only test one component and mock others.

yarn test int

Executes the integration tests. These tests do access more of the stack, e.g. they query external API. Since we can't ensure that the external resources are available all the time, these tests may sometimes fail.

Guide for @lifi/sdk

Follow the linked Readme if you need changes in @lifi/sdk package.

Deployment

Pushing code to the repository automatically triggers deployments to several environments:

Branch main:

  • https://transferto.xyz/ (with .env.lifinance-mainnet configuration)

Branch staging:

  • https://staging.transferto.xyz/ (with .env.lifinance-mainnet.staging configuration)