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

js-lcs

v1.0.1

Published

Longest common substring implementation in JavaScript

Downloads

18

Readme

js-lcs

npm version License: MIT Build Status

Partial1 implementation of Longest common substring problem in TypeScript/JavaScript, relatively fast and memory-optimized2.

Usage

Simple

import { LCS } from 'js-lcs';

LCS.size("aababcabcdabcaba", "eabcde"); // 4

Advanced

You can get more performance if you switch to typed arrays like Uint8Array, Uint16Array, and instantiate only one instance of LCS class:

import { LCS } from 'js-lcs';

const rawFiles = [
  // Uint16Array of char codes in file_1.txt
  // ...
  // Uint16Array of char codes in file_n.txt
];

const maxSize = Math.max(...rawFiles.map(f => f.length));
const lcs = new LCS({ maxSize }); // in this way you reuse once allocated memory for every lcs.size() call

for (let i = 0; i < rawFiles.length; i++) {
  for (let j = 0; j < i; j++) {
      const [a, b] = [rawFiles[j], rawFiles[i]];
      console.log(lcs.size(a, b));
    }
  }
}

Please always make sure you don't mix types of arguments to lcs.size(), e.g. if you start passing typed arrays, do not pass strings anymore and vice versa. Otherwise, you risk getting size() function deoptimized by V8.

Footnotes

  1. At the moment, it can calculate only size of the longest common substring, not the string itself.
  2. Processing two 3,000-char strings takes under 2 seconds, however, memory consumption still can be improved a bit, from O(max(r, n)) to O(min(r, n)) with a little pull request. Performance improvements are very welcome!