Title: generic type parameters, for generic call expressions, not reduced to canonical form, causing type inference malfuction and errors · Issue #56702 · microsoft/TypeScript · GitHub
Open Graph Title: generic type parameters, for generic call expressions, not reduced to canonical form, causing type inference malfuction and errors · Issue #56702 · microsoft/TypeScript
X Title: generic type parameters, for generic call expressions, not reduced to canonical form, causing type inference malfuction and errors · Issue #56702 · microsoft/TypeScript
Description: 🔎 Search Terms type reduction fails generic function return type inference fails Couldn't find any issues that match this one sufficiently. 🕗 Version & Regression Information This is the behavior in every version I tried up to 5.3.2. ⏯ P...
Open Graph Description: 🔎 Search Terms type reduction fails generic function return type inference fails Couldn't find any issues that match this one sufficiently. 🕗 Version & Regression Information This is the behavior i...
X Description: 🔎 Search Terms type reduction fails generic function return type inference fails Couldn't find any issues that match this one sufficiently. 🕗 Version & Regression Information This is the be...
Opengraph URL: https://github.com/microsoft/TypeScript/issues/56702
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"generic type parameters, for generic call expressions, not reduced to canonical form, causing type inference malfuction and errors","articleBody":"### 🔎 Search Terms\r\n\r\n- type reduction fails \r\n- generic function return type inference fails\r\n\r\nCouldn't find any issues that match this one sufficiently.\r\n\r\n\r\n### 🕗 Version & Regression Information\r\n\r\nThis is the behavior in every version I tried up to 5.3.2.\r\n\r\n### ⏯ Playground Link\r\n\r\n[playground](https://www.typescriptlang.org/play?ts=5.3.2#code/JYWwDg9gTgLgBAbzgEwKYDMCGBXANvTAZzgBI4BfOdKCEOAcgCsBHbVKAT3oG4AoUSLDgApAIptOVGnSat2XPrwDGEAHaF4MAIwAuOBqjBVAczgAfEePkAeABIAVALIAZAKK5UIVKpgA+c3DYqmjoRqjIcAC8pAAUAJTccAD0SXCqEHDsNFC8ymoacDAATHoxMQZGphZiEhx2Tm4eXj6+cXAAZHDlMIYmATU2Di7unt5+AUEhYchxbRaTGNNRsQnJqVnQvClwO3AAfntbqfYcYKgMA5zWFX0WQ42jLfRwwMTpBISEwMaqmABGHkKGRgp3O9DKNyqllq9WGTTGrQ6XUh-SsV3uI2a43mwUWqnCswmuNC+OQ9AAdEcdiczhc0XUUXcGpiEc9XmkIB8vj9-oCYMDQXSYRj4U9KdtdjSwYy4CLHjA2W9OXAiNzfgDzvzCoL6HKsRSqbtqTrIYqOVzvuq+QLabrmaKFeSYkUAMxFIpxXIqdSaLS6fQ9Sqo4X2+X+aIkeKJbbpTJQbJe-K+krIwO3aGDUNYxGdbq9KGXOp6hFEqaktoRqNrOMJiU7A5UqVCmwy4tPF5Ki08jVA7W2mWF2EPbMBPNBzqDtt+OZdSdZkudSFxA0Spv0Qet+ft9nvFWfS28zU2sFzuFhg15H0ZzgAfRR0Q3aeMvmj63jm22a9NKAgqE7+kwGBXnQDhCgAC3Ob0DEwIx4HoFkfApZ0XQAFhQz1PxNJ9nmQX9-0IQDgNAmAILgKCehgnwGCnJDXTQjDjiw-McLw80AKAwgQPAyCkygSi4IABVwSiAHk-kYVAlBgaxMFUDhfFo1D0N4IA)\r\n\r\n### 💻 Code\r\n\r\n```ts\r\nimport { default as $ } from 'jquery';\r\nimport JQuery from 'jquery';\r\n\r\nconst t1: string | JQuery\u003cHTMLElement> | undefined = $(); // no error\r\n\r\nconst t2: ((string | JQuery\u003cHTMLElement>) & (string | JQuery\u003cHTMLElement> | undefined)) | undefined = $(); // error\r\n// ~~\r\n// Type 'JQuery\u003cstring | HTMLElement>' is not assignable to type '((string | JQuery\u003cHTMLElement>) & (string | JQuery\u003cHTMLElement> | undefined)) | undefined'.\r\n// Type 'JQuery\u003cstring | HTMLElement>' is not assignable to type 'JQuery\u003cHTMLElement>'.\r\n// Type 'string | HTMLElement' is not assignable to type 'HTMLElement'.\r\n// Type 'string' is not assignable to type 'HTMLElement'.(2322)\r\n\r\nconst t11: string | JQuery\u003cHTMLElement> = $(); // no error\r\n\r\nconst t12: (string | JQuery\u003cHTMLElement>) & (string | JQuery\u003cHTMLElement> | undefined) = $(); // error\r\n// ~~\r\n// Type 'JQuery\u003cstring | HTMLElement>' is not assignable to type 'string | JQuery\u003cHTMLElement> | (string & JQuery\u003cHTMLElement>) | (JQuery\u003cHTMLElement> & string)'.\r\n// Type 'JQuery\u003cstring | HTMLElement>' is not assignable to type 'JQuery\u003cHTMLElement>'.\r\n\r\nconst JQuery_string = JQuery\u003cstring>; // error\r\n// Type 'string' does not satisfy the constraint 'Element'.(2344)\r\n// Type 'string' does not satisfy the constraint 'HTMLElement'.(2344)\r\n// Type 'string' does not satisfy the constraint 'PlainObject\u003cany>'.(2344)\r\n```\r\n\r\n\r\n### 🙁 Actual behavior\r\n\r\n1. Even though the type declarations for `t1` and `t2` are the same (after reduction), only `t2` shows an error. The same relationship exists between `t11` and `t12`. \r\n\r\n2. The return type of assigned to `t1` is `string | JQuery\u003cHTMLElement> | undefined`.\r\n\r\n### 🙂 Expected behavior\r\n\r\n1. `t1` and `t2` should have the same error status. Likewise for `t11` and `t12`.\r\n\r\n2. The jQuery function `$()` has a generic signature `\u003cTElement=HTMLElement>() JQuery\u003cTElement>`. So the return type assigned to `t1` should be `JQuery\u003cstring> | JQuery\u003cHTMLElement> | JQuery\u003cundefined>`.\r\n\r\n3. As shown at the bottom of the code, `JQuery\u003cstring>` is judged to be an invalid instantiation of JQuery. If so, the lines with `t1` and `t2` should both be errors, but they are not. However, the actual declaration for the interface JQuery seems to be \r\n```\r\ninterface JQuery\u003cTElement = HTMLElement> extends Iterable\u003cTElement>\r\n```\r\nwhich actually doesn't look as though it should constraint the domain of JQuery to HTMLElement, so perhaps `JQuery\u003cstring>` should not be an error? Furthermore, from within a `DefinitelyTyped/semantic-ui` test file, `JQuery\u003cstring>` does not incur an error.\r\n\r\n### Additional information about the issue\r\n\r\n#### Origin of strange declaration type\r\n\r\nI explain where the weird declaration types (e.g. `(string | JQuery\u003cHTMLElement>) & (string | JQuery\u003cHTMLElement> | undefined) `) came from.\r\n\r\nThe following is quoted and condensed from filles under `DefinitelyTyped/semantic-ui-search`\r\n```\r\nimport { default as $ } from 'jquery';\r\n\r\ninterface _Impl {\r\n stateContext: string | JQuery;\r\n};\r\n\r\ntype Param =\r\n & (\r\n | Pick\u003c_Impl, \"stateContext\">\r\n )\r\n & Partial\u003cPick\u003c_Impl, keyof _Impl>>;\r\n```\r\nThe type of `Param[\"stateContext\"]` is indeed the weird type:\r\n```\r\ntype StateContext = Param[\"stateContext\"];\r\n// ^? (string | JQuery\u003cHTMLElement>) & (string | JQuery\u003cHTMLElement> | undefined)\r\n```\r\nThe error can then be incurred as follows:\r\n```\r\nconst p: Param = {\r\n stateContext: $()\r\n// ~~\r\n// Type 'JQuery\u003cstring | HTMLElement>' is not assignable \r\n// to type '(string | JQuery\u003cHTMLElement>) & (string | JQuery\u003cHTMLElement> | undefined)'.(2322)\r\n}\r\n```\r\n[playground](https://www.typescriptlang.org/play?#code/JYWwDg9gTgLgBAbzgEwKYDMCGBXANvTAZzgBI4BfOdKCEOAcgCsBHbVKAT3oG4AoX4ADsY7LAGNUcAPoBJcLkS84yuIRiYRAYQjDUADxgAuVTChCA5nAA+cAFIBFNpz7k+vGBzCSACpiiY6AF4lFQAyOAAKEJUVG29gMQBrAB5ZeQAaOAAiNQ1UbV0DLIA+aLgASjLw31hgTFxk+KTUuTBcTMTUDgh0aVbcYuK3Dy84AGV1LR0RAzhAuBqAgG0cyfzp-RgsgF0+AHo9lQA9AH5lCLUzQUsbBycOZIAJABUAWQAZAFFcVBBUYWK5Tg4Qupgs1jsjnYDxeH2+v3+MGKEOwgjQ6CEqGQlV4Yh0ajgYGMiyCihiuSmhSMpAilQOygAfgzePTnp5JPQ7tDkpdwTZYV8fn8AfQ4MBiIIIARCIRgOZBJgAEY-OAsw4wCBwEYc0FXG6Q+5PN6ChEAoEg3nXCFczhGuFCxHImyo9GY7H0AB0EQATABmb3eyrkXhAA)\r\n\r\n#### Relation to issue #56013 and pull #56373\r\n\r\nThe submitted pull pull #56373 for the bug in issue #56013 resulted in [similar errors](https://github.com/microsoft/TypeScript/pull/56373#issuecomment-1828763860) to this report. That's because the bug #56013 is due to improper caching of generic call expression arguments, resulting in the call expression not be re-evaluated when the context changed. When the fix allows that later evaluation, those latent errors appear in the existing test code under `DefinitelyTyped/semantic-ui`. \r\n\r\nAn obvious \"patchy\" fix would be to write new code to force reduction just in time at the critical point - but it could be called multiple times. A better fix would be to do the reduction once when the declaration is parsed - but there is likely some reason it wasn't done that way. Some feedback from the original designers would be helpful.\r\n\r\n\r\n-----------------------------------------------------------------------------------\r\nUPDATE:\r\n\r\n## Stand alone code with pseudo jQuery\r\n\r\n```\r\ninterface JQuery\u003cTElement = HTMLElement> {\r\n something: any;\r\n // Change `[Symbol.iterator]` to `other` and the error goes away\r\n [Symbol.iterator]: () => {\r\n // Change `next` to `foo` and the error goes away\r\n next(): {\r\n value: TElement;\r\n }\r\n | {\r\n done: true;\r\n value: any;\r\n };\r\n }\r\n}\r\n\r\ndeclare function jQuery\u003cTElement = HTMLElement>(): JQuery\u003cTElement>;\r\n\r\nconst t11: string | JQuery\u003cHTMLElement> = jQuery(); // no error\r\n\r\nconst t12: (string | JQuery\u003cHTMLElement>) & (string | JQuery\u003cHTMLElement> | undefined) = jQuery(); // error\r\n// ~~\r\n// Type 'JQuery\u003cstring | HTMLElement>' is not assignable to type '(string | JQuery\u003cHTMLElement>) & (string | JQuery\u003cHTMLElement> | undefined)'.\r\n// Type 'JQuery\u003cstring | HTMLElement>' is not assignable to type 'JQuery\u003cHTMLElement>'.ts(2322)\r\n\r\nconst ta: string = jQuery(); // error\r\n// ?^ jQuery\u003cHTMLElement>(): JQuery\u003cHTMLElement>\r\nconst tb: JQuery\u003cHTMLElement> = jQuery(); // no error\r\n// ^? jQuery\u003cHTMLElement>(): JQuery\u003cHTMLElement>\r\nconst tc: string & JQuery\u003cHTMLElement> = jQuery(); // error\r\n// ^? // jQuery\u003cHTMLElement>(): JQuery\u003cHTMLElement>\r\nconst td: JQuery\u003cHTMLElement> & string = jQuery(); // error\r\n// ?^ // jQuery\u003cstring>(): JQuery\u003cstring>\r\n```\r\n[playground](https://www.typescriptlang.org/play?#code/JYOwLgpgTgZghgYwgAgFIEUCu0CeAeAFQFEAbCAWwnGQF5kAJAgWQBlSKqwA+ZAbwChkQ5AGcA9pTAALUAHMAXMjggcAbkHCA9JuQBhKctkoABgG0AyjnIAjMSQB0wSFDhgxUALrHkb5MbHS0N7KACY+UijQUO7IsmIQIkoA7nA4GkIWVrYOTtCu7h6KABQAlLQ8AsJVyNp6BiBGfiAQAB5g3r7GMGJiwSBhgchRMXEJyanp1c1tpYqV1QsAbnAk2IrEZJTg6gtCAL6TVQA+fIe7IWLNimBQ2Du7VcurEIrKamf79-v8B-whEAgSHAoCgYJgQAgwMBLsgAFZYXCEdhbMC0BjMNibThcWZoBFQfAbDjgLjqfgIS4iVFgACMNMUVKgcmQJww2AJeEYrGR2LR8PZOFKqhqOhAYiGUGiUH45Mp1JpACZiozmaz8fguZjidwygAyZBFFUNFl4gWcjE8kkm8H-GCgCAhMp0fm4IUiiVS-i1YQAPx9Xp0BBwAAcUAByNmIo2yE2ay3cMPIYCJMWouAiETAWQgODWMg+cVgEPhw03VWmxFxrEkvUG6MmyMcqvangnG0QO3NR1h+wB4RB0PICPqvD1k7NlFcRPJ5CppQZrM5vMoXxFwfDs0T7E9sAiIoKgDMCoVJRlFJAVJ8cAZZeNfPVbtqw2l3oeDwA-AA9OEjrck3GNhqFrVtwsoXtS1iKIB5rciBPD3gKj6iuKz59m+6EYZ+74-puwEtgBv54ZOYGXmACA3kyxr6tBf7cEIzoPiUwpPpK7hoRhHGcUIWHui6TZEdiBG4bBLYkdSIRQYRImTsg+r1ghrpMe6qGvlxakft+tR8fg0Y4iUklmrpQA)\r\n\r\n## Debugging analyis using the above code for the psuedo-JQuery\r\n\r\nIn the declaration\r\n```\r\nt12: (string | JQuery\u003cHTMLElement>) & (string | JQuery\u003cHTMLElement> | undefined) = jQuery()\r\n```\r\nthe type\r\n```\r\n(string | JQuery\u003cHTMLElement>) & (string | JQuery\u003cHTMLElement> | undefined)\r\n```\r\nis reduced to union of these 4 types\r\n\r\n- `string`\r\n- `JQuery\u003cHTMLElement>`\r\n- `string & JQuery\u003cHTMLElement>`\r\n- `JQuery\u003cHTMLElement> & string`\r\n\r\n`inferTypes` tries to infer `TElement` in\r\n```\r\n\u003cTElement = HTMLElement>jQuery(): JQuery\u003cTElement>\r\n```\r\nby independently inferring for `TElement` from each of the 4 types above,\r\nto get the following candidates:\r\n\r\n- source: `string`, target:`JQuery\u003cTElement>`\r\n - candidate for `TElement`: (none)\r\n- source: `JQuery\u003cHTMLElement>`, target:`JQuery\u003cTElement>`\r\n - candidate for `TElement`: `HTMLElement`\r\n- source: `string & JQuery\u003cHTMLElement>`, target:`JQuery\u003cTElement>`\r\n - candidate for `TElement`: `HTMLElement` (repeat, ignored)\r\n- source: `JQuery\u003cHTMLElement> & string`, target:`JQuery\u003cTElement>``\r\n - candidate for `TElement`: `string`\r\n\r\nThen it takes the union `string | HTMLElement` so the final return type is `JQuery\u003cstring | HTMLElement>`.\r\n\r\n\r\nThe most noticeable problem is the result for:\r\n\r\n- source: `JQuery\u003cHTMLElement> & string`, target:`JQuery\u003cTElement>`\r\n - candidate for `TElement`: `string`\r\n\r\nThat happens because `inferTypes` calls `getApparentType(JQuery\u003cHTMLElement> & string)`\r\nwhich promotes `string` to `String`.\r\n\r\nThen `JQuery\u003cHTMLElement> & String` is object whose properties are compared to the properties of `JQuery\u003cTElemet>`.\r\n\r\n\r\nThey both share `[[Symbol.iterator]]` as a property the the properties\r\n\r\n- source: `(() => { next(): { done: true; value: any; } | { value: HTMLElement; }; }) & (() => IterableIterator\u003cstring>)`\r\n- target: `\"() => { next(): { done: true; value: any; } | { value: TElement; }; }\"`\r\n\r\nbecome a valid source-target pair for inference in the function\r\n```\r\nfunction inferFromSignatures(source: Type, target: Type, kind: SignatureKind) {\r\n const sourceSignatures = getSignaturesOfType(source, kind);\r\n const sourceLen = sourceSignatures.length;\r\n if (sourceLen > 0) {\r\n // We match source and target signatures from the bottom up, and if the source has fewer signatures\r\n // than the target, we infer from the first source signature to the excess target signatures.\r\n const targetSignatures = getSignaturesOfType(target, kind);\r\n const targetLen = targetSignatures.length;\r\n for (let i = 0; i \u003c targetLen; i++) {\r\n const sourceIndex = Math.max(sourceLen - targetLen + i, 0);\r\n inferFromSignature(getBaseSignature(sourceSignatures[sourceIndex]), getErasedSignature(targetSignatures[i]));\r\n }\r\n }\r\n}\r\n```\r\n- Here the source intersection is treated as an array of signatures.\r\n- Notice that the source signatures are of length 2, but the target signature is of length 1.\r\n- The code matches each of the target signatures to some source signature, but because there are more source signatures than target signature, the first source signature is ignored.\r\n\r\nEach match potentially contributes a candidates. In this case the deep match stack is as follows:\r\n\r\n-\r\n - `(...args: [] | [undefined]) => IteratorResult\u003cstring, any>`\r\n - `() => { done: true; value: any; } | { value: TElement; }`\r\n-\r\n - `IterableIterator\u003cstring>`\r\n - `{ next(): { done: true; value: any; } | { value: TElement; }; }`\r\n- \r\n - `IteratorYieldResult\u003cstring>`\r\n - `{ value: TElement; }`\r\n-\r\n - `string`\r\n - `TElement`\r\n\r\nand so `string` gets added as an inferred candidate for `TElement`.\r\n\r\nThere are a couple of remarkable things going on here.\r\n\r\n#### One remarkable thing\r\n\r\nUsing the the return type of the objects iterator for to infer the typeArgument for the object itself.\r\nBy coincide `String` and `JQuery` both have iterators, but the inference seems to be an extraordinary overreach.\r\n\r\n- Suggestion: *Resolve `string & \u003cSomeObject>` (`SomeObject` excepting `Enum`) to `never` in `getReducedType`. In the rare cases where `String & \u003cSomeObject>` is actually intended to represent their common properties, `String` can be explicitly specified instead of `string`*.\r\n - Test: Ran runtests to test this suggestion.\r\n - Result:\r\n - It does eliminate the bug noted in this post. \r\n - However there are 44 tests errors, many of which were cases of type abstractions such as \"tagged strings\" which have no relation to actual JS runtime types, and could be replaced with some other tagging method such as `WeakMap` or using a straightforward `interface TaggedString\u003cT> {string:string, tag:T}`. Overloading the `&` symbol, which already has a specific meaning in flow and inference, to represent other concepts is not a clean design, so TypeScript should not be obliged to support it.\r\n \r\n#### Another remarkable thing, that does not directly cause the main topic bug \r\n\r\nThere are a lot assumptions in `inferFromSignatures`, and because of that these two inferences give difference results;\r\n- source: `string & JQuery\u003cHTMLElement>`, target:`JQuery\u003cTElement>`\r\n - candidate for `TElement`: `HTMLElement` (repeat, ignored)\r\n- source: `JQuery\u003cHTMLElement> & string`, target:`JQuery\u003cTElement>`\r\n - candidate for `TElement`: `string`\r\n\r\nThe result should not depend upon the order around the `&` symbol. (However, changes to this \"remarkable thing\" would not prevent the bug which is the main topic of this post.) \r\n\r\n- Suggestion: *If the source and target don't share the same symbol and thus share the same overloads, then in if a full NxM comparison of signatures can not be made, it might be better to do nothing than risk unpredictable behavior. Instead, detect potential inferences from `tsserver`, and offer to fill in corresponding template constraints as an auto-completion. What I mean is not the final type (which is obviously may be undetermined), but the location in terms of object member path.* \r\n\r\n\r\n","author":{"url":"https://github.com/craigphicks","@type":"Person","name":"craigphicks"},"datePublished":"2023-12-07T03:24:10Z","url":"https://github.com/microsoft/TypeScript/issues/56702"}
| react-profiling | 0 |
| react-import-map | react,react-dom,react-dom/client,react-dom/profiling,react-is,react/compiler-runtime,react/jsx-dev-runtime,react/jsx-runtime,scheduler@b8488ee2c322 |
| route-pattern | /_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format) |
| route-controller | voltron_issues_fragments |
| route-action | issue_layout |
| fetch-nonce | v2:bb141a7c-e7ce-4c85-f589-2f8d045c03ff |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | CEA4:364B55:B0F279:E634D1:6B00E79F |
| html-safe-nonce | 75d312d188d947abdfd1322a557eaf7e008aff186dd08534eb7d34c4a27eaf10 |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJDRUE0OjM2NEI1NTpCMEYyNzk6RTYzNEQxOjZCMDBFNzlGIiwidmlzaXRvcl9pZCI6IjYyMzc3MTc4MjYyNTQyMDI3ODMiLCJyZWdpb25fZWRnZSI6ImlhZCIsInJlZ2lvbl9yZW5kZXIiOiJpYWQifQ== |
| visitor-hmac | 01eaed6511874d47bda37840f8ef4d0d44fb880d067a704457d98448976d7f88 |
| hovercard-subject-tag | issue:2029808183 |
| github-keyboard-shortcuts | repository,issues,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/microsoft/TypeScript/56702/issue_layout |
| twitter:image | https://opengraph.githubassets.com/7303eeb7d573c02f46cf6c5e0ce1709f0b52f1b742415d7185cd36ae8cd5fde8/microsoft/TypeScript/issues/56702 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/7303eeb7d573c02f46cf6c5e0ce1709f0b52f1b742415d7185cd36ae8cd5fde8/microsoft/TypeScript/issues/56702 |
| og:image:alt | 🔎 Search Terms type reduction fails generic function return type inference fails Couldn't find any issues that match this one sufficiently. 🕗 Version & Regression Information This is the behavior i... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | craigphicks |
| hostname | github.com |
| expected-hostname | github.com |
| None | 27088b6977484d0d3321d9a11c907c6d6637b315cfa359ef7952dbf6292f9b14 |
| turbo-cache-control | no-preview |
| go-import | github.com/microsoft/TypeScript git https://github.com/microsoft/TypeScript.git |
| octolytics-dimension-user_id | 6154722 |
| octolytics-dimension-user_login | microsoft |
| octolytics-dimension-repository_id | 20929025 |
| octolytics-dimension-repository_nwo | microsoft/TypeScript |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 20929025 |
| octolytics-dimension-repository_network_root_nwo | microsoft/TypeScript |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | 624179fb8b88d26ba5bba08894eb60a1c5a1d93d |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
| react-app-name | issues |
Links:
Viewport: width=device-width