"Get Started" Button Not Functioning in Local Environment

[bhushang19]

• Followed Instructions provided in the readme.md file.
• Configured .env File: Added the Clerk API details and Supabase information to the .env file.
• Installed Dependencies: Ran npm install and ensured that the latest version of Next.js is installed.
• Started Development Server: Executed npm run dev.
• Checked for Compilation Issues: There were no compilation errors, and I can access the app at http://localhost:3000/.
• Encountered Problem: Clicking the "Get Started" button does not trigger any action.
• Provided Evidence: Attached a console image from the Edge browser for reference.

[RafiulM]

@bhushang19 The "Get Started" button was just meant to be a dummy component and isn't suppose to do anything which I agree is a bit confusing so you've raised a good point here. We're working on an improved starting page for the starter kits to provide better explanation on how to get started, so stay tune for this update. Thanks!

[fdeus]

So how do we use it now?

[RainNaZ]

If you have the same doubts, what is the effect?

[EdgarJob]

@bhushang19 The "Get Started" button was just meant to be a dummy component and isn't suppose to do anything which I agree is a bit confusing so you've raised a good point here. We're working on an improved starting page for the starter kits to provide better explanation on how to get started, so stay tune for this update. Thanks!

I encountered the same issue. Glad that its something in the works, but is there a timeline or tentative date when it will be fixed? Thanks in advance.