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

esewa-react

v1.1.2

Published

A React library for integrating eSewa payment gateway into your React applications. This library handles hash signatures, base64 URL encoding, and provides a simple interface for initiating and verifying eSewa payments.

Readme

esewa-react

A React library for integrating eSewa payment gateway into your React applications. This library handles hash signatures, base64 URL encoding, and provides a simple interface for initiating and verifying eSewa payments.

npm version GitHub stars

Installation

npm install esewa-react
# or
yarn add esewa-react

Quick Start

import { useEsewa } from 'esewa-react';

function PaymentButton() {
  const { initiatePayment, loading, error } = useEsewa({
    merchantId: 'YOUR_MERCHANT_ID',
    successUrl: 'https://your-domain.com/success',
    failureUrl: 'https://your-domain.com/failure',
    secretKey: 'YOUR_SECRET_KEY',
    isTest: true, // Set to false for production
  });

  const handlePayment = () => {
    initiatePayment({
      amount: '100',
      productId: 'TXN_ID',
      successUrl: 'https://your-domain.com/success',
      failureUrl: 'https://your-domain.com/failure',
    });
  };

  return (
    <div>
      {error && <div className="error">{error}</div>}
      <button 
        onClick={handlePayment}
        disabled={loading}
      >
        {loading ? 'Processing...' : 'Pay with eSewa'}
      </button>
    </div>
  );
}

Features

  • 🚀 Simple React hook for easy integration
  • 🔒 Secure payment handling with proper signatures
  • 📦 TypeScript support out of the box
  • 🧪 Test and production environment support
  • ⚡️ Lightweight and fast

API Reference

useEsewa Hook

const { initiatePayment, loading, error } = useEsewa(config);

Config Options

| Option | Type | Required | Description | |--------|------|----------|-------------| | merchantId | string | Yes | Your eSewa merchant ID | | secretKey | string | Yes | Your eSewa secret key | | successUrl | string | Yes | URL to redirect after successful payment | | failureUrl | string | Yes | URL to redirect after failed payment | | isTest | boolean | No | Set to true for test environment |

Payment Data

| Field | Type | Required | Description | |-------|------|----------|-------------| | amount | string | Yes | Payment amount | | productId | string | Yes | Unique transaction ID | | successUrl | string | Yes | Success callback URL | | failureUrl | string | Yes | Failure callback URL |

Security Best Practices

  1. Always use environment variables for sensitive data:
VITE_ESEWA_MERCHANT_ID=your_merchant_id
VITE_ESEWA_SECRET_KEY=your_secret_key
VITE_ESEWA_SUCCESS_URL=https://your-domain.com/success
VITE_ESEWA_FAILURE_URL=https://your-domain.com/failure
  1. Use HTTPS for all URLs in production
  2. Keep your secret key secure and never expose it in client-side code
  3. Test thoroughly in test mode before going to production

Contributing

Contributions are welcome! Please feel free to submit a Pull Request.

License

MIT