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

payplug-ui-plugins-bo

v2.2.1

Published

V2.0.0

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Maintainers

hdelaforcehdelaforcejhoarauppjhoaraupp

Keywords

Readme

payplug-ui-plugins

V2.0.0

PayPlug design library for CMS (specially Woocommerce and PrestaShop)

Getting started

cd existing_repo
git remote add origin https://github.com/payplug/payplug-ui-plugins.git
git branch -M master
git push -uf origin master

Project setup

###Prerequisites: Familiarity with the command line

Install Node.js version 16.0 or higher

npm install

Compiles and hot-reloads for development

npm run serve

Compiles and minifies for production depending on your environment

npx vue-cli-service build --mode environment_file

Run Storybook

npm run storybook

Lints and fixes files

npm run lint

Environment variables

VUE_APP_ENV=sandbox
VUE_APP_LOGIN
VUE_APP_OAUTH_LOGIN
VUE_APP_LOGOUT
VUE_APP_INIT
VUE_APP_BANCONTACT
VUE_APP_DEFERRED
VUE_APP_ONE_CLICK
VUE_APP_INSTALLMENT
VUE_APP_AMERICAN_EXPRESS
VUE_APP_ONEY
VUE_APP_APPLE_PAY
VUE_APP_INTEGRATED
VUE_APP_SATISPAY
VUE_APP_MYBANK
VUE_APP_SOFORT
VUE_APP_GIROPAY
VUE_APP_IDEAL
VUE_APP_REQUIREMENTS
VUE_APP_REFRESH_KEYS
VUE_APP_SAVE
VUE_APP_TELEMETRY

Environment files available

.env - environment file, used in development, get from project file

.env.prestashop - environment file, used for prestashop project

.env.woocommerce - environment file, used for woocommerce project

Build Command

ENV=woocommerce npm run build - for woocommerce env file ENV=prestashop npm run build - for prestashop env file

NB: ENV is not mandotory, if not specified, .env file will be used

Integrate with your framework

  • Copy the compiled files into your project.
  • include them into your code. eg for woocommerce:
wp_enqueue_script('chunk-vendors.js', PAYPLUG_GATEWAY_PLUGIN_URL . 'assets/dist/js/chunk-vendors-0.1.1.js', [], PAYPLUG_GATEWAY_VERSION);
wp_enqueue_script('app.js', PAYPLUG_GATEWAY_PLUGIN_URL . 'assets/dist/js/app-0.1.1.js', [], PAYPLUG_GATEWAY_VERSION);
wp_enqueue_style('app.css', PAYPLUG_GATEWAY_PLUGIN_URL . 'assets/dist/css/app.css', [], PAYPLUG_GATEWAY_VERSION);

Support

Contributing

State if you are open to contributions and what your requirements are for accepting them.

For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.

You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.

Authors and acknowledgment