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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@doogly/react

v1.0.6

Published

A React component for Doogly with QR code support.

Readme

This is a react component that can be used to accept payments using Doogly.

Peer Dependencies

ethers >= ^6.0.0 react" >= 16.8.0 react-dom >= 16.8.0

Installation

npm i @doogly/react

Usage

Accepting payments with Doogly

  1. Visit https://app.doogly.org and choose the chain and token to receive payments.
  2. Add the contract interactions on destination chain if any
  3. Choose the widget theme color and get the component
  4. The component looks like this:
<DooglyButton
  buttonText="ADD DONATE BUTTON TEXT (OPTIONAL)"
  modalTitle="ADD MODAL HEADING (OPTIONAL)"
  // Api url to fetch token and route details
  apiUrl="https://api.doogly.org"
  // Configure modal
  config={{
    destinationChain: "DESTINATION CHAIN ID",
    destinationAddress: "DESTINATION ADDRESS", // Destination address (Dummy if postSwapHook is used)
    destinationOutputTokenAddress: "OUTPUT TOKEN", // Output token at destination
    initialAmount: "DEFAULT INPUT AMOUNT (OPTIONAL)",
    initialChainId: "DEFAULT SOURCE CHAIN ID (OPTIONAL)",
    initialToken: "DEFAULT SOURCE TOKEN (OPTIONAL)",
  }}
  modalStyles={{
    backgroundColor: "MODAL BACKGROUND (OPTIONAL)",
    headingColor: "MODAL HEADING COLOR (OPTIONAL)",
    buttonColor: "MODAL BUTTON COLOR (OPTIONAL)",
    textColor: "MODAL TEXT COLOR (OPTIONAL)",
  }}
  /* Callback function executes on frontend after user executes transaction
  @type ({
          transactionId: string;
          requestId: string;
          fromChainId: string;
          toChainId: string;
          status: string; // ["success", "partial_success", "needs_gas", "not_found"]
        }) => void;
  **/
  callback={"CALLBACK FUNCTION (OPTIONAL)"}
  /* Webhook Url to post transaction details to backend if any once user confirms transaction
  Body - 
  {
    address: string;
    transactionHash: string;
    fromChain: string;
    toChain: string;
    data: additional webhook data
  }
  **/
  webhookUrl="WEBHOOK URL"
  webHookData="ADDITIONAL WEBHOOK DATA"
  /**
  Contract calls to be executed sequentially on destination chain
  @type {
    target: `0x${string}`; // Contract address
    callData: `0x${string}`; // Call data
    callType?: number; // Calltype 0 - Default, 1 - Utilise all the resulting output tokens after bridging + swapping, 2 - Utilize all output native tokens after bridging + swapping
    tokenAddress?: `0x${string}`; // Token address in case calltype is 1
    inputPos?: number; // Input position to dynamically modify with previous call output
  }
   */
  postSwapHook={"HOOKDATA"} // Post swap hook to execute contract calls after swap from bridge itself
  buttonClassName="CHECKOUT BUTTON CLASSNAME"
/>