Parses lines from text, preserving line numbers, offsets and line endings.

Usage no npm install needed!

<script type="module">
  import linez from '';



Parses lines from text, preserving line numbers, offsets and line endings.

Build Status Dependency Status npm version codecov


Getting Started


$ npm install linez



import * as linez from 'linez';


import linez from 'linez';


var linez = require('linez');


By default, linez uses /\r?\n/g as the regular expression to detect newline character sequences and split lines. This regular expression is tuned for performance and only covers the most common newline types (i.e., \n and \r\n). If you have need for more newline character sequences, you can configure linez with the configure method.

  newlines: ['\n', '\r\n', '\r', '\u000B']

Setting this property will automatically create a piped regular expression for you and use it in any future linez() calls. You can make up your own newlines if you want. Linez doesn't care one way or the other.

  newlines: ['foo', 'bar']

This would be converted into /(foo|bar)/g. Newlines are just strings. They can be anything. There are, however, some known newline character sequences. Should you need them, refer to the following table:

String Unicode Name
\n U+000A Line feed
\r\n U+000D, U+000A Carriage Return + Line Feed
\r U+000D Carriage Return
\u000B U+000B Vertical Tab
\u000C U+000C Form Feed
\u0085 U+0085 Next Line
\u2028 U+2028 Line Separator
\u2029 U+2029 Paragraph Separator

Byte Order Marks

Also referred to as BOM signatures, these are the bytes at the beginning of a file that indicating the encoding in which the file is written. Currently, linez only reads BOMs to detect the encoding and does not take into account the contents of the file.

Supported BOMs

  • utf-8-bom
  • utf-16le
  • utf-16be

Unsupported BOMs

  • utf-32le
  • utf-32be

If linez detects an unsupported BOM, an error will be thrown, indicating that decoding the detected charset is not supported.

Default decoding

By default, the document will attempt to be decoded as utf8. This is the default behavior of the Node API's conversion from buffers into strings.


configure(options: IOptions)

Configures linez to use the supplied options. Currently, only the newlines property is available, where you can specify any number of newline character sequences.

  newlines: ['\n', '\r\n', '\r', '\u000B']


Resets the configuration to the default settings, using /\r?\n/g as the newlines regular expression.


constructor(public lines: Line[]);

Calling the toString() method converts the document's lines into a string, discarding information about line numbers and offsets.


interface Line {
  offset: number;
  number: number;
  text: string;
  ending: string;


interface Options {
  newlines?: string[];

linez(file: string|Buffer): Document

Parses text into a Document.

The specs show some great usage examples.

var lines = linez('foo\nbar\nbaz').lines;
lines[1].offset; // 4
lines[1].number; // 2
lines[1].text; // bar
lines[1].ending; // \n

Note: You can also pass-in a Buffer.


Released under the MIT license.