fix: resolve custom bundle paths in dev - #6990
Open
omercnet wants to merge 1 commit into
Open
Conversation
Author
|
CI is blocked pending maintainer approval of the fork workflow run: https://github.com/anomalyco/sst/actions/runs/33208975206 |
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
1 participant
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.
Related Issues
Fixes #6253
In a Nutshell
Description
Custom bundle paths remained relative during dev builds, while the Node runtime used the same path as both its working directory and part of the handler path. Resolve relative bundles against the SST config directory so dev handler loading matches deploy behavior, while preserving absolute bundle paths.
Must
Verification
go test ./pkg/runtimebun run test:clibun run build:platformbun run build:cli