Skip to content

Commit 15f369c

Browse files
authored
[ADR-0006] Use Next.js framework (#1090)
1 parent 5372044 commit 15f369c

File tree

1 file changed

+28
-0
lines changed

1 file changed

+28
-0
lines changed

doc/adr/0007-use-nextjs.md

+28
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,28 @@
1+
# 7: Use pnpm packagage manager
2+
3+
Date: 2024-04-29
4+
5+
## Status
6+
7+
Accepted
8+
9+
## Context
10+
11+
AsyncAPI Studio is currently a CRA application and runs entirely on the client.
12+
We find the need for a more robust and scalable solution to handle UI rendering and enhance the user experience. There are several [key considerations](https://github.com/asyncapi/studio/issues/661#issuecomment-1594226439) leading to this proposal.
13+
14+
15+
## Decision
16+
17+
Following [our discussion](https://github.com/asyncapi/studio/issues/661), we have decided to adopt Next.js as the new front-end framework for AsyncAPI Studio. Next.js offers several advantages that align with our requirements:
18+
19+
- **Server-Side Rendering (SSR)**: Next.js allows components to render on the server side, speeding up initial page load times in the future.
20+
- **Automatic Code Splitting**: It automatically splits code at the component level, allowing users to load only the necessary amount of code. It will be specially useful when we have the visaul editor.
21+
22+
23+
## Consequences
24+
25+
Adopting Next.js for AsyncAPI Studio will lead to:
26+
27+
- Improved Load Times and Performance.
28+
- Intial effort for migration.

0 commit comments

Comments
 (0)