feat(frontend): init nextjs frontend app

.github/pull_request_template.md

@@ -0,0 +1,11 @@
+**Motivation:**
+
+Explain here the context, and why you're making that change. What is the problem you're trying to solve.
+
+**Modifications:**
+
+Describe the modifications you've done.
+
+**Result:**
+
+After your change, what will change.

.github/workflows/lint.yml

@@ -0,0 +1,24 @@
+name: Lint
+
+on:
+  pull_request:
+
+jobs:
+  lint:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+      - name: Cache Biome
+        uses: actions/cache@v4
+        with:
+          path: ~/.cache/biome
+          key: biome-${{ runner.os }}-${{ hashFiles('biome.json') }}
+          restore-keys: |
+            biome-${{ runner.os }}-
+      - name: Setup Biome
+        uses: biomejs/setup-biome@v2
+        with:
+          version: 2.1.2
+      - name: Run Biome
+        run: biome ci --linter-enabled=true --formatter-enabled=true

.gitignore

@@ -19,3 +19,66 @@ target
 #  and can be added to the global gitignore or merged into this file.  For a more nuclear
 #  option (not recommended) you can uncomment the following to ignore the entire idea folder.
 #.idea/
+
+# See https://help.github.com/articles/ignoring-files/ for more about ignoring files.
+
+# dependencies
+/node_modules
+/.pnp
+.pnp.*
+.yarn/*
+!.yarn/patches
+!.yarn/plugins
+!.yarn/releases
+!.yarn/versions
+build/
+# testing
+/coverage
+frontend/.cache-synpress/
+frontend/playwright-results/
+frontend/test-results/
+de_data.csv
+
+claim_*.csv
+claim_data.csv
+
+# next.js
+frontend/.next/
+/out/
+
+# production
+/build
+
+# misc
+.DS_Store
+*.pem
+
+# debug
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*
+.pnpm-debug.log*
+
+# env files (can opt-in for committing if needed)
+.env*
+!.env.example
+
+# vercel
+.vercel
+
+# typescript
+*.tsbuildinfo
+next-env.d.ts
+
+# Sentry Config File
+.env.sentry-build-plugin
+
+# Playwright
+node_modules/
+/test-results/
+/playwright-report/
+/blob-report/
+/playwright/.cache/
+
+.claude
+dist/

.vscode/extensions.json

@@ -0,0 +1,3 @@
+{
+  "recommendations": ["biomejs.biome"]
+}

.vscode/settings.json

@@ -0,0 +1,26 @@
+{
+  "biome.enabled": true,
+  "eslint.enable": true,
+  "editor.defaultFormatter": "biomejs.biome",
+  "editor.formatOnPaste": false,
+  "editor.formatOnSave": true,
+  "editor.codeActionsOnSave": {
+    "quickfix.biome": "always",
+    "source.organizeImports.biome": "always"
+  },
+  "[typescriptreact]": {
+    "editor.defaultFormatter": "biomejs.biome"
+  },
+  "[typescript]": {
+    "editor.defaultFormatter": "biomejs.biome"
+  },
+  "[css]": {
+    "editor.defaultFormatter": "biomejs.biome"
+  },
+  "[json]": {
+    "editor.defaultFormatter": "biomejs.biome"
+  },
+  "[jsonc]": {
+    "editor.defaultFormatter": "biomejs.biome"
+  }
+}

CODEOWNERS

@@ -0,0 +1 @@
+*       @austingreen @marcuspang @0xflashboy @Im-Madhur-Gupta @nkrishang @mijovic @Camillebzd @iamvukasin

CONTRIBUTING.md

@@ -0,0 +1,91 @@
+# Contribution guide
+
+NOTE: This format should only be followed after your PR gets approved and you are squashing your commits to merge to main.
+
+Please consider these guidelines when filing a pull request:
+
+* Please write tests.
+* After your PR gets approved, you should squash your commits when merging to main, and follow the convention below.
+
+## Final Commit Message Format
+
+Commit message consists of a **header**, a **body** and a **footer**.  The header has a special
+format that includes a **type**, a **scope**, **subject**, and should also include the PR number in parenthesis:
+
+```html
+feat(Buttons): Added Button Groups (#622)
+<BLANK LINE>
+<body>
+<BLANK LINE>
+<optional footer>
+```
+
+The **header** is mandatory and the **scope** of the header is optional.
+
+The **body** should contain the motivation, that's where you describe the context of the change, the history how the code relates to other code, what the problem is and why it is a problem. That should be followed by describing the changes the commit actually makes. Do not focus too much on how the code works as that is better described as source code comments in the patch itself (to the extend that your code needs to be explained). Rather focus on the change itself.
+
+Finally, describe what effects the change will have. Sometimes this is trivial, like a bug that was described in the motivation is now fixed.
+
+### Example
+
+An example of a fix commit would look like this:
+
+```markdown
+fix: Remove semicolon from N4CC's set of wrappable chars (#201)
+
+**Motivation:**
+
+The comment above `ShouldWrapCharsBitSet` suggests that semicolons are legal
+according to Netty 4's encoder and decoder, but they are not.
+
+**Modifications:**
+
+Remove the semicolon character from the bit set.
+
+**Result:**
+
+Now the bit set is correctly aligned with Netty 4's strict validation rules and
+the comment is correct. There is no difference in behavior since validation
+happens after unwrapping: a semicolon in a cookie value will cause the
+validation to fail regardless of whether the value is wrapped.
+```
+
+Another example would be of an feature that contains a breaking change:
+
+```markdown
+feat: Introduce `.withDeadlines` API for admission control (#228)
+
+**Motivation:**
+
+We would like deadline admission control to be turned on by default.
+
+**Modifications:**
+
+Introduce new APIs so that servers can be configured with
+`Server.withAdmissionControl.deadlines` to turn deadlines on,
+`.darkModeDeadlines` to turn deadlines on in dark mode, and `.noDeadlines` so
+that `DeadlineFilter` can be turned on off. We also introduce more params for
+configuring `DeadlineFilter`'s window for when `DeadlineFilter` is enabled or in
+dark mode.
+
+**Result:**
+
+BREAKING CHANGE: Rename DeadlineFilter.Param(maxRejectFraction) to
+DeadlineFilter.MaxRejectFraction(maxRejectFraction) to reduce confusion
+when adding additional params.
+```
+
+### Type
+
+Must be one of the following:
+
+* **feat**: A new feature
+* **fix**: A bug fix
+* **docs**: Documentation only changes
+* **style**: Changes that do not affect the meaning of the code (white-space, formatting, missing
+  semi-colons, etc)
+* **refactor**: A code change that neither fixes a bug nor adds a feature
+* **perf**: A code change that improves performance
+* **test**: Adding missing or correcting existing tests
+* **chore**: Changes to the build process or auxiliary tools and libraries such as documentation
+  generation

biome.json

@@ -0,0 +1,75 @@
+{
+  "$schema": "https://biomejs.dev/schemas/2.1.2/schema.json",
+  "vcs": {
+    "enabled": true,
+    "clientKind": "git",
+    "useIgnoreFile": true
+  },
+  "root": true,
+  "files": {
+    "ignoreUnknown": false
+  },
+  "formatter": {
+    "enabled": true,
+    "indentStyle": "space",
+    "indentWidth": 2
+  },
+  "linter": {
+    "enabled": true,
+    "rules": {
+      "recommended": true,
+      "correctness": {
+        "useExhaustiveDependencies": "off",
+        "noUnusedFunctionParameters": {
+          "level": "error",
+          "fix": "none"
+        },
+        "noUnusedVariables": {
+          "level": "error",
+          "fix": "none"
+        }
+      },
+      "style": {
+        "useImportType": "error",
+        "useTemplate": {
+          "level": "error",
+          "fix": "safe"
+        },
+        "useSelfClosingElements": {
+          "level": "error",
+          "fix": "safe"
+        },
+        "noUnusedTemplateLiteral": {
+          "level": "error",
+          "fix": "safe"
+        },
+        "noNonNullAssertion": {
+          "level": "warn"
+        }
+      },
+      "suspicious": {
+        "noArrayIndexKey": "warn"
+      }
+    }
+  },
+  "javascript": {
+    "formatter": {
+      "quoteStyle": "single",
+      "semicolons": "asNeeded"
+    }
+  },
+  "json": {
+    "formatter": {
+      "indentStyle": "space",
+      "indentWidth": 2
+    }
+  },
+  "assist": {
+    "enabled": true,
+    "actions": {
+      "source": {
+        "organizeImports": "on"
+      }
+    }
+  }
+}

frontend/.gitignore

@@ -0,0 +1,41 @@
+# See https://help.github.com/articles/ignoring-files/ for more about ignoring files.
+
+# dependencies
+/node_modules
+/.pnp
+.pnp.*
+.yarn/*
+!.yarn/patches
+!.yarn/plugins
+!.yarn/releases
+!.yarn/versions
+
+# testing
+/coverage
+
+# next.js
+/.next/
+/out/
+
+# production
+/build
+
+# misc
+.DS_Store
+*.pem
+
+# debug
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*
+.pnpm-debug.log*
+
+# env files (can opt-in for committing if needed)
+.env*
+
+# vercel
+.vercel
+
+# typescript
+*.tsbuildinfo
+next-env.d.ts

frontend/README.md

@@ -0,0 +1,36 @@
+This is a [Next.js](https://nextjs.org) project bootstrapped with [`create-next-app`](https://nextjs.org/docs/app/api-reference/cli/create-next-app).
+
+## Getting Started
+
+First, run the development server:
+
+```bash
+npm run dev
+# or
+yarn dev
+# or
+pnpm dev
+# or
+bun dev
+```
+
+Open [http://localhost:3000](http://localhost:3000) with your browser to see the result.
+
+You can start editing the page by modifying `app/page.tsx`. The page auto-updates as you edit the file.
+
+This project uses [`next/font`](https://nextjs.org/docs/app/building-your-application/optimizing/fonts) to automatically optimize and load [Geist](https://vercel.com/font), a new font family for Vercel.
+
+## Learn More
+
+To learn more about Next.js, take a look at the following resources:
+
+- [Next.js Documentation](https://nextjs.org/docs) - learn about Next.js features and API.
+- [Learn Next.js](https://nextjs.org/learn) - an interactive Next.js tutorial.
+
+You can check out [the Next.js GitHub repository](https://github.com/vercel/next.js) - your feedback and contributions are welcome!
+
+## Deploy on Vercel
+
+The easiest way to deploy your Next.js app is to use the [Vercel Platform](https://vercel.com/new?utm_medium=default-template&filter=next.js&utm_source=create-next-app&utm_campaign=create-next-app-readme) from the creators of Next.js.
+
+Check out our [Next.js deployment documentation](https://nextjs.org/docs/app/building-your-application/deploying) for more details.