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

furya-chain-web

v1.0.0

Published

<p align="center"><img src="https://furya.exchange/icon.svg?" width="256" /></p>

Downloads

6

Readme

Prerequisites

  • Node.js version 18 and pnpm installed on your system
  • Wallet Connect account

For deploying with Vercel, create an account with Vercel if you don't have one already.

For deploying to IPFS, choose one of the following:

For web3.storage, sign up for an account and generate an API token on the API tokens page. web3.storage offers an easy-to-use interface for storing and retrieving content on IPFS.

Alternatively, follow the IPFS Kubo installation guide to download the IPFS command-line tool.

Part 1: Setting up your local environment

1. Clone the repo

Clone the repository and navigate to its directory:

git clone https://github.com/furyaprotocol/v4-web.git
cd v4-web

2. Install pnpm and dependencies

Install pnpm and the project dependencies:

npm i -g pnpm
pnpm i

Part 2: Running the project locally

Run the following command in the project directory to start the development server:

pnpm dev

The development server will be running at http://localhost:5173 (or the port number displayed in the terminal). Visit this URL to interact with the web app and see your changes in real-time.

To view component stories:

pnpm ladle

This will automatically open your default browser at http://localhost:61000.

Part 3: Configuring environment

Add or modify the relevant endpoints, links and options in /public/configs/env.json. You'll need to provide a Wallet Connect project id to enable onboarding and wallet connection:

  • Create a project on https://cloud.walletconnect.com/app
  • Copy over the project ID into this field

Part 4: Set Enviornment variables

Set environment variables via .env.

  • VITE_BASE_URL (required): The base URL of the deployment (e.g., https://www.example.com).
  • VITE_ALCHEMY_API_KEY (optional): Add an Alchemy API key for EVM interactions; the app will fall back to public RPCs if not provided.
  • VITE_PK_ENCRYPTION_KEY (optional): AES encryption key used for signature obfuscation; necessary for enabling the "Remember Me" feature.
  • VITE_V3_TOKEN_ADDRESS (optional): Address of the V3 $FURYA token.
  • VITE_TOKEN_MIGRATION_URI (optional): The URL of the token migration website.
  • AMPLITUDE_API_KEY (optional): Amplitude API key for enabling Amplitude; used with pnpm run build:inject-amplitude.
  • BUGSNAG_API_KEY (optional): API key for enabling Bugsnag; used with pnpm run build:inject-bugsnag.
  • IOS_APP_ID (optional): iOS app ID used for enabling deep linking to the iOS app; used with pnpm run build:inject-app-deeplinks.
  • INTERCOM_APP_ID (optional): Used for enabling Intercom; utilized with pnpm run build:inject-intercom.
  • STATUS_PAGE_SCRIPT_URI (optional): Used for enabling the status page; used with pnpm run build:inject-statuspage.

Deployments

Deploying with Vercel

Step 1: Connect your repository to Vercel

Select "Import Git Repository" from your dashboard, and provide the URL of this repository or your forked repository.

Step 2: Configure your project

For the "Build & Development Settings", we recommend the following:

  • Framework Preset: Vite
  • Build Command (override): pnpm run build

By default, the dev server runs in development mode and the build command runs in production mode. To override the default mode, you can pass in the --mode option flag. For example, if you want to build your app for testnet:

pnpm run build --mode testnet

If you wish to incorporate analytics via Amplitude and Bugsnag, you can use our scripts: pnpm run build:inject-amplitude and pnpm run build:inject-bugsnag. You will need to provide your own API keys for these services. In the Environment Variables section, name the variables as AMPLITUDE_API_KEY and BUGSNAG_API_KEY and provide the respective keys as their values.

For more details, check out Vercel's official documentation.

Deploying to IPFS

web3.storage: deploy to IPFS via web3.storage using the provided script

Export the API token as an environment variable (replace your_token with the generated token), and run the script to build and deploy to IPFS:

export WEB3_STORAGE_TOKEN=your_token
pnpm run deploy:ipfs

Save the URL provided in the output, as it is the link to your deployed content on IPFS.

IPFS client: deploy with the command-line tool

To use the IPFS command-line tool, run:

ipfs add -r dist

Save the CID provided in the output.

Accessing your content on IPFS

To access your content on IPFS:

  1. Native IPFS support in a browser: Use a browser with native IPFS support, such as Brave or Opera. Enable a local IPFS node and visit the URL directly using the IPNS protocol, like ipfs://your_cid.

  2. Public IPFS gateway: Access your content via a public IPFS gateway, such as https://dweb.link or https://w3s.link/. Use the gateway URL with your CID appended, like https://dweb.link/ipfs/your_cid.

Replace your_cid with the actual CID.

Cloudflare Settings

We recommend that you add your website to Cloudflare for additional security settings.

To block OFAC Sanctioned countries:

  1. Navigate Websites > Domain > Security > WAF

  2. Create Rule with the following settings:

  • If incoming requests match (ip.geoip.country eq "CU") or (ip.geoip.country eq "IR") or (ip.geoip.country eq "KP") or (ip.geoip.country eq "SY") or (ip.geoip.country eq "MM") or (ip.geoip.subdivision_1_iso_code eq "UA-09") or (ip.geoip.subdivision_1_iso_code eq "UA-14") or (ip.geoip.subdivision_1_iso_code eq "UA-43")
  • This rule will bring up a Cloudflare page when a restricted geography tries to access your site. You will have the option to display:
    1. Custom Text
    • (e.g. Because you appear to be a resident of, or trading from, a jurisdiction that violates our terms of use, or have engaged in activity that violates our terms of use, you have been blocked. You may withdraw your funds from the protocol at any time.)
    1. Default Cloudflare WAF block page