-
-
Notifications
You must be signed in to change notification settings - Fork 98
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[ADR-0006] Use Next.js framework (#1090)
- Loading branch information
1 parent
5372044
commit 15f369c
Showing
1 changed file
with
28 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,28 @@ | ||
# 7: Use pnpm packagage manager | ||
|
||
Date: 2024-04-29 | ||
|
||
## Status | ||
|
||
Accepted | ||
|
||
## Context | ||
|
||
AsyncAPI Studio is currently a CRA application and runs entirely on the client. | ||
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. | ||
|
||
|
||
## Decision | ||
|
||
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: | ||
|
||
- **Server-Side Rendering (SSR)**: Next.js allows components to render on the server side, speeding up initial page load times in the future. | ||
- **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. | ||
|
||
|
||
## Consequences | ||
|
||
Adopting Next.js for AsyncAPI Studio will lead to: | ||
|
||
- Improved Load Times and Performance. | ||
- Intial effort for migration. |