Add nextJSTypescriptTemplate

[dellorogiulio]

Hi @microhobby ,
i just prefered to create a new pull request instead of continuing the @escherstair one.
I decide to create the template for NextJS starting from the 'old' pages structure and not the 'new' src directory. It can be easily changed in case.
I tested the created container and runs with no problem on my module. I didn't test the Dockerfile.debug but I take it from the previous PR from @escherstair, so, should be fine.

I could miss something more related to torizonCore since I focus on the NextJS part, feel free to test scripts etc.

[microhobby]

hey, @dellorogiulio thanks for the contribution. I did a rebase taking as a reference the dev branch which should be the branch to include new templates.

Let me ask, are you guys not using a docker-compose.yml file?

[dellorogiulio]

Currently we are using no docker-compose, but I think that this should be fine

version: "3.9"
services:
  __container__-debug:
    build:
      context: .
      dockerfile: Dockerfile.debug
    image: ${LOCAL_REGISTRY}:5002/__container__-debug:${TAG}
    ports:
      - 2229:2229
      - 9229:9229
      - 9230:9230
      - 9231:9231


  __container__:
    build:
      context: .
      dockerfile: Dockerfile
    image: ${DOCKER_LOGIN}__container__:${TAG}
    ports:
      - 3000:3000

[microhobby]

Hey @dellorogiulio I was testing here and trying to attach to the debugger but seems that something has been crashed on the Next JS side: vercel/next.js#55862

So, I will wait until they fix this.

[escherstair]

Hi @microhobby
they should have fixed with this PR (already merged)

[escherstair]

Next.js team worked on this issue and now it seems that this PR fixed it.
It's in the canary branch and I think it will be included in the upcoming v14.0.5 release

[escherstair]

Hi @microhobby
Next.js v14.1.0 has been released and it includes the fix.
Can you verify if now the Next.js Typescript Template works?

[microhobby]

Hey @escherstair we are in the process to release in this weekend a new version. I'm putting this to be reviewed in the next dev cycle. Thanks to point!

[escherstair]

Hi @microhobby
do you have news on the merge of this PR?
Thanks

[microhobby]

Hi @escherstair and @dellorogiulio sorry for the delay.
I tested it again and now with the latest NextJS version, but still no success trying to connect to the debugger node inspect. I opened a new issue there: vercel/next.js#66189

So, we will need to wait for this fix. Inside the container, we must set the NODE_OPTIONS='--inspect=0.0.0.0:9229' to be able to connect the debugger inside the container.

[microhobby]

Waiting for NextJS fix.

[escherstair]

Hi @microhobby thank you...
Sad to see that this feature is broken again