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

bnpl-ui-sdk

v0.8.10

Published

``` Note: This project uses Node Version 16 and NPM Version 8 , Make sure you have that installed in your machine

Downloads

4

Readme

Bnpl UI SDK

Note: This project uses Node Version 16 and NPM Version 8 , Make sure you have that installed in your machine

Quick Overview

There are 3 parts to this project.
- Examples folder
- Src folder: SDK folder, components folder
- Stories folder

Examples Folder:

This folder contains the playground environment where you are able to see the UI components and the whole app itself. You as a user can click through buttons and use the app as a standalone.

Src Folder:

SDK Folder

This folder contains the UI SDK that can be installed from npm and imported and used inside of a React app. The SDK has interfaces that needs to be implemented so that the sdk can run and function as expected.

Components Folder

This folder contains all the modular components that can be important and used inside of the SDK folder. The modular components can be installed and used inside of an React app by themselves and a stand alone component. Note: Some components might be dependent on others.

Stories Folder

This folder contains all the implementation of the component as a doc and also shows how the component looks like by itself. Gives good understanding of the needed and optional props that needs to be passed for the component so that it can work as expected.

Easy start to run UI locally

npm install

cd to example folder

npm install

npm start

Storybook

Running storybook to see each component:

npm run storybook

This loads the stories from ./stories.

Unit test with Jest

Jest tests are set up to run with npm run test or yarn run test.

E2E test with cypress

- Note: if this is your first time running cypress the browser might not open right away, you might have to run the cmd again
Before running cypress test, make sure you are running the example.

Cypress tests are set up to run with npm run e2e or yarn run e2e. This will open up a browser showing all the available e2e test than can be run. Continue by selecting and running the test.

Running Cypress headless mode

npm run e2e-headless

TypeScript

tsconfig.json is set up to interpret dom and esnext types, as well as react for jsx. Adjust according to your needs.

Module Formats

CJS, ESModules, and UMD module formats are supported.

The appropriate paths are configured in package.json and dist/index.js accordingly. Please report if any issues are found.

Publishing

  • When you are in development phase and if you do need to publish your library for testing, recommend using postfix the Version number with your initial such as 0.11.0-TD

  • If you want to change version number while publising from your laptop, do following

npm config set @equipifi:registry https://gitlab.com/api/v4/projects/34083948/packages/npm/
echo "//gitlab.com/api/v4/projects/34083948/packages/npm/:_authToken=HpjEbfx3Rz5gWCnoNSsH">.npmrc
npm version 0.11.0-TD -no-git-tag-version --force
npm publish
  • Once you are ready for review your code you can update the version number in .gitlab-ci.yml without postfix and create PR

  • Once the the PR is merged to release branch an artifact will be published as <version_no>-release (e.g. 0.11.0-release)

  • Once we merged release branch to deploy branch the an artifact will be published as <version_no> (e.g. 0.11.0)

  • Consumer of this library should always use specific release version while in release branch

  • Once the consumer of this library decided to move from release to deploy branch, you can update the version to use deploy version of the library