add named export for main Turnstile component#45
Merged
Le0Developer merged 1 commit intoLe0Developer:mainfrom Jan 30, 2026
Merged
add named export for main Turnstile component#45Le0Developer merged 1 commit intoLe0Developer:mainfrom
Le0Developer merged 1 commit intoLe0Developer:mainfrom
Conversation
We keep the existing default export to maintain backwards compatibility.
Le0Developer
approved these changes
Jan 30, 2026
Owner
Le0Developer
left a comment
Le0Developer
left a comment
There was a problem hiding this comment.
LGTM. Sorry for the late review.
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.
This adds a named export
Turnstilefor the main component, which is the same as the default export, and bumps the version to 1.1.5.The reason for this is that modern tools like Rolldown wrecks / reformats exports of libraries that have both a default export and named exports, leading to the following error:
This behaviour is likely the root cause behind issue #24.
Providing a named export and making this the suggested way to consume the exports gives users a way out of this behaviour. The existing default export is still kept as is to maintain backwards compatibility.