feat: add Nextjs SSR example

[raynerljm]

Problem

Our SDK currently lacks example apps demonstrating how to use our SDK. This introduces two problems

1. RPs do not have example apps following good practices to refer to
2. We are not able to easily test SDK changes with an app (we need to do an npm link)

Closes #384

Solution

Added an example Next.js app using SSR and server components (Next.js 13.4 feature). It is hosted here.

Features:

• Utilizes an in-memory store src/lib/store.js to store Session data (e.g. state, nonce, codeVerifier, etc.)

Tests

// TODO: ADD recording

[kwajiehao]

Left some comments, but otherwise looks good to me!

I have 2 more points I wanted to talk about:

1. PKCE

What is the plan for this? I think it might be useful to include PKCE in this example, keen to hear your thoughts on how we planned to roll that out

2. Error-handling

I know we are using an in-memory data store, which makes sense. But currently if you complete the login flow, and then refresh the page, you get this error page:

I'm wondering if it would be more useful if we can render an error page instead with some information on why this is not showing / some other kind of error message.

What do you think?

[kwajiehao]

Can we remove this file and add .DS_Store to our .gitignore file?

[raynerljm]

yup okay!

[kwajiehao]

Again, remove this file

[raynerljm]

👍

[raynerljm]

@kwajiehao with regards to your 1st point - yes! when you reviewed it the example had yet to be updated with PKCE (that's why it's WIP) - but now I've updated it with PKCE

with regards to the 2nd point - the error messages are not showing up because we are using next start to run the server and thus it's treated as a prod environment as the error messages are being omitted. I've searched around and I'm not sure that Next.js allows us to run next start while changing NODE_ENV to development. we could instead put change the message to prompt users to check their terminal for the error instead - what do you think?

[PrawiraGenestonlia]

with regards to the 2nd point - the error messages are not showing up because we are using next start to run the server and thus it's treated as a prod environment as the error messages are being omitted. I've searched around and I'm not sure that Next.js allows us to run next start while changing NODE_ENV to development. we could instead put change the message to prompt users to check their terminal for the error instead - what do you think?

This is next.js new features. It does not forward server error to FE through SSR unless we do special error boundary. Let's exclude this for this release because I don't think this is super important. Just some next.js shit features..

[kwajiehao]

with regards to the 2nd point - the error messages are not showing up because we are using next start to run the server and thus it's treated as a prod environment as the error messages are being omitted. I've searched around and I'm not sure that Next.js allows us to run next start while changing NODE_ENV to development. we could instead put change the message to prompt users to check their terminal for the error instead - what do you think?

Saw the changes you made - they look good to me! Don't think we need to do anything more beyond that. Thanks @raynerljm

[kwajiehao]

lgtm