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

@gojiraf/floating-ecommerce-display-prod

v1.0.7

Published

<div align="center">

Downloads

254

Readme

Floating Ecommerce Display - Iframe

| Staging Version | Production Version | |:----------------:|:-------------------:| | Staging Package Version | Production Package Version |

Table of Contents

  1. Introduction
  2. Features
  3. Scripts
  4. Usage
  5. Folder Structure
  6. How to work in this project

Introduction

This project focuses on the implementation of an iFrame that embeds Live and is distributed to clients through a script. By employing an iFrame and a specialized script, it facilitates the dynamic delivery of real time experiences to end users, offering a practical and scalable solution for integrating Live into clients' sites.

Features

  • Show Live icon
  • Autoplay iframe when a page is open
  • Open iframe when press in Live icon
  • Open Live in new tab when press in Live icon
  • Change position of Live icon

Script

The script accepts the following parameters

  • showLiveButton - to show the live icon
  • position - to put the icon on the left side or right side
  • openNewTab - to open the live in a new tab
  • autoPlayIframe - to leave the iframe open
  • storeId - id of the client's store

Example Script

<script
    src="https://unpkg.com/@gojiraf/floating-ecommerce-display-prod/dist/gj-ctc-production.js"
    autoPlayIframe="true"
    openNewTab="false"
    showLiveButton="true"
    position="right"
    storeId="<storeId>"
></script>

Usage

For use this project you need to start a Live and run the command server:dev to start a project in local

  • Simulate params of script in file App.tsx
const simulatedProps: AppProps = {
    position: 'left',
    autoPlayIframe: true,
    openLiveNewTab: false,
};

return <ClickToCall {...simulatedProps} />;

Folder Structure

|    |-- src/
|       |-- app.tsx
|       |-- index.tsx
|       |-- App.css
|       |-- index.css
|       |-- components/
|       |     |-- Devices/
|             |--  Forms/
|             |-- Iframe/ 
|             |-- Kit/
|             |-- ClickToCall.tsx
|   |-- ...
|-- README.md

How to work in this project

Two branchs:

  • dev - for staging
  • main - for production

Git flow:

  • Create a new branch from dev and do the PR against the same branch.
  • Once the PR has been merged against the dev branch, you need to create another PR against the main branch to take the changes to production.

Deploy changes:

  • For Deploy changes you need access to gojiraf npm account - You must consult the corresponding person for access
  • Once you have access to gojiraf npm account you need to open terminal and run npm login
  • Then run the script publish corresponding to each environment