windows-1251 - npm Package Compare versions

Comparing version 3.0.1 to 3.0.2

package.json

		{
		"name": "windows-1251",
		"version": "3.0.1",
		"version": "3.0.2",
		"description": "A robust windows-1251 encoder/decoder written in JavaScript.",
		@@ -5,0 +5,0 @@ "homepage": "https://mths.be/windows-1251",

README.md

		@@ -37,3 +37,3 @@ # windows-1251 [![Build status](https://github.com/mathiasbynens/windows-1251/workflows/run-checks/badge.svg)](https://github.com/mathiasbynens/windows-1251/actions?query=workflow%3Arun-checks) [![windows-1251 on npm](https://img.shields.io/npm/v/windows-1251)](https://www.npmjs.com/package/windows-1251)

		The optional `options` object and its `mode` property can be used to set the error mode. The two available error modes are `'fatal'` (the default) or `'replacement'`. (Note: This differs from [the spec](https://encoding.spec.whatwg.org/#error-mode), which recognizes `'fatal`' and `html` modes for encoders. The reason behind this difference is that the spec algorithm is aimed at producing HTML, whereas this library encodes into an environment-agnostic `Uint16Array` of bytes.)
		The optional `options` object and its `mode` property can be used to set the error mode. The two available error modes are `'fatal'` (the default) or `'replacement'`. (Note: This differs from [the spec](https://encoding.spec.whatwg.org/#error-mode), which recognizes “fatal” and HTML” modes for encoders. The reason behind this difference is that the spec algorithm is aimed at producing HTML, whereas this library encodes into an environment-agnostic `Uint16Array` of bytes.)

		@@ -40,0 +40,0 @@ ```js

windows-1251.mjs

Sorry, the diff of this file is not supported yet

New alerts