Repository navigation
ci: smoke-test framework adapter subpaths - #149
Merged
Merged
Conversation
Contributor
|
@poyrazavsever is attempting to deploy a commit to the CzayLabs Team on Vercel. A member of the Team first needs to authorize it. |
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.
What and why
Closes #148
The existing smoke tests resolve the core, testing and plugins entries, but do not check framework adapter exports. This adds package-name checks for next, express, hono, fastify, elysia and react-router in both CommonJS and ESM. Each check also verifies that the expected handler is a function.
The package-content step now requires every adapter's .js, .mjs and .d.ts artifacts. These checks use the existing Node 20/22/24 matrix. No runtime code, dependencies or public API changes.
Verification
Checklist