Fix sdk root imports in file-secrets and keychain plugins - #1838
Merged
Conversation
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
executor-marketing | 607a1df | Commit Preview URL Branch Preview URL |
Aug 29 2026, 06:45 AM |
Contributor
Cloudflare previewTorn down — the PR is closed. |
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ✅ Deployment successful! View logs |
executor-cloud | 607a1df | Aug 29 2026, 06:47 AM |
@executor-js/cli
@executor-js/config
@executor-js/execution
@executor-js/sdk
@executor-js/codemode-core
@executor-js/runtime-quickjs
@executor-js/plugin-file-secrets
@executor-js/plugin-graphql
@executor-js/plugin-keychain
@executor-js/plugin-mcp
@executor-js/plugin-onepassword
@executor-js/plugin-openapi
executor
commit: |
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 #1833
plugin-file-secretsandplugin-keychainimportedStorageError,definePlugin,PluginCtx, andPluginfrom the@executor-js/sdkroot. In the workspace, the root and/coreboth resolve tosrc/index.ts, so everything worked in-repo. The published root is the Promise surface (dist/index.js), which does not export those symbols, so both packages failed to load when installed from npm.Change
@executor-js/sdk/core, the same wayplugin-onepassworddoes. This covers all five affected files;ProviderKey,ProviderItemId, andCredentialProvidermove with them since/coreexports the full Effect surface.scripts/smoke-test-packed.ts: adoes not provide an export namedfailure is now a hard FAIL. It was previously downgraded to a skip, which is how this shipped past the release smoke gate.A browser e2e is meaningless for a packaging bug — nothing user-visible changes in the app. The repro below is at the published surface, the way an npm consumer resolves the packages.
Red (before the fix)
Packed all public packages via
publish-packages.ts --dry-run, installed the two plugin tarballs into a fresh fixture with npmoverridespinning every@executor-js/*dep to its local tarball, then imported with node:Green (after the fix)
Same pack-and-install fixture:
Gates:
format:check,lint,typecheck, and package tests for both plugins (18 + 3) all pass.