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

@linx-impulse/banner-client-js

v1.10.2

Published

Banner SDK for Linx Banner API customers

Downloads

13

Readme

banner-client-js

Version CircleCI License Downloads jsDelivr Hits

Front end Banner SDK for Linx Banner API customers

Installation

CDN

<script src="https://cdn.jsdelivr.net/npm/@linx-impulse/banner-client-js/dist/linx-banner.min.js"></script>

There will be created a property called banner in global linx object.

const LinxBanner = linx.banner;
// or
const LinxBanner = window.linx.banner;

npm

npm install --save @linx-impulse/banner-client-js

Using some module bundler like Webpack, it should be called this way:


const LinxBanner = require('@linx-impulse/banner-client-js');
// or
import { BannerClient } from '@linx-impulse/banner-client-js';

Usage

getRecommendations

Parameters

  • options (object)
    • page(string): current page. Ex: home, product, category, subcategory, cart.
    • source(string): device of user. Ex: app, desktop, mobile.
    • showLayout(boolean): whether or not bring layout properties previously set. Default: false.
    • userId(string): the user identifier, used to personalize slides even when user access a new device.
    • homologation(boolean): enable banner homologation. With this feature enabled the disabled banners will be sent on api response.
    • timeout(number): defines a timeout for request in milliseconds.
    • categories(array): list of categories of the page. This information is used by api to apply the exhibition rules for banners.
    • product(object): object containing product data. Useful for product pages.
    • tags(array): array of tags of the page.
    • url(string): url of the page.
    • testGroup(string): AB test group info.
    • searchQuery(string): query terms used if in a search page.

PS: options parameter is not required, neither any of these properties.

Example

LinxBanner.getRecommendations({
  page: 'home',
  source: 'desktop',
  showLayout: true,
  userId: 'user01',
})
  .then((banners) => {
    console.log('Banners: ', banners);
  })
  .catch((error) => {
    console.error('Banners error: ', error);
  });
LinxBanner.getRecommendations({
  page: 'product',
  source: 'mobile',
  showLayout: true,
  product: {
    id: 'prod001',
  },
  url: 'https://www.yourdomain/product/prod001'
})
  .then((banners) => {
    console.log('Banners: ', banners);
  })
  .catch((error) => {
    console.error('Banners error: ', error);
  });
LinxBanner.getRecommendations({
  page: 'subcategory',
  source: 'desktop',
  homologation: true,
  showLayout: true,
  categories: [
    { id: 'cat01', parents: null },
    { id: 'cat02', parents: [ 'cat01' ] },
  ],
  tags: [
    { id: 'tag01' },
    { id: 'tag02' },
    { id: 'tag03' },
  ],
  url: 'https://www.yourdomain/category/cat01/cat02'
})
  .then((banners) => {
    console.log('Banners: ', banners);
  })
  .catch((error) => {
    console.error('Banners error: ', error);
  });

Contributing

  1. Fork it!
  2. Create your feature branch: git checkout -b my-new-feature
  3. Commit your changes: git commit -am 'Add some feature'
  4. Push to the branch: git push origin my-new-feature
  5. Submit a pull request

PS: Do not forget the tests ;)

Test

Run test command:

npm test

Release

Changelog

CHANGELOG

License

MIT