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

textlint-rule-one-sentence-per-line

v2.0.0

Published

A fixable textlint rule to add a line break after each sentence

Downloads

510

Readme

textlint-rule-one-sentence-per-line

textlint rule

A fixable textlint rule adding a line break after each sentence, also known as Semantic Line Breaks (SemBr).

For example, consider the Gettysburg Address but with one paragraph per line:

# Gettysburg Address

Four score and seven years ago our fathers brought forth on this continent, a new nation, conceived in Liberty, and dedicated to the proposition that all men are created equal.

Now we are engaged in a great civil war, testing whether that nation, or any nation so conceived and so dedicated, can long endure. We are met on a great battle-field of that war. We have come to dedicate a portion of that field, as a final resting place for those who here gave their lives that that nation might live. It is altogether fitting and proper that we should do this.

But, in a larger sense, we can not dedicate—we can not consecrate—we can not hallow—this ground. The brave men, living and dead, who struggled here, have consecrated it, far above our poor power to add or detract. The world will little note, nor long remember what we say here, but it can never forget what they did here. It is for us the living, rather, to be dedicated here to the unfinished work which they who fought here have thus far so nobly advanced. It is rather for us to be here dedicated to the great task remaining before us—that from these honored dead we take increased devotion to that cause for which they gave the last full measure of devotion—that we here highly resolve that these dead shall not have died in vain—that this nation, under God, shall have a new birth of freedom—and that government of the people, by the people, for the people, shall not perish from the earth.

This can be pretty hard to read, especially without word wrapping. More importantly, it is incredibly hard to use a version control system such as Git to track changes to the text. Now take a look at the SemBr Gettysburg Address with one sentence per line:

# Gettysburg Address

Four score and seven years ago our fathers brought forth on this continent, a new nation, conceived in Liberty, and dedicated to the proposition that all men are created equal.

Now we are engaged in a great civil war, testing whether that nation, or any nation so conceived and so dedicated, can long endure.
We are met on a great battle-field of that war.
We have come to dedicate a portion of that field, as a final resting place for those who here gave their lives that that nation might live.
It is altogether fitting and proper that we should do this.

But, in a larger sense, we can not dedicate—we can not consecrate—we can not hallow—this ground.
The brave men, living and dead, who struggled here, have consecrated it, far above our poor power to add or detract.
The world will little note, nor long remember what we say here, but it can never forget what they did here.
It is for us the living, rather, to be dedicated here to the unfinished work which they who fought here have thus far so nobly advanced.
It is rather for us to be here dedicated to the great task remaining before us—that from these honored dead we take increased devotion to that cause for which they gave the last full measure of devotion—that we here highly resolve that these dead shall not have died in vain—that this nation, under God, shall have a new birth of freedom—and that government of the people, by the people, for the people, shall not perish from the earth.

For more information on SemBr (which dates back to the legendary Brian W. Kernighan), take a look at this blog post.

Install

If you don't have textlint installed, please see their installation instructions. Then, install with npm:

npm install textlint-rule-one-sentence-per-line

Usage

Via .textlintrc(Recommended)

Set "one-sentence-per-line" to true:

{
  "rules": {
    "one-sentence-per-line": true
  }
}

To fix errors, run

textlint --fix README.md

Via CLI

To find errors:

textlint --rule one-sentence-per-line README.md

and then to fix them:

textlint --rule one-sentence-per-line README.md --fix

Usage Suggestions

In case that we rely make a mistake splitting sentences into separate lines, please let us know by filing an issue. In the mean time, we suggest using textlint-filter-rule-comments to disable sentence splitting for the offending lines:

<!-- textlint-disable one-sentence-per-line -->

These two sentences will be one the same line. This is because we disabled the rule.

<!-- textlint-enable one-sentence-per-line -->

Although the line breaks will not (hopefully!) change the rendered file, it may make the raw Markdown a little ugly. To solve that, we recommend using prettier to clean up the outputted Markdown.

Finally, if you are using Pandoc's Markdown with citations, put the citations inside the period. This will keep the citation on the same line as the sentence if you use the --fix option. Don't worry! Pandoc is smart enough to figure out whether to put your citation after the period if you style requires it in the rendered output. For example:

Do this [@Lee2018]. Don't do this.[@Lee2019] Also don't do this. [@Lee2020]

Will be changed to:

Do this [@Lee2018].
Don't do this.[@Lee2019] Also don't do this.
[@Lee2020]

Contribute

This repository's skeleton was generated by create-textlint-rule.

Build

Builds source code for publish to the lib folder. You can write ES2015+ source code in src/ folder.

npm run build

Tests

Run test code in test folder. Test textlint rule by textlint-tester.

npm test

License

Apache-2.0 (summary)