[nextjs starters] Replace ngrok with alternatives for having HTTPS

[edvinasjurele]

Thank you a lot for nice NextJS starters for both tool and space plugins in the repo! The new app bridge oauth solution works smoothly, though we have some suggestions.

This is related to storyblok/app-extention-auth and the nextjs starters (tool and space).

As mentioned in https://github.com/storyblok/app-extension-auth?tab=readme-ov-file#getting-started, the ngrok is needed to quickly get HTTPS:

The base URL must be absolute and secure with https.

Using ngrok turns out to be an overhead:

• ngrok is being flagged as malware in companys' malware scanning software, therefore requires whitelisting it for each computer.
• ngrok may expose development and potentially sensitive data to be accessible publicly.
• ngrok's free plan has limit of 20k requests monthly (not even speaking about creating an account in 3rd party), which means if there is a lot of development you can easily hit them.

I have checked for alternatives and it seems there is an easier way to get HTTPS in development in NextJS.

The issue is that the starters uses Next v13.4.19, while --experimental-https flag was introduced starting Next v13.5 and upwards (see docs)

Expected Behavior

Use minimum Next v13.5 (f.e. 13.5.7) + next dev --experimental-https

As a user, I would expect NextJS starters to recommend multiple alternatives for achieving HTTPS in development, leaving ngrok as one of choice and not the primary tool to use.

Current Behavior

Use Next v13.4.19 + ngrok = HTTPS