Fix OpenAPI spec file path resolution#12
Merged
mikesellitto merged 1 commit intomainfrom Feb 24, 2026
Merged
Conversation
emily-curry
reviewed
Feb 24, 2026
Member
emily-curry
left a comment
emily-curry
left a comment
There was a problem hiding this comment.
Could we instead include this file in the published files so that this continues to work while testing locally?
mikesellitto
force-pushed
the
mike/fix-openapi-spec-resolution
branch
from
2499cca to
8f218e9
Compare
Contributor
Author
🤦🏻 Done in the latest force push |
emily-curry
approved these changes
Feb 24, 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
2 participants
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.
Currently, the OpenAPI spec is copied into
dist/during build, but the runtime path resolves to the parent directory. Users installing/running with npm/npx get a missing file error since onlydist/is published.This PR fixes that.