The buffer-based encoding utility method for node.js.

Following types of encodings are supported:

Encoding urlencode

This is a real urlencode implement, it will escape all bytes as %xx format, excepting A-Z, a-z and 0-9. This is a binary-safe encoding.

Binary-safe means it could work with binary data perfectly, without gibberish. And it’s all the same below.

Encoding uri

This is a simple reference of method encodeURIComponent, so it works as method encodeURIComponent does. And it’s not a binary-safe encoding.

Encoding strict_uri

This is based on uri, but all special chars including "-", ".", "_", "!", "*", "(", ")", "~", "'" will be escaped. However, it’s still not a binary-safe encoding.

NOTE: The data of strict_uri encoding, could be simply decoded by function decodeURIComponent.

Encoding base64url

This is based on base64, while charactors "=", "+", "/" will be replaced with URL-safe charactors. This is a binary-safe encoding.

Encoding base62x

This is a variation of base64. And it is a binary-safe encoding.

Installation

1npm install @litert/encodings@^2.3.0

v2.3.0 CHANGELOG

• config(deps): updated dependencies.
• fix(encoding): fixed decoding of the urlencode.
• build(test): added test cases.
• build(project): upgraded the minimum version of Node.js to v14.

Another strange problem in Bug 11, the “Slideshow” in the lock screen doesn’t work at all. No matter how you choose the images directory, it always shows two kinds of error messages:

• The directory you selected cannot be used as the picture directory.
• You need more than one picture for slideshow

However, if you choose a single image in “Picture” mode, it can display normally.

All right, I can’t stand M$ stupid engineers anymore, so let’s solve this problem with a Powershell script.

A strange problem in Bug 10 and Bug 11, the “New Text Document” option in the right-click menu of the File Explorer sometimes disappears for no reason.

Microsoft’s products really smell like sh*t today.

One day, when I tried connecting to a host by SSH, I got errors like Received disconnect from xxxxx port 22:2: Too many authentication failures, what’s going on?

@litert/redis is a Redis client library developed entirely in TypeScript, for NodeJS.

All asynchronous operations are based on Promise, and it supports transactions and messaging.

Features

• Support read/write separation.
• Support pipeline.
• Support multi and exec.
• Support subscribe and publish.

Installation

1npm install @litert/redis@^3.0.2

v3.0.2 CHANGES

• fix(command): Incorrect preprocessing of arguments for SREM command.
• feat(command): Added basic supports for ZADD, ZREM, ZRANGE commands.
• fix(docs): Fixed the links to the command documents.
• build(test): Initialized test flows.

Contributors

• @superxrb #9