Dynamic Code Evaluation prevents Flagsmith to run on Next.js middlewares about flagsmith-js-client

[alizain]

my bad, i couldn't find the correct file :)

[cagrispan]

Nice @kyle-ssg! Thank you!

[alizain]

@dabeeeenster all of the flagsmith code is obfuscated and compiled. you don't provide unobfuscated source. you've added the help-wanted label, but what's the best way for us to help?

[dabeeeenster]

Hi @alizain - i don't follow - the source is in this repo?

[kyle-ssg]

Hey @cagrispan, this wasn't on my radar but I'd like to help with this - am a massive fan of Next.js. It might actually be worth trying with the latest version >3, calls to async storage now check for typeof window, e.g https://github.com/Flagsmith/flagsmith-js-client/blob/main/flagsmith-core.ts#L270

[kyle-ssg]

This is now available in flagsmith 3.3.2, there's a working example here

[kyle-ssg]

No problem! I'd love to hear about what you do with it, had a play around with it today, It looks like the main use cases would be redirecting for abn tests maybe

[cagrispan]

Precisely. Since it was not supported then, we are calling Flagsmith API to retrieve the flags and route based on that. And you are right, it's for ab tests.