recoder-code 2.4.1 → 2.4.2

package/packages/cli/node_modules/tough-cookie/dist/cookie/parseDate.js

@@ -1,323 +0,0 @@
-"use strict";
-// date-time parsing constants (RFC6265 S5.1.1)
-Object.defineProperty(exports, "__esModule", { value: true });
-exports.parseDate = parseDate;
-// eslint-disable-next-line no-control-regex
-const DATE_DELIM = /[\x09\x20-\x2F\x3B-\x40\x5B-\x60\x7B-\x7E]/;
-const MONTH_TO_NUM = {
-    jan: 0,
-    feb: 1,
-    mar: 2,
-    apr: 3,
-    may: 4,
-    jun: 5,
-    jul: 6,
-    aug: 7,
-    sep: 8,
-    oct: 9,
-    nov: 10,
-    dec: 11,
-};
-/*
- * Parses a Natural number (i.e., non-negative integer) with either the
- *    <min>*<max>DIGIT ( non-digit *OCTET )
- * or
- *    <min>*<max>DIGIT
- * grammar (RFC6265 S5.1.1).
- *
- * The "trailingOK" boolean controls if the grammar accepts a
- * "( non-digit *OCTET )" trailer.
- */
-function parseDigits(token, minDigits, maxDigits, trailingOK) {
-    let count = 0;
-    while (count < token.length) {
-        const c = token.charCodeAt(count);
-        // "non-digit = %x00-2F / %x3A-FF"
-        if (c <= 0x2f || c >= 0x3a) {
-            break;
-        }
-        count++;
-    }
-    // constrain to a minimum and maximum number of digits.
-    if (count < minDigits || count > maxDigits) {
-        return;
-    }
-    if (!trailingOK && count != token.length) {
-        return;
-    }
-    return parseInt(token.slice(0, count), 10);
-}
-function parseTime(token) {
-    const parts = token.split(':');
-    const result = [0, 0, 0];
-    /* RF6256 S5.1.1:
-     *      time            = hms-time ( non-digit *OCTET )
-     *      hms-time        = time-field ":" time-field ":" time-field
-     *      time-field      = 1*2DIGIT
-     */
-    if (parts.length !== 3) {
-        return;
-    }
-    for (let i = 0; i < 3; i++) {
-        // "time-field" must be strictly "1*2DIGIT", HOWEVER, "hms-time" can be
-        // followed by "( non-digit *OCTET )" therefore the last time-field can
-        // have a trailer
-        const trailingOK = i == 2;
-        const numPart = parts[i];
-        if (numPart === undefined) {
-            return;
-        }
-        const num = parseDigits(numPart, 1, 2, trailingOK);
-        if (num === undefined) {
-            return;
-        }
-        result[i] = num;
-    }
-    return result;
-}
-function parseMonth(token) {
-    token = String(token).slice(0, 3).toLowerCase();
-    switch (token) {
-        case 'jan':
-            return MONTH_TO_NUM.jan;
-        case 'feb':
-            return MONTH_TO_NUM.feb;
-        case 'mar':
-            return MONTH_TO_NUM.mar;
-        case 'apr':
-            return MONTH_TO_NUM.apr;
-        case 'may':
-            return MONTH_TO_NUM.may;
-        case 'jun':
-            return MONTH_TO_NUM.jun;
-        case 'jul':
-            return MONTH_TO_NUM.jul;
-        case 'aug':
-            return MONTH_TO_NUM.aug;
-        case 'sep':
-            return MONTH_TO_NUM.sep;
-        case 'oct':
-            return MONTH_TO_NUM.oct;
-        case 'nov':
-            return MONTH_TO_NUM.nov;
-        case 'dec':
-            return MONTH_TO_NUM.dec;
-        default:
-            return;
-    }
-}
-/**
- * Parse a cookie date string into a {@link https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Date | Date}. Parses according to
- * {@link https://www.rfc-editor.org/rfc/rfc6265.html#section-5.1.1 | RFC6265 - Section 5.1.1}, not
- * {@link https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Date/parse | Date.parse()}.
- *
- * @remarks
- *
- * ### RFC6265 - 5.1.1. Dates
- *
- * The user agent MUST use an algorithm equivalent to the following
- * algorithm to parse a cookie-date.  Note that the various boolean
- * flags defined as a part of the algorithm (i.e., found-time, found-
- * day-of-month, found-month, found-year) are initially "not set".
- *
- * 1.  Using the grammar below, divide the cookie-date into date-tokens.
- *
- * ```
- *     cookie-date     = *delimiter date-token-list *delimiter
- *     date-token-list = date-token *( 1*delimiter date-token )
- *     date-token      = 1*non-delimiter
- *
- *     delimiter       = %x09 / %x20-2F / %x3B-40 / %x5B-60 / %x7B-7E
- *     non-delimiter   = %x00-08 / %x0A-1F / DIGIT / ":" / ALPHA / %x7F-FF
- *     non-digit       = %x00-2F / %x3A-FF
- *
- *     day-of-month    = 1*2DIGIT ( non-digit *OCTET )
- *     month           = ( "jan" / "feb" / "mar" / "apr" /
- *                        "may" / "jun" / "jul" / "aug" /
- *                        "sep" / "oct" / "nov" / "dec" ) *OCTET
- *     year            = 2*4DIGIT ( non-digit *OCTET )
- *     time            = hms-time ( non-digit *OCTET )
- *     hms-time        = time-field ":" time-field ":" time-field
- *     time-field      = 1*2DIGIT
- * ```
- *
- * 2. Process each date-token sequentially in the order the date-tokens
- *     appear in the cookie-date:
- *
- *     1. If the found-time flag is not set and the token matches the
- *         time production, set the found-time flag and set the hour-
- *         value, minute-value, and second-value to the numbers denoted
- *         by the digits in the date-token, respectively.  Skip the
- *         remaining sub-steps and continue to the next date-token.
- *
- *     2. If the found-day-of-month flag is not set and the date-token
- *         matches the day-of-month production, set the found-day-of-
- *         month flag and set the day-of-month-value to the number
- *         denoted by the date-token.  Skip the remaining sub-steps and
- *         continue to the next date-token.
- *
- *     3. If the found-month flag is not set and the date-token matches
- *         the month production, set the found-month flag and set the
- *         month-value to the month denoted by the date-token.  Skip the
- *         remaining sub-steps and continue to the next date-token.
- *
- *     4. If the found-year flag is not set and the date-token matches
- *         the year production, set the found-year flag and set the
- *         year-value to the number denoted by the date-token.  Skip the
- *         remaining sub-steps and continue to the next date-token.
- *
- *  3. If the year-value is greater than or equal to 70 and less than or
- *      equal to 99, increment the year-value by 1900.
- *
- *  4. If the year-value is greater than or equal to 0 and less than or
- *      equal to 69, increment the year-value by 2000.
- *
- *      1. NOTE: Some existing user agents interpret two-digit years differently.
- *
- *  5. Abort these steps and fail to parse the cookie-date if:
- *
- *      - at least one of the found-day-of-month, found-month, found-
- *          year, or found-time flags is not set,
- *
- *      - the day-of-month-value is less than 1 or greater than 31,
- *
- *      - the year-value is less than 1601,
- *
- *      - the hour-value is greater than 23,
- *
- *      - the minute-value is greater than 59, or
- *
- *      - the second-value is greater than 59.
- *
- *      (Note that leap seconds cannot be represented in this syntax.)
- *
- *  6. Let the parsed-cookie-date be the date whose day-of-month, month,
- *      year, hour, minute, and second (in UTC) are the day-of-month-
- *      value, the month-value, the year-value, the hour-value, the
- *      minute-value, and the second-value, respectively.  If no such
- *      date exists, abort these steps and fail to parse the cookie-date.
- *
- *  7. Return the parsed-cookie-date as the result of this algorithm.
- *
- * @example
- * ```
- * parseDate('Wed, 09 Jun 2021 10:18:14 GMT')
- * ```
- *
- * @param cookieDate - the cookie date string
- * @public
- */
-function parseDate(cookieDate) {
-    if (!cookieDate) {
-        return;
-    }
-    /* RFC6265 S5.1.1:
-     * 2. Process each date-token sequentially in the order the date-tokens
-     * appear in the cookie-date
-     */
-    const tokens = cookieDate.split(DATE_DELIM);
-    let hour;
-    let minute;
-    let second;
-    let dayOfMonth;
-    let month;
-    let year;
-    for (let i = 0; i < tokens.length; i++) {
-        const token = (tokens[i] ?? '').trim();
-        if (!token.length) {
-            continue;
-        }
-        /* 2.1. If the found-time flag is not set and the token matches the time
-         * production, set the found-time flag and set the hour- value,
-         * minute-value, and second-value to the numbers denoted by the digits in
-         * the date-token, respectively.  Skip the remaining sub-steps and continue
-         * to the next date-token.
-         */
-        if (second === undefined) {
-            const result = parseTime(token);
-            if (result) {
-                hour = result[0];
-                minute = result[1];
-                second = result[2];
-                continue;
-            }
-        }
-        /* 2.2. If the found-day-of-month flag is not set and the date-token matches
-         * the day-of-month production, set the found-day-of- month flag and set
-         * the day-of-month-value to the number denoted by the date-token.  Skip
-         * the remaining sub-steps and continue to the next date-token.
-         */
-        if (dayOfMonth === undefined) {
-            // "day-of-month = 1*2DIGIT ( non-digit *OCTET )"
-            const result = parseDigits(token, 1, 2, true);
-            if (result !== undefined) {
-                dayOfMonth = result;
-                continue;
-            }
-        }
-        /* 2.3. If the found-month flag is not set and the date-token matches the
-         * month production, set the found-month flag and set the month-value to
-         * the month denoted by the date-token.  Skip the remaining sub-steps and
-         * continue to the next date-token.
-         */
-        if (month === undefined) {
-            const result = parseMonth(token);
-            if (result !== undefined) {
-                month = result;
-                continue;
-            }
-        }
-        /* 2.4. If the found-year flag is not set and the date-token matches the
-         * year production, set the found-year flag and set the year-value to the
-         * number denoted by the date-token.  Skip the remaining sub-steps and
-         * continue to the next date-token.
-         */
-        if (year === undefined) {
-            // "year = 2*4DIGIT ( non-digit *OCTET )"
-            const result = parseDigits(token, 2, 4, true);
-            if (result !== undefined) {
-                year = result;
-                /* From S5.1.1:
-                 * 3.  If the year-value is greater than or equal to 70 and less
-                 * than or equal to 99, increment the year-value by 1900.
-                 * 4.  If the year-value is greater than or equal to 0 and less
-                 * than or equal to 69, increment the year-value by 2000.
-                 */
-                if (year >= 70 && year <= 99) {
-                    year += 1900;
-                }
-                else if (year >= 0 && year <= 69) {
-                    year += 2000;
-                }
-            }
-        }
-    }
-    /* RFC 6265 S5.1.1
-     * "5. Abort these steps and fail to parse the cookie-date if:
-     *     *  at least one of the found-day-of-month, found-month, found-
-     *        year, or found-time flags is not set,
-     *     *  the day-of-month-value is less than 1 or greater than 31,
-     *     *  the year-value is less than 1601,
-     *     *  the hour-value is greater than 23,
-     *     *  the minute-value is greater than 59, or
-     *     *  the second-value is greater than 59.
-     *     (Note that leap seconds cannot be represented in this syntax.)"
-     *
-     * So, in order as above:
-     */
-    if (dayOfMonth === undefined ||
-        month === undefined ||
-        year === undefined ||
-        hour === undefined ||
-        minute === undefined ||
-        second === undefined ||
-        dayOfMonth < 1 ||
-        dayOfMonth > 31 ||
-        year < 1601 ||
-        hour > 23 ||
-        minute > 59 ||
-        second > 59) {
-        return;
-    }
-    return new Date(Date.UTC(year, month, dayOfMonth, hour, minute, second));
-}

package/packages/cli/node_modules/tough-cookie/dist/cookie/permutePath.d.ts

@@ -1,14 +0,0 @@
-/**
- * Generates the permutation of all possible values that {@link pathMatch} the `path` parameter.
- * The array is in longest-to-shortest order.  Useful when building custom {@link Store} implementations.
- *
- * @example
- * ```
- * permutePath('/foo/bar/')
- * // ['/foo/bar/', '/foo/bar', '/foo', '/']
- * ```
- *
- * @param path - the path to generate permutations for
- * @public
- */
-export declare function permutePath(path: string): string[];

package/packages/cli/node_modules/tough-cookie/dist/cookie/permutePath.js

@@ -1,32 +0,0 @@
-"use strict";
-Object.defineProperty(exports, "__esModule", { value: true });
-exports.permutePath = permutePath;
-/**
- * Generates the permutation of all possible values that {@link pathMatch} the `path` parameter.
- * The array is in longest-to-shortest order.  Useful when building custom {@link Store} implementations.
- *
- * @example
- * ```
- * permutePath('/foo/bar/')
- * // ['/foo/bar/', '/foo/bar', '/foo', '/']
- * ```
- *
- * @param path - the path to generate permutations for
- * @public
- */
-function permutePath(path) {
-    if (path === '/') {
-        return ['/'];
-    }
-    const permutations = [path];
-    while (path.length > 1) {
-        const lindex = path.lastIndexOf('/');
-        if (lindex === 0) {
-            break;
-        }
-        path = path.slice(0, lindex);
-        permutations.push(path);
-    }
-    permutations.push('/');
-    return permutations;
-}

package/packages/cli/node_modules/tough-cookie/dist/getPublicSuffix.d.ts

@@ -1,55 +0,0 @@
-/**
- * Options for configuring how {@link getPublicSuffix} behaves.
- * @public
- */
-export interface GetPublicSuffixOptions {
-    /**
-     * If set to `true` then the following {@link https://www.rfc-editor.org/rfc/rfc6761.html | Special Use Domains} will
-     * be treated as if they were valid public suffixes ('local', 'example', 'invalid', 'localhost', 'test').
-     *
-     * @remarks
-     * In testing scenarios it's common to configure the cookie store with so that `http://localhost` can be used as a domain:
-     * ```json
-     * {
-     *   allowSpecialUseDomain: true,
-     *   rejectPublicSuffixes: false
-     * }
-     * ```
-     *
-     * @defaultValue false
-     */
-    allowSpecialUseDomain?: boolean | undefined;
-    /**
-     * If set to `true` then any errors that occur while executing {@link getPublicSuffix} will be silently ignored.
-     *
-     * @defaultValue false
-     */
-    ignoreError?: boolean | undefined;
-}
-/**
- * Returns the public suffix of this hostname. The public suffix is the shortest domain
- * name upon which a cookie can be set.
- *
- * @remarks
- * A "public suffix" is a domain that is controlled by a
- * public registry, such as "com", "co.uk", and "pvt.k12.wy.us".
- * This step is essential for preventing attacker.com from
- * disrupting the integrity of example.com by setting a cookie
- * with a Domain attribute of "com".  Unfortunately, the set of
- * public suffixes (also known as "registry controlled domains")
- * changes over time.  If feasible, user agents SHOULD use an
- * up-to-date public suffix list, such as the one maintained by
- * the Mozilla project at http://publicsuffix.org/.
- * (See {@link https://www.rfc-editor.org/rfc/rfc6265.html#section-5.3 | RFC6265 - Section 5.3})
- *
- * @example
- * ```
- * getPublicSuffix('www.example.com') === 'example.com'
- * getPublicSuffix('www.subdomain.example.com') === 'example.com'
- * ```
- *
- * @param domain - the domain attribute of a cookie
- * @param options - optional configuration for controlling how the public suffix is determined
- * @public
- */
-export declare function getPublicSuffix(domain: string, options?: GetPublicSuffixOptions): string | undefined;

package/packages/cli/node_modules/tough-cookie/dist/getPublicSuffix.js

@@ -1,71 +0,0 @@
-"use strict";
-Object.defineProperty(exports, "__esModule", { value: true });
-exports.getPublicSuffix = getPublicSuffix;
-const tldts_1 = require("tldts");
-// RFC 6761
-const SPECIAL_USE_DOMAINS = ['local', 'example', 'invalid', 'localhost', 'test'];
-const SPECIAL_TREATMENT_DOMAINS = ['localhost', 'invalid'];
-const defaultGetPublicSuffixOptions = {
-    allowSpecialUseDomain: false,
-    ignoreError: false,
-};
-/**
- * Returns the public suffix of this hostname. The public suffix is the shortest domain
- * name upon which a cookie can be set.
- *
- * @remarks
- * A "public suffix" is a domain that is controlled by a
- * public registry, such as "com", "co.uk", and "pvt.k12.wy.us".
- * This step is essential for preventing attacker.com from
- * disrupting the integrity of example.com by setting a cookie
- * with a Domain attribute of "com".  Unfortunately, the set of
- * public suffixes (also known as "registry controlled domains")
- * changes over time.  If feasible, user agents SHOULD use an
- * up-to-date public suffix list, such as the one maintained by
- * the Mozilla project at http://publicsuffix.org/.
- * (See {@link https://www.rfc-editor.org/rfc/rfc6265.html#section-5.3 | RFC6265 - Section 5.3})
- *
- * @example
- * ```
- * getPublicSuffix('www.example.com') === 'example.com'
- * getPublicSuffix('www.subdomain.example.com') === 'example.com'
- * ```
- *
- * @param domain - the domain attribute of a cookie
- * @param options - optional configuration for controlling how the public suffix is determined
- * @public
- */
-function getPublicSuffix(domain, options = {}) {
-    options = { ...defaultGetPublicSuffixOptions, ...options };
-    const domainParts = domain.split('.');
-    const topLevelDomain = domainParts[domainParts.length - 1];
-    const allowSpecialUseDomain = !!options.allowSpecialUseDomain;
-    const ignoreError = !!options.ignoreError;
-    if (allowSpecialUseDomain &&
-        topLevelDomain !== undefined &&
-        SPECIAL_USE_DOMAINS.includes(topLevelDomain)) {
-        if (domainParts.length > 1) {
-            // eslint-disable-next-line @typescript-eslint/no-non-null-assertion
-            const secondLevelDomain = domainParts[domainParts.length - 2];
-            // In aforementioned example, the eTLD/pubSuf will be apple.localhost
-            return `${secondLevelDomain}.${topLevelDomain}`;
-        }
-        else if (SPECIAL_TREATMENT_DOMAINS.includes(topLevelDomain)) {
-            // For a single word special use domain, e.g. 'localhost' or 'invalid', per RFC 6761,
-            // "Application software MAY recognize {localhost/invalid} names as special, or
-            // MAY pass them to name resolution APIs as they would for other domain names."
-            return topLevelDomain;
-        }
-    }
-    if (!ignoreError &&
-        topLevelDomain !== undefined &&
-        SPECIAL_USE_DOMAINS.includes(topLevelDomain)) {
-        throw new Error(`Cookie has domain set to the public suffix "${topLevelDomain}" which is a special use domain. To allow this, configure your CookieJar with {allowSpecialUseDomain: true, rejectPublicSuffixes: false}.`);
-    }
-    const publicSuffix = (0, tldts_1.getDomain)(domain, {
-        allowIcannDomains: true,
-        allowPrivateDomains: true,
-    });
-    if (publicSuffix)
-        return publicSuffix;
-}