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

languagetool-cli

v1.0.13

Published

Command line tool to check for spelling errors in documents

Downloads

22

Readme

languagetool-cli

Command line interface towards languagetool (https://languagetool.org)

This is some kind of work in progress as a side-kick besides writing a book. For a list of open issues, please refer to the to-dos.

Dependencies

You have to have a running LanguageTool-Server (see https://dev.languagetool.org/http-server) on port 8081

usage

Usage: language-tool [options] [files...]

Arguments:
  files                                  Input files

Options:
  -v, --verbose                          Debug output (default: false)
  --enabled-rules <rules...>
  --disabled-rules <rules...>
  --enabled-categories <categories...>
  --disabled-categories <categories...>
  --only-enabled                         Use enabled rules only (default: false)
  -r, --rule-config <files...>
  --url <url>
  --concurrent <concurrent>
  --output-format <format>               Output format (choices: "pretty", "vim", "reviewdog", default: "pretty")
  -l, --language <language>              Sprache (default: "auto")
  -m, --mother-tongue <mother-tongue>    Mother tongue
  -h, --help                             display help for command

-language, -l

Sets the language to be used.

-mother-tongue, -m

The mother tongue. If set, some more grammar checks are performed

--rule-file, -r

Adds rules that are processed for all files. The syntax is described in Configuration Files below.

You can add as many files as needed

--enabled-rules, --disabled-rules

Enables/disables rules given by rule-id.

--enable-categories, --disable-categories

Enables/disables rules given by rule-id.

--output-format

Output messages a pretty (user friedly) or computer readable (vim, reviewdog) format.

--concurrent

Limit the number of concurrent requests to the LanguageTool-server in parallel. The default is set to 2.

Line and file inline comments

<!-- languagetool-disable-file german_grammar_rule(atembar) -->
<!-- languagetool-enable-file german_grammar_rule(atembar) -->
<!-- languagetool-disable-line german_grammar_rule(atembar) -->
<!-- languagetool-enable-line german_grammar_rule(atembar) -->
<!-- languagetool-disable-next-line german_grammar_rule(atembar) -->
<!-- languagetool-enable-next-line german_grammar_rule(atembar) -->

This needs <<TBD>>

Configuration Files

The file contains a simple syntax:

  • Every line can contain a command, which is either disabled or enabled, followed by rules in the for rule-id, followed by an optional token in parens.

  • A line starting with a hash sign ('#') represents a comment

An example:

# missing in lexicon
disable german_grammar_rule(atembar) german_grammar_rule(atembare)

# A Name
disable GERMAN_SPELLER_RULE(Brom)

# This book contains a lot of repeating starts
disable GERMAN_WORD_REPEAT_BEGINNING_RULE