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

clu-recognizer

v1.0.1

Published

This library implements node.js support for Composer with Conversation Language Understanding.

Downloads

24

Readme

Conversation Language Understanding (CLU) Recognizer

Summary

This recognizer helps you add a custom recognizer to an empty bot built with Bot Framework Composer in order to use the Conversation Language Understanding Service in place of the now deprecated LUIS.

Installation

In order to enable the CLU recognizer, you must first install the CLU recognizer package from NPM in your Composer project.

  1. Create a new Composer bot using the Empty Bot template.

  2. Open the Package Manager in Composer.

  3. Search for ConversationLanguageUnderstandingRecognizer and install the package.

Configuration

To enable the Conversation Language Understanding recognizer, complete the following steps:

  1. Select Custom as your root dialog's recognizer type.

  2. Paste the following JSON into the custom recognizer configuration window:

{
  "$kind": "Microsoft.CluRecognizer",
  "projectName": "<your project name>",
  "endpoint": "<your endpoint, including https://>",
  "endpointKey": "<your endpoint key>",
  "deploymentName": "<your deployment name>"
}
  1. Update the projectName, endpoint, endpointKey, and deploymentName fields with the values from your Conversation Language Understanding service.

    • The deploymentName value can be found in the Deploying a model blade under Deployments inside Language Studio.

    • The endpoint value can be found in the Deploying a model blade under Deployments inside Language Studio by clicking on the Get prediction URL option. It can also be found in the Keys & Endpoint blade of your Language resource in the Azure Portal. The endpoint should take the format https://<language-resource-name>.cognitiveservices.azure.com. Ensure that the trailing slash is omitted.

    • The projectName and endpointKey values can be found in your Project Settings blade under Azure Language Resource inside Language Studio.

Ensure that you have selected the correct values for each field. Using the wrong values can lead to errors when running the bot.

Usage

Once you have configured intents and entities in your Conversation Language Understanding project, custom intent triggers and the CLU intent triggers should function as normal. When creating a new intent trigger in a Composer bot, make sure that the intent value of the trigger matches the intent in the deployed Language resource (case-sensitive).

Since the Conversation Language Understanding recognizer is a modified version of the existing LUIS recognizer, the workflow elements work the same. In addition the respective LUIS events and telemetry are written out to the logs.

Limitations

Please remember that Composer does not integrate natively with Conversation Language Understanding, so managing intents and entities must be done in the Language Studio portal instead of Composer.