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

keywords-provider

v0.0.6

Published

Serves as provider (parser) of .lex keyword files

Downloads

22

Readme

keywords-provider

Serves as provider (parser) of .lex keyword files.

  1. Imagine a world, full of keyword subsets for each particular language, which should be handled somehow between each other.
  2. Imagine a simple naive translator serving for handling of such a subsets.
  3. Now you knows everything about this repo :)

Distributed via npm, run npm i keywords-provider in project you want this code.

Usage

var KeywordsProvider = require('keywords-provider);
var r2js = new KeywordsProvider({
  folder: './keywords'
});

Options

@param {string} [folder=./] Folder to lookup keywords for
@param {string} [extname=.lex] Extension of keyword files
@param {string} [sep=\r\n] Keywords separator
@param {string} [delim= ] Delimiter between keyword id and its value

Example .lex file for default config

KEY word
AIR plane
HOVER board

KeywordsProvider interface

/**
 * Applies the given config to Provider instance
 *
 * @param {Object} config @see CONFIG
 */
applyConfig: function(config)

/**
  * Initialises keyword storage from given folder
  *
  * @param {String} directory Directory to look keywords from.
  */
initKeywords: function(directory)

/**
  * Returns subset of keywords by its name.
  *
  * @param {String} subset Name of one of loaded subsets
  * @returns {Object}
  */
getKeywords: function(subset)

/**
  * Returns an actual value of keyword from a given subset by its id (key).
  *
  * @param {String} subset Name of one of loaded subsets
  * @param {String} key Id of keyword
  */
getKeyword: function(subset, key)

/**
  * Returns id (key) of keyword by its actual value in given subset.
  *
  * @param {String} keyword Actual keyword value
  * @param {String} subset Name of one of loaded subsets
*/
getKeyId: function(subsets, keyword)

/**
  * Translates the given keyword from the source subsets to the destination subset.
  *
  * @param {String} keyword Actual keyword value
  * @param {String} sourceSubset Name of source subset (one keyword came from)
  * @param {String} destinationSubset Name of target subset (one, translate keyword to)
  * @returns {String} translated keyword
  */
translate: function(keyword, sourceSubset, destinationSubset)

/**
  * Returns translation offset between two keywords.
  * As the keywords of source and target languages may have different length.
  * (they rarely don't)
  *
  * @param {String} keyword Actual keyword value
  * @param {String} sourceSubset Name of source subset (one keyword came from)
  * @param {String} destinationSubset Name of target subset (one, translate keyword to)
  * @returns {Number} count of symbols
  */
getTranslationOffset: function(keyword, sourceSubset, destinationSubset)