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

@tailrecursive/bs-react-stripe-elements

v0.0.6

Published

Bindings for Stripe's react-stripe-elements

Downloads

4

Readme

bs-react-stripe-elements

Introduction

Minimal, hand-generated BuckleScript + ReasonReact bindings for react-stripe-elements. The bindings are vanilla, which means it'll mostly be 1-to-1 bindings. However, the bindings will help you out by for example removing stringly-typed code wherever possible.

State: experimental, but active. unpublished and requires polishing

Examples / Demo

Main Demo

Note that these examples are not runnable. You would have to copy the files to your own React app to test them. For testing the bindings, I just constantly yarn add <path-to-local-directory-of-bs-stripe-react-elements> within a different web app to get the updated changes.

This demo ideally will match Stripe's own basic demo.

Component Demos

TBD. I will add specific component usage (styling a CardElement for example).

Installation

1

Since the package is currently unpublished, we do not use npm. Instead, we rely on the master branch.

  • With yarn

yarn add cnguy/bs-react-stripe-elements#master

  • With npm

npm install --save cnguy/bs-react-stripe-elements#master

2

Add @tailrecursive/bs-react-stripe-elements to bsconfig.json bs-dependencies.

3

Add Stripe.js to your index.html file as well. Put it before your app's JS bundle.

<html>
  <head />
  <body>
    <div id="root" />
    <script src="https://js.stripe.com/v3/"></script>
    <script src="bundle.js"></script>
  </body>
</html>

Entry Point

let component = ReasonReact.statelessComponent("App");

let make = _children => {
  ...component,
  render: _self =>
    <div>
      StripeElements.(
        <StripeProvider apiKey="pk_abcdefghijklmnoprstuvwxyz">
          ...<CheckoutForm />
        </StripeProvider>
      )
    </div>,
};

Changes

Currently unpublished. master branch will be the "releases" while the development branch will be where we'll be working.

Goal is to figure out all issues and publish a v0.0.1 that implements a majority of the API's.

Contributing

Hi! I'm Chau. This is my first Reason binding, and it's mostly experimental, but I really, really want to polish it, especially because I think Stripe is cool. Also, I use a lot of Reason libraries made by amazing community members, and so I want to try to give back in some way.

All contributions are welcome, whether it's fixing bugs, advice, or important questions (how will I deal with style props for example? will I make a wrapper, convenient API? etc).

I'm pretty active, so don't hesitate to post an issue or send a pull request.