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

@xkit-co/crm-link.js

v2.10.9

Published

CRM integrations on your application via XKit

Downloads

292

Readme

@xkit-co/crm-link.js

Installation

Refer to documentation

Changelog

View Changelog

Debugging

Under some very specific circumstances, you might run into issues with using this library. Some of these are known and are listed below:

  • This library renders DOM elements at z-index values of 999 and 1000. You might notice an issue if the z-index values in your application are the same or higher.
  • This library uses the available height of the document window to determine where to render dropdown menus. If for some reason, the height of your application's html or body element is less than the viewport height, you might notice an issue.
  • This library when consumed as a node package is built for ES5 and above. Make sure your build tool or bundler is up to date.
  • When using the browser script, ensure window.linkCRM is not re-assigned.
  • Ensure that no DOM elements in your application have an id attribute of xkit-crm-link-scope.

API

linkCRM()

| Argument | Type | Description | | --------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | domain | string | The domain string of your Xkit application. This can be viewed and configured in the Xkit developer portal. | | token | string | The Xkit context token that is fetched from your application's backend. Refer to the Xkit documentation. | | options | object | The configuration object by which the user will map data from their CRM, and customize how CRM Link is launched. Refer to the Xkit documentation. |

| Return Type | Description | | ----------------- | -------------------------------------------------------------------------- | | Promise<string> | A promise that either resolves to a connection ID or rejects with an error |