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

@alibaba-aero/vue-webengage

v0.0.11

Published

webengage wrapper for vue as a plugin

Downloads

120

Readme

vue-webengage

Webengage wrapper for vue as a plugin

👀 EARLY RELEASE

CHANGELOGS


Install

npm install vue-webengage
// or
yarn add vue-webengage

Setup

In main.js or wherever you register the plugins:

Vue.use(VueWebengage, {
    namespace: 'webengage',
    key: process.env.WEBENGAGE_LICENSE,
    schemas: {
        hotel: {
            Searched: hotelSearchedSchema,
            Selected: hotelSelectedSchema,
            AddedToCart: hotelAddedToCartSchema,
        },
    },
});
  • namespace The property to access webengage in component context (set this without $). E.g this.$webengage
  • key The key provided by webengage
  • schemas All of your schemas. It's not required to use schemas. Though, it's highly recommended to implement your data structure using a good library and then list them here, so you can access them later in components. 👍 Here is some:

Usage

After adding the plugin, there will be a top-level webengage option available in SFCs.

export default {
    ...
    data() {},
    computed: {},
    ...,
    webengage: {
        ...
    }
}

webengage may be an object or a function returning an object, containing webengage events:

webengage: {
    'Search - Domestic Hotel': {
        ...
    },
    'Selected - Domestic Hotel': {
        ...
    }
} 

// or

webengage(schema) {
    return {
        'Search - Domestic Hotel': {
            ...
        },
        'Selected - Domestic Hotel': {
            ...
        }
    }
} 

There are times when you need same data in different events. So, if webengage is a function, before returning the events object, defined your repetitive data, and use them multiple times in any of the events.

Also, with webengage() being a function, the first parameter will be schema.

webengage(schema) {
    const departureDate = new Date(...);
    return {
        'Search - Domestic Hotel': new schema.hotel.Searched({
            'Departure Date': departureDate,
            ...
        }),
        'Selected - Domestic Hotel': new schema.hotel.Selected ({
            'Departure Date': departureDate,
            ...
        })
    }
} 

Each event may be an object, or a function returning an object. this will be available as the context of your component.


Later then, use this.$webengage.track(eventName) in a proper time, to calculate event's data and trigger webengage tracker.

$webengage

These methods and properties will be available in this.$webengage.

  • .track(payload) Triggers webengage's track. The payload will be available when calculating event's data like 'Search - Domestic Hotel'(payload) { ... }.

  • service Original webengage object. contains all methods and properties that webengage provides. use this for tracking user and other things.

Contribute

Feel free to open pull requests or issues. make sure you implement proper test and all of them are passing with yarn test:unit