René's URL Explorer Experiment


Title: Establish a package.json convention for Typescript source in monorepos and npm packages · Issue #51750 · microsoft/TypeScript · GitHub

Open Graph Title: Establish a package.json convention for Typescript source in monorepos and npm packages · Issue #51750 · microsoft/TypeScript

X Title: Establish a package.json convention for Typescript source in monorepos and npm packages · Issue #51750 · microsoft/TypeScript

Description: Suggestion Establish a convention for a field in package.json that will to point to Typescript source code, respected as an override by tsc, for IDE and downstream build tooling. 🔍 Search Terms List of keywords you searched for before cr...

Open Graph Description: Suggestion Establish a convention for a field in package.json that will to point to Typescript source code, respected as an override by tsc, for IDE and downstream build tooling. 🔍 Search Terms Lis...

X Description: Suggestion Establish a convention for a field in package.json that will to point to Typescript source code, respected as an override by tsc, for IDE and downstream build tooling. 🔍 Search Terms Lis...

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

X: @github

direct link

Domain: github.com


Hey, it has json ld scripts:
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Establish a package.json convention for Typescript source in monorepos and npm packages","articleBody":"# Suggestion\r\n\r\nEstablish a convention for a field in package.json that will to point to Typescript source code, respected as an override by tsc, for IDE and downstream build tooling.\r\n\r\n## 🔍 Search Terms\r\n\r\nList of keywords you searched for before creating this issue. Write them down here so that others can find this suggestion more easily and help provide feedback.\r\n\r\nexports typescript index.ts main source package.json\r\n\r\n## ✅ Viability Checklist\r\n\r\nMy suggestion meets these guidelines:\r\n\r\n* [X] This wouldn't be a breaking change in existing TypeScript/JavaScript code\r\n* [X] This wouldn't change the runtime behavior of existing JavaScript code\r\n* [X] This could be implemented without emitting different JS based on the types of the expressions\r\n* [X] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)\r\n* [X] This feature would agree with the rest of [TypeScript's Design Goals](https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals).\r\n\r\n\r\n## ⭐ Suggestion\r\n\r\nThe tsc tool, through implementing and documenting a specific source import behaviour from package.json fields, could ensure that monorepo authors importing local packages and third-party bundlers importing upstream packages can resolve directly to Typescript source, while allowing package.json metadata to support publishing into the javascript ecosystem through \"main\", \"module\", \"exports\" independently (since they would always use distinct fields from the fields pointing to Typescript source).\r\n \r\nProposals for this new field could be...\r\n\r\n* Introduce a convention for a field in `exports[*][\"import\"]` and `exports[*][\"require\"]` alongside `\"node\"`, `\"browser\"`, `\"default\"` e.g. a `\"typescript\"` or `\"source\"` field.\r\n* Introduce a convention for a field in `exports[*]` alongside `\"import\"` and `\"require\"` - e.g. an `\"import:tsc\"` or `\"compile\"` field.\r\n* Document and support that the top-level `\"types\"` field can be `.ts` and not just `.d.ts`, meaning it can serve both declarations and source\r\n* Document and support that the top-level `\"source\"` field can point to `.ts` and that tsc see will see it as an override of `\"main\"`, `\"module\"`, entries in `\"exports\"` \r\n\r\n## 📃 Motivating Example\r\n\r\nIn a monorepo, using a \"main\" field that resolves directly to a `.ts` path already allows direct resolution of source code. However, this interferes with the primary use case of the \"main\" field - to resolve Javascript. This then demands fragile prepublish and postpublish steps if \"./src/index.ts\" is to be rewritten to \"./dist/index.js\" and back again to fulfil the needs of a publish script. This suggests a distinct field needs to live alongside the Javascript resolution fields, allowing all elements to coexist and be individually addressable within the structure of a package.\r\n\r\n## 💻 Use Cases\r\n\r\n* Within a monorepo having multiple workspaces, they can have \"main\" or \"exports\" fields which point directly to Typescript files, allowing easy hot-reloading and eliminating the need for complex and fragile watches to fulfil e.g. transpiling to the CommonJS artefact pointed to by \"main\", or prepublish/postpublish scripts to rewrite \"main\".\r\n\r\n* Within a downstream project that consumed an npm package following this convention (and including Typescript source) the downstream bundling process could consume source before it had been through any prior bundling process, minimising cruft and increasing the chances of adequate sourcemapping.","author":{"url":"https://github.com/cefn","@type":"Person","name":"cefn"},"datePublished":"2022-12-04T23:51:38Z","url":"https://github.com/microsoft/TypeScript/issues/51750"}

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:a1b244ae-a873-3911-d50b-0742d98f251a
current-catalog-service-hash81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114
request-id80E8:269AD9:27CD688:35281A3:6B01B0ED
html-safe-nonce80fe56419ab99ddb08ee8d1aab2266c82b4e3b85130ff107898068fdf4550be4
visitor-payloadeyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiI4MEU4OjI2OUFEOToyN0NENjg4OjM1MjgxQTM6NkIwMUIwRUQiLCJ2aXNpdG9yX2lkIjoiNDk1OTU4ODExOTc1MjAxMDA1IiwicmVnaW9uX2VkZ2UiOiJpYWQiLCJyZWdpb25fcmVuZGVyIjoiaWFkIn0=
visitor-hmacb9a8b3621903c2b137e46ef99e72a3d8721c0c3f89d72e38119fa528a25d7ae2
hovercard-subject-tagissue:1475314796
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/51750/issue_layout
twitter:imagehttps://opengraph.githubassets.com/e8bfb78e7c5613bbcdfd6724cafc5a9a5329926e991038e96c4cc846b8c9a754/microsoft/TypeScript/issues/51750
twitter:cardsummary_large_image
og:imagehttps://opengraph.githubassets.com/e8bfb78e7c5613bbcdfd6724cafc5a9a5329926e991038e96c4cc846b8c9a754/microsoft/TypeScript/issues/51750
og:image:altSuggestion Establish a convention for a field in package.json that will to point to Typescript source code, respected as an override by tsc, for IDE and downstream build tooling. 🔍 Search Terms Lis...
og:image:width1200
og:image:height600
og:site_nameGitHub
og:typeobject
og:author:usernamecefn
hostnamegithub.com
expected-hostnamegithub.com
Nonecc5dfdd32f62ebd3223cab3af3aa2b268d3605218237326a48a99d1efd89495c
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
release8c77c9e8439031ad54c75a250694842892f693e1
ui-targetfull
theme-color#1e2327
color-schemelight dark
react-app-nameissues

Links:

Skip to contenthttps://github.com/microsoft/TypeScript/issues/51750#start-of-content
https://github.com/
Sign inhttps://github.com/login?return_to=https%3A%2F%2Fgithub.com%2Fmicrosoft%2FTypeScript%2Fissues%2F51750
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%2F51750
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/51750
Reloadhttps://github.com/microsoft/TypeScript/issues/51750
Reloadhttps://github.com/microsoft/TypeScript/issues/51750
microsofthttps://github.com/microsoft
TypeScripthttps://github.com/microsoft/TypeScript
Codehttps://github.com/microsoft/TypeScript
Issues5k (5k)https://github.com/microsoft/TypeScript/issues
Pull requests312 (312)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/51750
New issuehttps://github.com/login?return_to=https://github.com/microsoft/TypeScript/issues/51750
Establish a package.json convention for Typescript source in monorepos and npm packageshttps://github.com/microsoft/TypeScript/issues/51750#top
https://github.com/cefn
Cefn Hoile (cefn)https://github.com/cefn
on Dec 4, 2022https://github.com/microsoft/TypeScript/issues/51750#issue-1475314796
TypeScript's Design Goalshttps://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals
https://github.com/cefn
Cefn Hoile (cefn)https://github.com/cefn
on Dec 5, 2022https://github.com/microsoft/TypeScript/issues/51750#issuecomment-1336557026
#21423https://github.com/microsoft/TypeScript/issues/21423
Cefn Hoile (cefn)https://github.com/cefn
completedhttps://github.com/microsoft/TypeScript/issues?q=is%3Aissue%20state%3Aclosed%20archived%3Afalse%20reason%3Acompleted
on Dec 5, 2022https://github.com/microsoft/TypeScript/issues/51750#event-7949581843
microsofthttps://github.com/microsoft
on Oct 22, 2025https://github.com/microsoft/TypeScript/issues/51750#event-20417635952
Sign up for freehttps://github.com/signup?return_to=https://github.com/microsoft/TypeScript/issues/51750
Sign in to commenthttps://github.com/login?return_to=https://github.com/microsoft/TypeScript/issues/51750
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.