I can confirm the issue, switching my node version to 14 fixed it for me.
I am assuming there were breaking changes with next 11 and newer node versions.
We are in the process of updating our starter to use Next 13, will let you know when it is ready.
But for now, if you would like to use the current starter, you need to use node 14.
Let me know if you have any other questions.