René's URL Explorer Experiment


Title: A Proposal For Module Resolution · Issue #50152 · microsoft/TypeScript · GitHub

Open Graph Title: A Proposal For Module Resolution · Issue #50152 · microsoft/TypeScript

X Title: A Proposal For Module Resolution · Issue #50152 · microsoft/TypeScript

Description: Background When a user writes a module specifier (the string literal after from in an import declaration) in a TypeScript file, how should the compiler resolve that string to a file on disk to be included in type checking? Because TypeSc...

Open Graph Description: Background When a user writes a module specifier (the string literal after from in an import declaration) in a TypeScript file, how should the compiler resolve that string to a file on disk to be i...

X Description: Background When a user writes a module specifier (the string literal after from in an import declaration) in a TypeScript file, how should the compiler resolve that string to a file on disk to be i...

Opengraph URL: https://github.com/microsoft/TypeScript/issues/50152

X: @github

direct link

Domain: github.com


Hey, it has json ld scripts:
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"A Proposal For Module Resolution","articleBody":"## Background\r\nWhen a user writes a module specifier (the string literal after `from` in an import declaration) in a TypeScript file, how should the compiler resolve that string to a file on disk to be included in type checking? Because TypeScript never rewrites module specifiers in its JavaScript emit, the only possible answer is that it should mirror whatever resolution behavior the code’s intended *runtime module resolver* has. I’m using “runtime module resolver” to mean the system whose module resolution behavior has observable effects at runtime: it may be a component of the runtime itself, as in Node, or it may be a bundler that consumes the module specifiers to produce one or more script files. (The “runtime” distinction is made to exclude analysis tools like linters, which may perform module resolution without having any impact on runtime behavior.) TypeScript’s way of handling this has been to say that the user must indicate what their code’s runtime module resolver is via the `moduleResolution` compiler option so the compiler can mirror it.\r\n\r\nAs little as five years ago, there were only two places JavaScript could run that were worth mentioning: in Node as CommonJS modules, and in the browser as scripts. For the former, TypeScript had `--moduleResolution node`. (The latter needed no `moduleResolution` mode, though you can argue some sort of `none` value would have been appropriate.) However, bundlers like Webpack were widely used and were themselves module resolvers, perhaps deserving their own `moduleResolution` setting according to TypeScript’s philosophy. But demand for bundler-specific module resolution was essentially nonexistent, because bundlers mostly just copied Node’s module resolution algorithm, so users were able to get by with `--moduleResolution node`.\r\n\r\n_(Note: as of this writing, `--moduleResolution node16` and `--moduleResolution nodenext` are identical in TypeScript. The latter is intended to be updated as Node changes. For brevity, I use `node16` in this writing, but both are equally applicable everywhere.)_\r\n\r\nOver the next few years, though, the landscape changed. Browsers adopted ESM as a natively supported format, and Node added ESM support alongside CJS, with a complex interop system and new features like package.json `exports`. A new wave of bundlers and runtimes emerged, and many adopted *some* of the features that Node introduced. But this time, none was similar enough to Node to piggyback on TypeScript’s `--moduleResolution node16` option without users noticing problems.\r\n\r\n## Today\r\nIn this new landscape, users have been trying both `node` and `node16` with bundlers and browsers and hitting walls, which I will explore in some detail. In brief, the JavaScript ecosystem is in a phase where we cannot hope to provide a dedicated `moduleResolution` mode for every runtime and bundler. At the same time, we have resisted allowing resolver plugins for many reasons:\r\n\r\n- security and performance concerns\r\n- implementing correct module specifier generation for a given resolution mode for declaration emit, auto-imports, and path completions is [extremely](https://github.com/microsoft/TypeScript/blob/main/src/compiler/moduleSpecifiers.ts) [non-trivial](https://github.com/microsoft/TypeScript/blob/main/src/services/stringCompletions.ts)\r\n- concerns about reliability under file-watching modes (a resolution must return not just what it found, but where it looked and found nothing, and where it looked up auxiliary information used in resolution such as package.json files)\r\n- we would like to avoid allowing bespoke per-project resolution simply to reduce chaos\r\n\r\nThis philosophy has brought TypeScript to a point where we have avoided some significant pitfalls, but have essentially no support for module resolvers that are not Node. To make the issues explicit, let’s examine some hypothetical case studies.\r\n\r\n### Bundling with Webpack, esbuild, or Vite\r\nThese bundlers use a Node-CJS-like resolution algorithm and support package.json `exports`. If the user chooses `--moduleResolution node`, any of their dependencies that modify their export structure via package.json `exports` will be misrepresented by TypeScript—imports from that package may not resolve, they may resolve to incorrect files, and they will receive incorrect auto-imports and path completions. If the user chooses `--moduleResolution node16`, TypeScript will resolve their imports against dependencies’ package.json `exports`, but the conditions it uses in the lookup may be wrong: bundlers always set the `import` condition for imports and the `require` definition for require calls, but TypeScript believes that import declarations in files that have not been explicitly scoped as ESM will be transpiled into `require` calls, so it looks up these imports with the `require` condition, which could lead to incorrect resolutions. Moreover, in these files, TypeScript will prohibit imports (because it think they are actually `require`s) of ESM-format files. The bundler has no such restriction, as its CJS/ESM divide is purely syntactic. (This is a slight oversimplification and the three bundlers mentioned behave slightly differently, but the simplification is good enough for describing the user experience.) If the user tries to get around this by scoping all of their files as ESM by setting `\"type\": \"module\"` in their own package.json, TypeScript will impose Node’s much stricter ESM resolution algorithm on those files, disabling index-file resolution and extensionless lookups—in fact, the extension the user has to write is `.js`, which will be nonsensical for the context, where the runtime module resolver (the bundler) only ever sees `.ts` files. (Vite and esbuild tolerate this extension mismatch out of the box; Webpack has historically required a plugin but just added a config setting for it.) This configuration satisfies both the bundler and TypeScript, but at a high DX cost for the user—TypeScript imposes rules on resolution that are wholly unnecessary for the bundler.\r\n\r\n### Running in Bun\r\nThe situation is exactly the same as the above, since Bun’s module resolver is a port of esbuild’s, and it consumes TS files directly.\r\n\r\n### Bundling with Parcel or Browserify\r\nThese bundlers do not (yet) support package.json `exports`, so `--moduleResolution node` is still a reasonably good fit.\r\n\r\n### Writing ESM for the browser\r\nEvery module resolution mode except `classic` performs node_modules resolution, which does not happen in the browser. `classic` performs index-file and extensionless lookups, which does not happen in the browser. The closest the user can get is probably to use `node16` such that index-file and extensionless lookups are disabled, but they have to take care to avoid node_modules lookups and importing CommonJS dependencies.\r\n\r\n### Writing ESM for Node, browser, or Deno\r\nWe have heard a few arguments recently about the ability to write code targeting multiple runtimes, mostly in the form of “if you let me write my imports with `.ts` extensions and emit them as `.js` extensions, my input files will work in Deno and my output files will work in Node” which is not generally true. However, it is true that Node, the browser, and Deno have a small amount of overlap in resolution behavior such that it is possible to write ES modules in JS and publish them both to npm and to a CDN where they can be consumed by browsers or Deno. A user trying to do this today faces the same situation as the case above, since the overlap between these systems is just relative URL imports including extensions: there is no mode restrictive enough to avoid writing imports that will work in Node but not in Deno or the browser. (Note that targeting a single bundler which produces a separate output for each target runtime is, for now, a better approach for multi-platform JS authoring.)\r\n\r\n## Proposal\r\nExisting module resolution modes (with the exception of `classic`, whose existence is still a mystery to me) have intended to target one specific runtime and have been named for that runtime—`node` (v11 and before), `node16`, and `nodenext`—and the resolution features they entail are non-configurable implementation details. To move forward, I suggest a strategy of composition: expose some lower-level modes that can be combined with additional options to build up modes that are suitable for a variety of runtime resolvers. If the ecosystem converges on combinations of these settings, we can encapsulate them in a named mode. To start this process, I propose the following reorganization and expansion of options (all names subject to bikeshedding):\r\n\r\n### Module Resolution Modes\r\n1. Expose what is now called `node` as a low-level mode called `conventional`, with a slight modification necessary to support `.ts` extension resolution under `noEmit`, and defaulting `esModuleInterop` to true. (The name, which I am more than happy to change, is a reference to the fact that most runtimes and bundlers have copied node_modules resolution, extensionless lookups, and special index-file handling from Node to the point where users no longer think of these features as specific to Node. Since we now have `node16` which is highly Node-specific, the goal is to create a situation where the only people who should choose a `moduleResolution` option named after Node are people who are actually using Node.)\r\n2. Implement today’s `node` as a composition of `conventional` and an internal-only option that undoes the modifications mentioned in (1) to preserve backward compatibility. Also, deprecate the name `node` in favor of `node-legacy` to encourage users of modern Node to consider migrating to `node16`, and to encourage users of other runtimes and bundlers to consider migrating to `conventional`. Today’s `node` is only accurate to Node v11 and earlier, so we need to start guiding people away from it at some point.\r\n3. Implement a new low-level mode called `minimal` which resolves only relative module specifiers including file extensions, and attempts to parse all files as ESM. This can be used as a base for browser module resolution.\r\n4. Leave `classic`, `node16`, and `nodenext` as they are.\r\n\r\n### Module Resolution Options\r\n1. Add an option to enable/disable package.json `exports` in `conventional` and add conditions to the resolver. (May also apply to other modes that do node_modules resolution, i.e. everything but `classic` and `minimal`.) \r\n\r\nThat’s it for now—in the future, import maps, HTTP imports, and other features adopted by more than one runtime resolver should be exposed as options. When/if we have support for import maps and HTTP imports specifically, we should consider creating a mode named `browser` that is a composition of `minimal` and those options defaulted to true.\r\n\r\n### Resolution of relative module specifiers ending in `.ts`\r\nBoth `minimal` and `conventional` (but not `node-legacy`) will support resolution to `.ts` files by specifying a `.ts` extension in the module specifier. This will be an error, as it is today, unless `noEmit` is enabled. This allows users who are bundling or directly running their TypeScript source to write relative module specifiers with the extension that their runtime module resolver will actually see, which has always been the underlying goal of telling users to write `.js` extensions when their runtime resolver will operate on the _emitted JS_ code. Additionally, in these modes, I suggest that it be legal to write an `import type` of a module specifier ending in `.d.ts`.\r\n\r\nThis cannot be supported in today’s `node` or `node16` in a fully backward-compatible way. In these modes, an import of `\"./foo.ts\"` will resolve to `foo.ts.js` or `foo.ts.d.ts` in the same directory even if `foo.ts` is also present; unsupported extensions are not probed for existence before moving on to fallbacks. This amounts to a bug in `node` and `node16`. I have proposed to leave the bug in place for `node-legacy` to preserve backward compatibility, but it may be reasonable to try fixing it everywhere and listen for feedback.\r\n\r\nIt should be noted that `composite` projects may not disable emit if they are referenced by another project. It may be possible to relax the `noEmit` restriction to `emitDeclarationOnly`. The primary challenge here is a portability concern: older `moduleResolution` modes will not be able to resolve the `.ts`-suffixed specifiers in those declaration files. I think it’s worth fixing `node16` to support this; they would receive the bug fix described above so that they can always resolve `.ts`-suffixed specifiers, but would continue to issue a checker error. That way, we can safely silence the error in declaration files for better portability, and projects that need to use `.ts`-suffixed imports could be `composite` project references. Fixing `node16` in this way would also prepare us for the possibility of Node running directly on TS files, transpiling in-memory like ts-node, an idea that has been gaining traction with Node maintainers recently. \r\n\r\nHowever, I think much of the demand we’ve heard so far for being able to use `.ts`-suffixed module specifiers has been misplaced. Users who tried to use `node16` with a bundler may have been prompted to add a `.js` extension to a module specifier and thought that adding a `.ts` extension makes more sense, when in actuality they can continue to use extensionless imports in a mode like `conventional`. Others demand `.ts`-suffixed imports in combination with module specifier rewriting because they believe that will let them write input code that will run natively in Deno, while tsc’s output will run natively in Node. This is out of scope; the way to write once and ship to multiple environments is to target a bundler and produce multiple bundles. Consequently, I think there are very few users who *need* to write `.ts`-suffixed imports (especially in a world with `conventional`), but they are unobjectionable in `noEmit` and easy to implement.  The feature is not core to this proposal, but I believe it would be a mistake to create new module resolution modes without at least fixing the aforementioned bug to carve out the possibility of `.ts`-suffixed imports resolving in the future.\r\n\r\n### Notes on `conventional`\r\nThis proposal does not allow for a perfect mapping of TypeScript’s resolution behavior onto every bundler, but I think it covers most cases, or what I will call *all reasonable cases*. If we wanted to be a bit prescriptive, I would be tempted to prohibit `.cts` and `.cjs` files, disallow `import m = require(...)` syntax in TypeScript files, and disable resolution of `require` calls in JS files. Some of the newer bundlers are explicitly ESM-only, ignoring or prohibiting `require` calls in user code and converting library dependencies from CJS to ESM. No bundler I tested had separate CJS and ESM resolution algorithms, with the exception of setting `import` vs. `require` in the resolver conditions when looking up package.json `exports`. There seems to be little reason to allow explicitly CJS constructs in implementation files in this mode (while CJS constructs in dependency declaration files obviously need to be consumable). As in TS files today, users will still be free to write `require` calls, but they will not have special resolution behavior.\r\n\r\n## Unanswered questions\r\n- This proposal exposes users to increased complexity. I don’t see a way around that. I have also proposed deprecating `--moduleResolution node`, which is the default for `--module commonjs`. Consequently, many users are using `node` without realizing it. This raises the question of what defaults we should have in the future, what `module` settings should be allowed with these `moduleResolution` modes, and more broadly, how to guide users into selecting the correct settings for their project.\r\n\t- A possible mitigation is to allow multiple tsconfig.json `extends` and encourage bundlers to publish (or publish ourselves under `@typescript`) tsconfig bases that reflect the resolution behaviors supported by these bundlers out-of-the-box. That way, an esbuild user could write\r\n\t  ```jsonc\r\n\t  {\r\n            \"extends\": [\"webpack\", \"./tsconfig.base.json\"],\r\n            \"compilerOptions\": { /* ... */ }\r\n          }\r\n\t  ```\r\n* Should `.ts`-suffixed resolution be automatically allowed based on `noEmit`, or should it be gated behind another flag, or should the capability be preserved for the future but not enabled yet? It makes sense to me that `noEmit` should enable it, because if you’re writing modules but not emitting, it stands to reason that another tool is going to consume the TS modules that you wrote. @DanielRosenwasser raised the idea that this may cannibalize project references usage, which requires declarations to be emitted and can help speed up type checking when splitting large codebases. More thought needs to be put into how `.ts` imports would work with declaration emit.\r\n* For simplicity and consistency, can we fix the resolution bug where files with unsupported extensions do not stop other lower priority extensions from being looked up even in today’s `node`, breaking backward compatibility? The first time I considered this, I thought this would be an untenable breaking change, because people rely on this behavior to write declarations for files with unsupported extensions, e.g. `import styles from \"./styles.css\"` would resolve to `styles.css.d.ts` because it thinks that’s analogous to `styles.css.js`, not `styles.css`. However, @weswigham has proposed a general solution for this at https://github.com/microsoft/TypeScript/issues/50133. Taking some form of that proposal may be key to fixing this “bug” in _any_ resolution mode without effectively losing a feature.\r\n\r\nRelated: #37582, #49083, #46452, #46334, and probably a dozen others","author":{"url":"https://github.com/andrewbranch","@type":"Person","name":"andrewbranch"},"datePublished":"2022-08-02T23:19:12Z","url":"https://github.com/microsoft/TypeScript/issues/50152"}

react-profiling0
react-import-mapreact,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-controllervoltron_issues_fragments
route-actionissue_layout
fetch-noncev2:b1cd5b2d-7faf-96db-f5b8-252448aa476d
current-catalog-service-hash81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114
request-idEA46:24ACB9:B95FA8:F5F72F:6B00ED16
html-safe-noncefeb3c5e2af588a8be236cff3da7695192d11958b8e2a6e13a3c817a031d1c0df
visitor-payloadeyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJFQTQ2OjI0QUNCOTpCOTVGQTg6RjVGNzJGOjZCMDBFRDE2IiwidmlzaXRvcl9pZCI6IjUyMDUyNDYzNTE1OTE0MDI3NzQiLCJyZWdpb25fZWRnZSI6ImlhZCIsInJlZ2lvbl9yZW5kZXIiOiJpYWQifQ==
visitor-hmaceaab39a8cdcbacc12c39e5450155d3f611df7d7c08a615c9a821c5dfc76d41f4
hovercard-subject-tagissue:1326498173
github-keyboard-shortcutsrepository,issues,copilot
google-site-verificationApib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I
octolytics-urlhttps://collector.github.com/github/collect
analytics-location///voltron/issues_fragments/issue_layout
fb:app_id1401488693436528
apple-itunes-appapp-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/microsoft/TypeScript/50152/issue_layout
twitter:imagehttps://opengraph.githubassets.com/c10a54ef1590fd74e898c02623fe84608b9415c1084aadf3dec264dfec80d2f1/microsoft/TypeScript/issues/50152
twitter:cardsummary_large_image
og:imagehttps://opengraph.githubassets.com/c10a54ef1590fd74e898c02623fe84608b9415c1084aadf3dec264dfec80d2f1/microsoft/TypeScript/issues/50152
og:image:altBackground When a user writes a module specifier (the string literal after from in an import declaration) in a TypeScript file, how should the compiler resolve that string to a file on disk to be i...
og:image:width1200
og:image:height600
og:site_nameGitHub
og:typeobject
og:author:usernameandrewbranch
hostnamegithub.com
expected-hostnamegithub.com
None4ef498cbabcbe3c50befc7a5b743e7072ee770b4daf0e15e54801180d1fa91fc
turbo-cache-controlno-preview
go-importgithub.com/microsoft/TypeScript git https://github.com/microsoft/TypeScript.git
octolytics-dimension-user_id6154722
octolytics-dimension-user_loginmicrosoft
octolytics-dimension-repository_id20929025
octolytics-dimension-repository_nwomicrosoft/TypeScript
octolytics-dimension-repository_publictrue
octolytics-dimension-repository_is_forkfalse
octolytics-dimension-repository_network_root_id20929025
octolytics-dimension-repository_network_root_nwomicrosoft/TypeScript
turbo-body-classeslogged-out env-production page-responsive
disable-turbofalse
browser-stats-urlhttps://api.github.com/_private/browser/stats
browser-errors-urlhttps://api.github.com/_private/browser/errors
release9983dd5da06943f833c971dd5b6bc988e2858be5
ui-targetfull
theme-color#1e2327
color-schemelight dark
react-app-nameissues

Links:

Skip to contenthttps://github.com/microsoft/TypeScript/issues/50152#start-of-content
https://github.com/
Sign inhttps://github.com/login?return_to=https%3A%2F%2Fgithub.com%2Fmicrosoft%2FTypeScript%2Fissues%2F50152
GitHubRepository hosting, code review, and collaborationhttps://github.com/platform
CopilotAI coding agent for tasks, projects, and automated workhttps://github.com/features/copilot
ActionsCI/CD and automationhttps://github.com/features/actions
Code QualityQuality analysis, fixes, and enforcementhttps://github.com/features/code-quality
CodespacesCloud development environmentshttps://github.com/features/codespaces
Code SecurityVulnerability detection and remediationhttps://github.com/security/advanced-security/code-security
Secret ProtectionSecret scanning and leak preventionhttps://github.com/security/advanced-security/secret-protection
All Featureshttps://github.com/features
Documentationhttps://docs.github.com/en
Traininghttps://learn.github.com/skills
Certificationshttps://learn.github.com/credentials
Build with Copilothttps://github.com/features/ai
Customize Copilothttps://docs.github.com/en/copilot/how-tos/copilot-on-github/customize-copilot/customize-copilot-overview
Integrationshttps://github.com/marketplace
Trending reposhttps://github.com/trending
GitHub Sponsorshttps://github.com/open-source/sponsors
Developer articleshttps://github.com/resources/articles
ChangelogYour source for the latest features, improvements, and fixes across GitHub products, all in one place.https://github.blog/changelog/
Enterpriseshttps://github.com/enterprise
Teamhttps://github.com/team
Startupshttps://github.com/enterprise/startups
Nonprofitshttps://github.com/solutions/industry/nonprofits
Healthcarehttps://github.com/solutions/industry/healthcare
Financial serviceshttps://github.com/solutions/industry/financial-services
Manufacturinghttps://github.com/solutions/industry/manufacturing
Governmenthttps://github.com/solutions/industry/government
See all industrieshttps://github.com/solutions/industry
Why GitHubhttps://github.com/why-github
Customer Storieshttps://github.com/customer-stories
Business insightshttps://github.com/solutions/executive-insights
Trust Centerhttps://github.com/trust-center
GitHub Advanced SecurityEnterprise-grade code securityhttps://github.com/security/advanced-security
Copilot for businessEnterprise-grade AI featureshttps://github.com/features/copilot/copilot-business
Premium SupportEnterprise-grade 24/7 supporthttps://github.com/enterprise/premium-support
Documentationhttps://docs.github.com/en
Resource centerhttps://github.com/resources
Bloghttps://github.blog/
Events & webinarshttps://github.com/resources/events
Community Forumhttps://github.com/orgs/community/discussions
Customer Storieshttps://github.com/customer-stories
Integrationshttps://github.com/marketplace
Customer supporthttps://help.github.com/
Traininghttps://learn.github.com/skills
GitHub Statushttps://www.githubstatus.com/
Abouthttps://github.com/about
Partnershttps://github.com/partners
Changeloghttps://github.blog/changelog/
GitHub UniverseThe event for developers, by developers — talks, workshops, and what’s next for GitHub.https://githubuniverse.com/
Pricinghttps://github.com/pricing
Sign inhttps://github.com/login?return_to=https%3A%2F%2Fgithub.com%2Fmicrosoft%2FTypeScript%2Fissues%2F50152
Sign uphttps://github.com/signup?ref_cta=Sign+up&ref_loc=header+logged+out&ref_page=%2F%3Cuser-name%3E%2F%3Crepo-name%3E%2Fvoltron%2Fissues_fragments%2Fissue_layout&source=header-repo&source_repo=microsoft%2FTypeScript
Reloadhttps://github.com/microsoft/TypeScript/issues/50152
Reloadhttps://github.com/microsoft/TypeScript/issues/50152
Reloadhttps://github.com/microsoft/TypeScript/issues/50152
microsofthttps://github.com/microsoft
TypeScripthttps://github.com/microsoft/TypeScript
Codehttps://github.com/microsoft/TypeScript
Issues5k (5k)https://github.com/microsoft/TypeScript/issues
Pull requests308 (308)https://github.com/microsoft/TypeScript/pulls
Actionshttps://github.com/microsoft/TypeScript/actions
Projectshttps://github.com/microsoft/TypeScript/projects
Wikihttps://github.com/microsoft/TypeScript/wiki
Security and qualityhttps://github.com/microsoft/TypeScript/security
Insightshttps://github.com/microsoft/TypeScript/insights
https://github.com/microsoft/TypeScript
New issuehttps://github.com/login?return_to=https://github.com/microsoft/TypeScript/issues/50152
New issuehttps://github.com/login?return_to=https://github.com/microsoft/TypeScript/issues/50152
A Proposal For Module Resolutionhttps://github.com/microsoft/TypeScript/issues/50152#top
https://github.com/andrewbranch
In DiscussionNot yet reached consensushttps://github.com/microsoft/TypeScript/issues?q=state%3Aopen%20label%3A%22In%20Discussion%22
SuggestionAn idea for TypeScripthttps://github.com/microsoft/TypeScript/issues?q=state%3Aopen%20label%3A%22Suggestion%22
TypeScript 5.1.0https://github.com/microsoft/TypeScript/milestone/178
https://github.com/andrewbranch
Andrew Branch (andrewbranch)https://github.com/andrewbranch
on Aug 2, 2022https://github.com/microsoft/TypeScript/issues/50152#issue-1326498173
extremelyhttps://github.com/microsoft/TypeScript/blob/main/src/compiler/moduleSpecifiers.ts
non-trivialhttps://github.com/microsoft/TypeScript/blob/main/src/services/stringCompletions.ts
Daniel Rosenwasser (@DanielRosenwasser)https://github.com/DanielRosenwasser
Wesley Wigham (@weswigham)https://github.com/weswigham
Proposal: Enable declaration files for non-js-extensioned files #50133https://github.com/microsoft/TypeScript/issues/50133
#37582https://github.com/microsoft/TypeScript/issues/37582
#49083https://github.com/microsoft/TypeScript/issues/49083
#46452https://github.com/microsoft/TypeScript/issues/46452
#46334https://github.com/microsoft/TypeScript/issues/46334
Nexthttps://github.com/microsoft/TypeScript/issues/50152?timeline_page=1
Andrew Branch (andrewbranch)https://github.com/andrewbranch
DiscussionIssues which may not have code impacthttps://github.com/microsoft/TypeScript/issues?q=state%3Aopen%20label%3A%22Discussion%22
SuggestionAn idea for TypeScripthttps://github.com/microsoft/TypeScript/issues?q=state%3Aopen%20label%3A%22Suggestion%22
In DiscussionNot yet reached consensushttps://github.com/microsoft/TypeScript/issues?q=state%3Aopen%20label%3A%22In%20Discussion%22
DiscussionIssues which may not have code impacthttps://github.com/microsoft/TypeScript/issues?q=state%3Aopen%20label%3A%22Discussion%22
on Aug 2, 2022https://github.com/microsoft/TypeScript/issues/50152#event-7114207347
https://github.com/weswigham
Wesley Wigham (weswigham)https://github.com/weswigham
on Aug 2, 2022https://github.com/microsoft/TypeScript/issues/50152#issuecomment-1203327678
https://github.com/weswigham
Wesley Wigham (weswigham)https://github.com/weswigham
on Aug 2, 2022https://github.com/microsoft/TypeScript/issues/50152#issuecomment-1203329401
https://github.com/weswigham
Wesley Wigham (weswigham)https://github.com/weswigham
on Aug 3, 2022https://github.com/microsoft/TypeScript/issues/50152#issuecomment-1203332769
#29353https://github.com/microsoft/TypeScript/pull/29353
https://github.com/andrewbranch
Andrew Branch (andrewbranch)https://github.com/andrewbranch
on Aug 3, 2022https://github.com/microsoft/TypeScript/issues/50152#issuecomment-1203339651
https://github.com/jakebailey
Jake Bailey (jakebailey)https://github.com/jakebailey
on Aug 3, 2022https://github.com/microsoft/TypeScript/issues/50152#issuecomment-1203339662
https://esbuild.github.io/api/#conditionshttps://esbuild.github.io/api/#conditions
https://esbuild.github.io/api/#main-fieldshttps://esbuild.github.io/api/#main-fields
evanw/esbuild#2417https://github.com/evanw/esbuild/issues/2417
https://github.com/DanielRosenwasser
Daniel Rosenwasser (DanielRosenwasser)https://github.com/DanielRosenwasser
on Aug 3, 2022https://github.com/microsoft/TypeScript/issues/50152#issuecomment-1203340054
ts-nodehttps://www.npmjs.com/package/ts-node
tsxhttps://www.npmjs.com/package/tsx
https://github.com/jakebailey
Jake Bailey (jakebailey)https://github.com/jakebailey
on Aug 3, 2022https://github.com/microsoft/TypeScript/issues/50152#issuecomment-1203342007
https://github.com/weswigham
Wesley Wigham (weswigham)https://github.com/weswigham
on Aug 3, 2022https://github.com/microsoft/TypeScript/issues/50152#issuecomment-1203342133
https://github.com/weswigham
Wesley Wigham (weswigham)https://github.com/weswigham
on Aug 3, 2022https://github.com/microsoft/TypeScript/issues/50152#issuecomment-1203344619
#50133https://github.com/microsoft/TypeScript/issues/50133
https://github.com/andrewbranch
Andrew Branch (andrewbranch)https://github.com/andrewbranch
on Aug 3, 2022https://github.com/microsoft/TypeScript/issues/50152#issuecomment-1203346018
Jake Bailey (@jakebailey)https://github.com/jakebailey
Daniel Rosenwasser (@DanielRosenwasser)https://github.com/DanielRosenwasser
https://github.com/jakebailey
Jake Bailey (jakebailey)https://github.com/jakebailey
on Aug 3, 2022https://github.com/microsoft/TypeScript/issues/50152#issuecomment-1203347036
https://github.com/frank-dspeed
Frank Lemanschik (frank-dspeed)https://github.com/frank-dspeed
on Nov 1, 2022https://github.com/microsoft/TypeScript/issues/50152#issuecomment-1298321347
Jarred Sumner (@Jarred-Sumner)https://github.com/Jarred-Sumner
https://github.com/robpalme
Rob Palmer (robpalme)https://github.com/robpalme
on Nov 1, 2022https://github.com/microsoft/TypeScript/issues/50152#issuecomment-1298442470
herehttps://www.bloomberg.com/company/stories/10-insights-adopting-typescript-at-scale/
https://github.com/frank-dspeed
Frank Lemanschik (frank-dspeed)https://github.com/frank-dspeed
on Nov 1, 2022https://github.com/microsoft/TypeScript/issues/50152#issuecomment-1298626261
Rob Palmer (@robpalme)https://github.com/robpalme
https://github.com/tc39/proposal-type-annotationshttps://github.com/tc39/proposal-type-annotations
https://github.com/Jarred-Sumner
Jarred Sumner (Jarred-Sumner)https://github.com/Jarred-Sumner
on Nov 1, 2022https://github.com/microsoft/TypeScript/issues/50152#issuecomment-1299233311
Rob Palmer (@robpalme)https://github.com/robpalme
https://github.com/hlovdal
hlovdalhttps://github.com/hlovdal
on Nov 8, 2022https://github.com/microsoft/TypeScript/issues/50152#issuecomment-1307871048
Rob Palmer (@robpalme)https://github.com/robpalme
How to design a good API and why it mattershttps://www.youtube.com/watch?v=aAb7hSCtvGw
slideshttps://static.googleusercontent.com/media/research.google.com/en//pubs/archive/32713.pdf
https://github.com/frank-dspeed
Frank Lemanschik (frank-dspeed)https://github.com/frank-dspeed
on Nov 9, 2022https://github.com/microsoft/TypeScript/issues/50152#issuecomment-1308209948
https://github.com/lemanschik
Frank Lemanschik (lemanschik)https://github.com/lemanschik
on Nov 29, 2022https://github.com/microsoft/TypeScript/issues/50152#issuecomment-1330340051
https://github.com/lemanschik
Frank Lemanschik (lemanschik)https://github.com/lemanschik
on Dec 11, 2022https://github.com/microsoft/TypeScript/issues/50152#issuecomment-1345533572
https://github.com/andrewbranch
Andrew Branch (andrewbranch)https://github.com/andrewbranch
on Dec 13, 2022https://github.com/microsoft/TypeScript/issues/50152#issuecomment-1349268988
--moduleResolution bundler (formerly known as hybrid) #51669https://github.com/microsoft/TypeScript/pull/51669
What should the new moduleResolution setting be called? #51714https://github.com/microsoft/TypeScript/issues/51714
Can’t resolve @types when vendoring dependencies for browser ESM imports #50600https://github.com/microsoft/TypeScript/issues/50600
What’s confusing about modules? #51876https://github.com/microsoft/TypeScript/issues/51876
Andrew Branch (andrewbranch)https://github.com/andrewbranch
TypeScript 5.0.0https://github.com/microsoft/TypeScript/milestone/175
TypeScript 5.1.0https://github.com/microsoft/TypeScript/milestone/178
on Apr 6, 2023https://github.com/microsoft/TypeScript/issues/50152#event-8948648075
https://github.com/IanVS
Ian VanSchooten (IanVS)https://github.com/IanVS
on Aug 22, 2023https://github.com/microsoft/TypeScript/issues/50152#issuecomment-1688352457
https://github.com/andrewbranch
Andrew Branch (andrewbranch)https://github.com/andrewbranch
on Aug 22, 2023https://github.com/microsoft/TypeScript/issues/50152#issuecomment-1688443961
#50600https://github.com/microsoft/TypeScript/issues/50600
Andrew Branch (andrewbranch)https://github.com/andrewbranch
completedhttps://github.com/microsoft/TypeScript/issues?q=is%3Aissue%20state%3Aclosed%20archived%3Afalse%20reason%3Acompleted
on Aug 22, 2023https://github.com/microsoft/TypeScript/issues/50152#event-10160171194
https://github.com/MicahZoltu
Micah Zoltu (MicahZoltu)https://github.com/MicahZoltu
on Aug 22, 2023https://github.com/microsoft/TypeScript/issues/50152#issuecomment-1688491433
https://github.com/Zoltu/preact-es2015-templatehttps://github.com/Zoltu/preact-es2015-template
Sign up for freehttps://github.com/signup?return_to=https://github.com/microsoft/TypeScript/issues/50152
Sign in to commenthttps://github.com/login?return_to=https://github.com/microsoft/TypeScript/issues/50152
Andrew Branch (andrewbranch)https://github.com/andrewbranch
In DiscussionNot yet reached consensushttps://github.com/microsoft/TypeScript/issues?q=state%3Aopen%20label%3A%22In%20Discussion%22
SuggestionAn idea for TypeScripthttps://github.com/microsoft/TypeScript/issues?q=state%3Aopen%20label%3A%22Suggestion%22
TypeScript 5.1.0https://github.com/microsoft/TypeScript/milestone/178
https://github.com
Termshttps://docs.github.com/site-policy/github-terms/github-terms-of-service
Privacyhttps://docs.github.com/site-policy/privacy-policies/github-privacy-statement
Securityhttps://github.com/security
Statushttps://www.githubstatus.com/
Communityhttps://github.community/
Docshttps://docs.github.com/
Contacthttps://support.github.com?tags=dotcom-footer

Viewport: width=device-width


URLs of crawlers that visited me.