Add missing exports entries for published JSON config files#5659
Merged
Add missing exports entries for published JSON config files#5659
exports entries for published JSON config files#5659Conversation
…t-plugin Co-authored-by: iclanton <5010588+iclanton@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Add missing exports to package.json for all packages
Add missing exports for JSON config files in api-extractor and heft-jest-plugin
Feb 21, 2026
iclanton
requested review from
apostolisms,
bmiddha,
dmichon-msft,
jxanthony and
octogonz
as code owners
iclanton
approved these changes
Feb 21, 2026
Copilot
AI
changed the title
Add missing exports for JSON config files in api-extractor and heft-jest-plugin
Add missing Feb 21, 2026
exports entries for published JSON config files
octogonz
approved these changes
Feb 21, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #5658
PR #5628 added
exportsfields to all packages, which restricts importable subpaths. Two packages had published JSON config files referenced by consumers that were not included inexports:@microsoft/api-extractor: Add"./extends/*.json"forextends/tsdoc-base.json, used via"extends": ["@microsoft/api-extractor/extends/tsdoc-base.json"]in consumertsdoc.jsonfiles@rushstack/heft-jest-plugin: Add"./includes/*.json"forjest-shared.config.jsonandjest-web.config.json, used via"extends": "@rushstack/heft-jest-plugin/includes/jest-shared.config.json"in consumer Jest configsAudited all ~130 packages with
exportsfields. Schema files (*.schema.json) are already covered everywhere via the existing"./lib/*.schema.json"pattern. Other manifest files (heft-plugin.json,rush-plugin-manifest.json,rush-mcp-plugin.json) are either already exported or loaded via filesystem paths rather than Node module resolution.💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.