Deprecated redirectUrl persists in production build output (v0.90.5)

[wendychowusgithub]

What happened?

Hi Plasmo Team,

I'm encountering an issue with Plasmo version 0.90.5. The production build output (build/chrome-mv3-prod/popup..js) contains numerous instances of the deprecated redirectUrl prop.

However, my source code (popup.tsx) correctly uses from @clerk/chrome-extension and does not contain the redirectUrl prop anywhere.

This issue persists even after:

Running pnpm build --no-cache.

Deleting the build, .plasmo, and node_modules folders before reinstalling and rebuilding.

The consequence is that the Clerk sign-in button fails in the built extension, and the browser console shows the redirectUrl deprecation warning, pointing to the incorrectly generated code.

Could you please investigate why the build process might be injecting this deprecated prop despite the correct source code and cache clearing attempts?

Thanks!

popup.tsx

Version

Latest

What OS are you seeing the problem on?

Windows

What browsers are you seeing the problem on?

Chrome

Relevant log output

Background script loaded.
popup.100f6462.js:412 Clerk: Clerk has been loaded with development keys. Development instances have strict usage limits and should not be used when deploying your application to production. Learn more: https://clerk.com/docs/deployments/overview
warnOnce @ popup.100f6462.js:412Understand this warning
popup.100f6462.js:412 Clerk: The prop "redirectUrl" is deprecated and should be replaced with the new "fallbackRedirectUrl" or "forceRedirectUrl" props instead. Learn more: https://clerk.com/docs/guides/custom-redirects#redirect-url-props

(OPTIONAL) Contribution

• I would like to fix this BUG via a PR

Code of Conduct

• I agree to follow this project's Code of Conduct
• I checked the current issues for duplicate problems.