Search public page files, titles, headings, and visible text with stronger weighting for exact matches, filenames, headings, sections, and motorsport-related synonyms.
Because of [reasonable security doubts](https://github.com/dcodeIO/bcrypt.js/issues/16), these files, which used to be a part of bcrypt-isaac.js, are no longer used but are kept here for reference only. What is required instead is a proper way to collect entropy sources (using an intermediate stream cipher) which is th...
# `@socket.io/component-emitter` Event emitter component. This project is a fork of the [`component-emitter`](https://github.com/sindresorhus/component-emitter) project, with [Socket.IO](https://socket.io/)-specific TypeScript typings. ## Installation ``` $ npm i @socket.io/component-emitter ``` ## API ### Emitter(obj)...
...[![Version Badge][npm-version-svg]][package-url] [![github actions][actions-image]][actions-url] [![coverage][codecov-image]][codecov-url] [![License][license-image]][license-url] [![Downloads][downloads-image]][downloads-url] [![npm badge][npm-badge-png]][package-url] parse argument options This module is the guts of...
....288.46-node.13 uv@1.21.0 zlib@1.2.11 ares@1.14.0 modules@64 nghttp2@1.32.0 napi@3 openssl@1.1.0h icu@61.1 unicode@10.0 cldr@33.0 tz@2018c > node benchmark/fullurl.js Parsing URL "http://localhost:8888/foo/bar?user=tj&pet=fluffy" 4 tests completed. fasturl x 2,207,842 ops/sec ±3.76% (184 runs sampled) nativeurl - legac...
# axios // core The modules found in `core/` should be modules that are specific to the domain logic of axios. These modules would most likely not make sense to be consumed outside of the axios module, as their logic is too specific. Some examples of core modules are: - Dispatching requests - Requests sent via `adapter...
...ing` Normalize user name or password. ##### `Options.allowUnassigned: bool` A special behavior for unassigned code points, see https://tools.ietf.org/html/rfc4013#section-2.5. Disabled by default. ## License MIT, 2017-2019 (c) Dmitriy Tsvettsikh
...s(size, callback) Generates strong pseudo-random bytes. The `size` argument is a number indicating the number of bytes to generate. ```js randomBytes(12, function (error, bytes) { if (error) throw error // do something with the bytes }) ``` ### randomBytes(size) Generates strong pseudo-random bytes and return a `Promis...
...') ``` ### parseRange(size, header, options) Parse the given `header` string where `size` is the maximum size of the resource. An array of ranges will be returned or negative numbers indicating an error parsing. * `-2` signals a malformed header string * `-1` signals an unsatisfiable range ```js // parse header from re...
...Node.js core, with the following differences: * All method names are lower-cased. * Contains a fallback list of methods for Node.js versions that do not have a `http.METHODS` export (0.10 and lower). * Provides the fallback list when using tools like `browserify` without pulling in the `http` shim module. ## Install `...
# sparse-bitfield Bitfield implementation that allocates a series of 1kb buffers to support sparse bitfields without allocating a massive buffer. If you want to simple implementation of a flat bitfield see the [bitfield](https://github.com/fb55/bitfield) module. This module is mostly useful if you need a big bitfield w...
...imple `stream.destroy()` call. The rules are as follows for a given stream: 1. If the `stream` is an instance of `ReadStream`, then call `stream.destroy()` and add a listener to the `open` event to call `stream.close()` if it is fired. This is for a Node.js bug that will leak a file descriptor if `.destroy()` is called...
Because of [reasonable security doubts](https://github.com/dcodeIO/bcrypt.js/issues/16), these files, which used to be a part of bcrypt-isaac.js, are no longer used but are kept here for reference only. What is required instead is a proper way to collect entropy sources (using an intermediate stream cipher) which is th...
