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-spell-checker

v1.0.4

Published

## Installation

Downloads

8

Readme

js-spell-checker

Installation

npm i js-spell-checker -g

Usage

$ spell-checker c <dictonary-file> <file-to-check>

Limitations

The dictonary/file-to-check files must be plain text (*.txt). The words within those files must be seperated by new lines. I've provided a file-to-check in this repo with common misspellings that I used during testing. You can also find a dictonary file within this repo. The dictonary does not have every word like 'Friday', so before you assume it's broken check to see if the word exists in the dictonary.

Example Output

screen shot 2019-01-17 at 11 35 17 am

How does it work?

  1. A dictonary and a file to check for spelling errors are provided as command line arguments.
  2. Those files are read as plain text and parsed into Arrays.
  3. The file to check array is matched against the dictonary array. Any differences in the file to check array can be assumed as a misspelled word.
  4. The user is provided feedback in the console, that feedback consists of the misspelled word, the line number to find the misspelled word and suggestions on what they might have meant to spell.
  5. The suggestions are determined by breaking up each misspelled word into an array of characters. Those characters are looped over and transformed using characters out of an alphabet array.
  6. The suggestions are then matched against the dictonary to determine if the suggestion is indeed a word.
  7. The results are output to the console for the user to read.