vercel feature flags about remix

[TooTallNate]

I created an example repo to show how to use @vercel/flags with Remix via just the Vercel toolbar (no provider): https://github.com/TooTallNate/remix-feature-flags/tree/main/app

[TooTallNate]

Was there something Remix-specific that you are looking for? The @vercel/flags package should work in your loader/action functions already. Let me know if you are running into any issues though.

[lifeiscontent]

@TooTallNate yeah, it's been a long time since I've used Next.js so I've forgotten a lot of the conventions.

e.g. is app/page.tsx similar to root.tsx or app/routes/_index.tsx?

do I want this script tag to run on all pages? or only the pages that have a feature backed by a feature flag?

https://vercel.com/docs/workflow-collaboration/feature-flags/supporting-feature-flags#exposing-feature-flags-to-the-vercel-toolbar

for this link:

https://vercel.com/docs/workflow-collaboration/feature-flags/supporting-feature-flags#api-endpoint-recommended

it mentions providers, but is there a way to use feature flags via just the vercel toolbar and not have a provider at all?

if so, what should I set as origin if anything?

[lifeiscontent]

@TooTallNate thank you for your help :)

is there a reason why you're using the cookie package vs https://remix.run/docs/en/main/utils/cookies ?

[lifeiscontent]

@TooTallNate FlagValues component doesn't accept a nonce parameter, so far that's been my only issue.

[lifeiscontent]

nvm, I realized remix is using the cookie package under the hood and they're doing some extra magic on top with createCookie

[TooTallNate]

I pushed some improvements after reading through the Vercel Feature Flags documentation some more. You can now add metadata like a description and link to the flags in the toolbar, and the toolbar is loaded during development as well.

I'll close out this issue now.