Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[ADR-0006] Use Next.js framework #1090

Merged
merged 1 commit into from
Apr 29, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
28 changes: 28 additions & 0 deletions doc/adr/0007-use-nextjs.md
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.
Loading