[SDK-813] Remix: Provide Non-Root Implementation #1963
Closed
parisholley
started this conversation in
Feature Requests
Replies: 3 comments 1 reply
-
Hello! We're tracking our feature requests now in feedback.clerk.com. If your suggestion is already in the list of proposed changes, please upvote. Otherwise, please create an entry. Thanks! Our feedback platform will be the source of truth for feature requests going forward and your input and votes will help us shape the roadmap. Thanks for using Clerk! 💙 |
Beta Was this translation helpful? Give feedback.
0 replies
-
Super +1 on this. It would be a huge win given many apps can have a large "logged out" section of routes where there is no need to call the clerk auth endpoint. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Preliminary Checks
I have reviewed https://clerk.com/docs for existing features that would solve my problem
I have searched for existing feature requests: https://github.com/clerkinc/javascript/issues
This issue is not a question, general help request, or anything other than a feature request directly related to Clerk. Please ask questions in our Discord community: https://clerk.com/discord.
Description
The current documentation encourages the user to create a root loader and wrap the main App with
ClerkApp
however this is not an efficient implementation for a few reasons:getAuth()
in a loader will cause additional requests as there is no request-level cache (eg: storing promise on the remix context, keeping in mind that loaders execute in parallel).Rather than only offer
ClerkApp
as a solution, encourage the user useClerkProvider
directly and provide agetClerkState()
call that returns valid types for TS.Affected Packages
@clerk/remix
SDK-813
Beta Was this translation helpful? Give feedback.
All reactions