| LOW | packages/docs/src/components/search.tsx | 41 | `url_without_anchor:${site?.origin ?? ""}${pathname}`, | COMMENT |
| LOW | packages/remeda/tsdown.config.ts | 81 | //! Even the programmatic `build` API tries to load the default config | COMMENT |
| LOW | packages/remeda/tsdown.config.ts | 141 | chunks | COMMENT |
| LOW | packages/remeda/src/groupByProp.ts | 41 | Prop extends GroupableProps<T>, | COMMENT |
| LOW | packages/remeda/src/groupByProp.ts | 61 | // because our mapped type would never run; but this doesn't represent the | COMMENT |
| LOW | packages/remeda/src/groupByProp.ts | 201 | | COMMENT |
| LOW | packages/remeda/src/startsWith.test-d.ts | 621 | // `startsWith("cat" as "cat" | "dog", "bird")` is (see "reject disjoint | COMMENT |
| LOW | packages/remeda/src/startsWith.test-d.ts | 721 | // needs `T` to find the prefix dead, doesn't match and the generic | COMMENT |
| LOW | packages/remeda/src/find.ts | 21 | // We distribute the array type to support unions of arrays/tuples. | COMMENT |
| LOW | packages/remeda/src/sample.ts | 181 | | COMMENT |
| LOW | …a/src/funnel.lodash-throttle-with-cached-value.test.ts | 101 | // (https://github.com/lodash/lodash/blob/4.17.21/test/test.js#L22768). They | COMMENT |
| LOW | packages/remeda/src/endsWith.ts | 61 | // suffix instead of any of them. Only one of them is the suffix at runtime, and | COMMENT |
| LOW | packages/remeda/src/endsWith.ts | 81 | // suffixes, which is exactly the kind of uncertainty that we are | COMMENT |
| LOW | packages/remeda/src/endsWith.ts | 201 | // the returned predicate; without one it falls back to `string`, which only | COMMENT |
| LOW | packages/remeda/src/stringToPath.ts | 1 | import type { IsNumericLiteral, IsStringLiteral } from "type-fest"; | COMMENT |
| LOW | packages/remeda/src/stringToPath.ts | 101 | // - `quoted`, `doubleQuoted`: used within square bracket notation to prevent | COMMENT |
| LOW | packages/remeda/src/endsWith.test-d.ts | 621 | // Actual: it compiles. `IsDisjointSuffix` short-circuits to `false` | COMMENT |
| LOW | packages/remeda/src/funnel.lodash-debounce.test.ts | 81 | // callback of `debounce`. In Remeda we return a proper object where the | COMMENT |
| LOW | packages/remeda/src/fromEntries.ts | 41 | // For the array case we also need to handle what kind of keys it defines: | COMMENT |
| LOW | packages/remeda/src/pickBy.ts | 21 | // `symbol` keys) we want to "reconstruct" the record from just its | COMMENT |
| LOW | …a/src/funnel.lodash-debounce-with-cached-value.test.ts | 101 | ); | COMMENT |
| LOW | packages/remeda/src/startsWith.ts | 61 | // prefix instead of any of them. Only one of them is the prefix at runtime, and | COMMENT |
| LOW | packages/remeda/src/startsWith.ts | 81 | // prefixes, which is exactly the kind of uncertainty that we are | COMMENT |
| LOW | packages/remeda/src/startsWith.ts | 201 | // the returned predicate; without one it falls back to `string`, which only | COMMENT |
| LOW | packages/remeda/src/internal/requireData.ts | 81 | ): boolean => | COMMENT |
| LOW | packages/remeda/src/internal/types/Resolved.ts | 1 | // Acts as a "inference" point that forces TypeScript to resolve during a deep | COMMENT |
| LOW | …ges/remeda/src/internal/types/NonEmptyPrefix.test-d.ts | 101 | expectTypeOf(result).toEqualTypeOf<[string, string?, string?]>(); | COMMENT |
| LOW | packages/remeda/src/internal/types/NonEmptyPrefix.ts | 61 | // the rest item. | COMMENT |
| LOW | packages/remeda/src/internal/types/ArrayAt.ts | 41 | // might be of that element's type, but it also could be any | COMMENT |
Adjusted legacy signal; badge bands: 25 / 50 / 75 (different from dashboard bands).