fix(ai-proxy): re-export FOREST_INTEGRATION_NAMES from package index [PRD-375]#1589
Merged
matthv merged 1 commit intoMay 20, 2026
Merged
Conversation
…[PRD-375] The const was declared and exported from forest-integration-client.ts in 1.10.0, but the package's index.ts has a selective re-export block that did not include it. Consumers importing from '@forestadmin/ai-proxy' got undefined at runtime and any at types. This adds the missing re-export so the runtime const is accessible through the package's main entry point, completing the work started in 1.10.0. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Scra3
approved these changes
May 20, 2026
|
Coverage Impact This PR will not change total coverage. Modified Files with Diff Coverage (1)
🛟 Help
|
forest-bot
added a commit
that referenced
this pull request
May 20, 2026
## @forestadmin/ai-proxy [1.10.1](https://github.com/ForestAdmin/agent-nodejs/compare/@forestadmin/ai-proxy@1.10.0...@forestadmin/ai-proxy@1.10.1) (2026-05-20) ### Bug Fixes * **ai-proxy:** re-export FOREST_INTEGRATION_NAMES from package index [PRD-375] ([#1589](#1589)) ([909d050](909d050))
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.

Summary
Follow-up to #1588 (released as ai-proxy@1.10.0). The const
FOREST_INTEGRATION_NAMESwas declared and exported fromforest-integration-client.tsbut the package'ssrc/index.tshas a selective named re-export block that did not include it. Consumers importing from@forestadmin/ai-proxygetundefinedat runtime andanyat the type level — the const is effectively invisible from the package boundary.Change
```diff
export {
ForestIntegrationConfig,
CustomConfig,
ForestIntegrationName,
} from './forest-integration-client';
```
How this slipped through 1.10.0
The original PR added tests inside ai-proxy that touched the file directly, so the internal declaration looked fine. No test asserted the visibility from the package's main entry. Caught only when wiring up the first consumer (forestadmin-server PR #8249) — the
yarn upgradeto 1.10.0 + theimport { FOREST_INTEGRATION_NAMES }swap failed lint and typecheck withanyerrors, which surfaced the missing re-export.Test plan
Release
Patch release (1.10.1) appropriate — fixes the export visibility intended in 1.10.0, no behavioral change for consumers already importing the type.
relates to PRD-375
🤖 Generated with Claude Code
Note
Re-export
FOREST_INTEGRATION_NAMESfromai-proxypackage indexAdds
FOREST_INTEGRATION_NAMESto the named exports in index.ts, alongside the existingForestIntegrationConfig,CustomConfig, andForestIntegrationNameexports from./forest-integration-client.🖇️ Linked Issues
Resolves PRD-375.
Macroscope summarized 80f7257.