dependabot[bot] cc8ee38701 Bump @next/bundle-analyzer from 15.2.0 to 15.3.0 in /frontend (#1186)
Bumps
[@next/bundle-analyzer](https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer)
from 15.2.0 to 15.3.0.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/vercel/next.js/releases"><code>@​next/bundle-analyzer</code>'s
releases</a>.</em></p>
<blockquote>
<h2>v15.3.0</h2>
<h3>Core Changes</h3>
<ul>
<li>[dev-overlay] Customize <code>&lt;select&gt;</code> styling for
consistency: <a
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/76973">#76973</a></li>
<li>Upgrade React from <code>029e8bd6-20250306</code> to
<code>0ca3deeb-20250311</code>: <a
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/76989">#76989</a></li>
<li>[metadata]: add pinterest meta tag: <a
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/76988">#76988</a></li>
<li>[dev-overlay] ensure stripping overlay bundle in prod build: <a
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/76976">#76976</a></li>
<li>Apply env inlining during generate build mode: <a
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/76990">#76990</a></li>
<li>Turbopack: Implement deploymentId: <a
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/76904">#76904</a></li>
<li>track persistent caching usage: <a
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/76996">#76996</a></li>
<li>[metadata] re-insert icons to head for streamed metadata: <a
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/76915">#76915</a></li>
<li>Upgrade React from <code>0ca3deeb-20250311</code> to
<code>6aa8254b-20250312</code>: <a
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/77033">#77033</a></li>
<li>Move static-env imports: <a
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/77035">#77035</a></li>
<li>[dev-overlay] Add <code>size</code> setting to preferences: <a
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/77027">#77027</a></li>
<li>Add config for only generating static env: <a
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/77038">#77038</a></li>
<li>chore(HMR clients): Clean up and share code between app and pages
router: <a
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/76960">#76960</a></li>
<li>Add dev warning for cross-origin and stabilize allowedDevOrigins: <a
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/77044">#77044</a></li>
<li>unify allowed origin detection handling: <a
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/77053">#77053</a></li>
<li>Handle hash change in all files for static env: <a
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/77058">#77058</a></li>
<li>[dev-overlay] highlight errored code line for runtime errors: <a
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/77078">#77078</a></li>
<li>NFT: Ignore all of Webpack: <a
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/77081">#77081</a></li>
<li>Add experimental build mode flag for env: <a
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/77089">#77089</a></li>
<li>(feat) support client-side instrumentation: <a
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/76916">#76916</a></li>
<li>Fix JSDoc comment for <code>'seconds'</code> cache life profile: <a
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/77084">#77084</a></li>
<li>refactor(HMR clients): Encapsulate some of the turbopack state
tracking into a shared TurbopackHmr class: <a
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/76994">#76994</a></li>
<li>Slightly improve error handling for unknown server actions: <a
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/77135">#77135</a></li>
<li>Fix output standalone for alternative bundler: <a
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/76971">#76971</a></li>
<li>Add alternate bundler plugin information to <code>next info</code>:
<a
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/77059">#77059</a></li>
<li>[metadata] remove the default segement check for metadata rendering:
<a
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/77119">#77119</a></li>
<li>[dev-overlay] Fix stacking order of highlighted line: <a
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/77189">#77189</a></li>
<li>Upgrade React from <code>6aa8254b-20250312</code> to
<code>5398b711-20250314</code>: <a
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/77129">#77129</a></li>
<li>fix(styled-jsx): Pass <code>useLightningcss</code> option to
<code>styled-jsx</code> correctly: <a
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/77008">#77008</a></li>
<li>log the instrumentation-client execution time: <a
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/77121">#77121</a></li>
<li>Turbopack: canary-gate production builds: <a
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/77146">#77146</a></li>
<li>[dev-overlay] remove special handling for missing tag error : <a
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/77147">#77147</a></li>
<li>chore(react-dev-overlay): Remove confusingly underscored variables
in <code>useErrorOverlayReducer</code>: <a
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/77205">#77205</a></li>
<li>Update middleware request header: <a
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/77201">#77201</a></li>
<li>Update default allowed origins list: <a
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/77212">#77212</a></li>
<li>Ensure deploymentId is used for CSS preloads: <a
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/77210">#77210</a></li>
<li>chore(HMR clients): Fix a bunch of typescript errors by including
the appropriate webpack type declarations: <a
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/77207">#77207</a></li>
<li>Update cache handler interface: <a
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/76687">#76687</a></li>
<li>Turbopack: don't include AMP optimizer in NFT: <a
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/77242">#77242</a></li>
<li>Server actions should not read stale data after calling
<code>revalidate*</code>: <a
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/76885">#76885</a></li>
<li>[dev-overlay] Blur fader for scrollable container: <a
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/77196">#77196</a></li>
<li>Make <code>revalidate*</code> work when followed by a redirect in a
route handler: <a
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/77090">#77090</a></li>
<li>feat: onNavigate for link: <a
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/77209">#77209</a></li>
<li>fix: pass telemetry plugin rspack tests: <a
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/77257">#77257</a></li>
<li>feat(eslint-plugin): add minimal built-in flat presets: <a
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/73873">#73873</a></li>
<li>[perf] skip loading client manifest for static metadata routes: <a
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/77260">#77260</a></li>
<li>Upgrade React from <code>5398b711-20250314</code> to
<code>c69a5fc5-20250318</code>: <a
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-bundle-analyzer/issues/77249">#77249</a></li>
</ul>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="b2ff04995b"><code>b2ff049</code></a>
v15.3.0</li>
<li><a
href="60bfe64295"><code>60bfe64</code></a>
v15.3.0-canary.46</li>
<li><a
href="f71c4a1582"><code>f71c4a1</code></a>
v15.3.0-canary.45</li>
<li><a
href="4451bae75d"><code>4451bae</code></a>
v15.3.0-canary.44</li>
<li><a
href="87d7d8eb7a"><code>87d7d8e</code></a>
v15.3.0-canary.43</li>
<li><a
href="82ab39f801"><code>82ab39f</code></a>
v15.3.0-canary.42</li>
<li><a
href="8f1409d6ce"><code>8f1409d</code></a>
v15.3.0-canary.41</li>
<li><a
href="2139369821"><code>2139369</code></a>
v15.3.0-canary.40</li>
<li><a
href="66514a6bc8"><code>66514a6</code></a>
v15.3.0-canary.39</li>
<li><a
href="fd5669dd41"><code>fd5669d</code></a>
v15.3.0-canary.38</li>
<li>Additional commits viewable in <a
href="https://github.com/vercel/next.js/commits/v15.3.0/packages/next-bundle-analyzer">compare
view</a></li>
</ul>
</details>
<br />


[![Dependabot compatibility
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=@next/bundle-analyzer&package-manager=npm_and_yarn&previous-version=15.2.0&new-version=15.3.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)

Dependabot will resolve any conflicts with this PR as long as you don't
alter it yourself. You can also trigger a rebase manually by commenting
`@dependabot rebase`.

[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits
that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after
your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge
and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating
it. You can achieve the same result by closing it manually
- `@dependabot show <dependency name> ignore conditions` will show all
of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will close this PR and stop
Dependabot creating any more for this major version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop
Dependabot creating any more for this minor version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop
Dependabot creating any more for this dependency (unless you reopen the
PR or upgrade to it yourself)


</details>

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2025-04-10 04:32:16 +00:00
2025-03-01 20:01:38 +00:00
2024-02-27 20:58:28 +01:00
2023-11-27 20:38:30 +01:00
2023-12-13 12:44:04 +01:00

Bracket - Tournament System

build status translations last commit release codecov

Demo · Documentation · Quickstart · GitHub · Releases

Tournament system meant to be easy to use. Bracket is written in async Python (with FastAPI) and Next.js as frontend using the Mantine library.

It has the following features:

  • Supports single elimination, round-robin and swiss formats.
  • Build your tournament structure with multiple stages that can have multiple groups/brackets in them.
  • Drag-and-drop matches to different courts or reschedule them to another start time.
  • Various dashboard pages are available that can be presented to the public, customized with a logo.
  • Create/update teams, and add players to teams.
  • Create multiple clubs, with multiple tournaments per club.
  • Swiss tournaments can be handled dynamically, with automatic scheduling of matches.

Explore the Bracket docs  ▶

Live Demo

A demo is available for free at https://www.bracketapp.nl/demo. The demo lasts for 30 minutes, after which your data will de deleted.

Quickstart

To quickly run bracket to see how it works, clone it and run docker compose up:

git clone git@github.com:evroon/bracket.git
cd bracket
sudo docker compose up -d

This will start the backend and frontend of Bracket, as well as a postgres instance. You should now be able to view bracket at http://localhost:3000. You can log in with the following credentials:

  • Username: test@example.org
  • Password: aeGhoe1ahng2Aezai0Dei6Aih6dieHoo.

To insert dummy rows into the database, run:

sudo docker exec bracket-backend pipenv run ./cli.py create-dev-db

See also the quickstart docs.

Usage

Read the usage guide for how to organize a tournament in Bracket from start to finish.

Configuration

Read the configuration docs for how to configure Bracket.

Bracket's backend is configured using .env files (prod.env for production, dev.env for development etc.). But you can also configure Bracket using environment variables directly, for example by specifying them in the docker-compose.yml.

The frontend doesn't can be configured by environment variables as well, as well as .env files using Next.js' way of loading environment variables.

Running Bracket in production

Read the deployment docs for how to deploy Bracket and run it in production.

Bracket can be run in Docker or by itself (using pipenv and yarn).

Development setup

Read the development docs for how to run Bracket for development.

Prerequisites are yarn, postgresql and pipenv to run the frontend, database and backend.

Translations

Based on your browser settings, your language should be automatically detected and loaded. For now, there's no manual way of choosing a different language.

Supported Languages

To add/refine translations, Crowdin is used. See the docs for more information.

More screenshots

Help

If you're having trouble getting Bracket up and running, or have a question about usage or configuration, feel free to ask. The best place to do this is by creating a Discussion.

Supporting Bracket

If you're using Bracket and would like to help support its development, that would be greatly appreciated!

Several areas that we need a bit of help with at the moment are:

  • Star Bracket on GitHub
  • 🌐 Translating: Help make Bracket available to non-native English speakers by adding your language (via crowdin)
  • 📣 Spread the word by sharing Bracket to help new users discover it
  • 🖥️ Submit a PR to add a new feature, fix a bug, extend/update the docs or something else

See the contribution docs for more information on how to contribute

Contributors

evroon
Erik Vroon
robigan
Null
BachErik
BachErik
djpiper28
Danny Piper
Sevichecc
SevicheCC
nvanheuverzwijn
Nicolas Vanheuverzwijn
IzStriker
IzStriker
babeuh
Raphael Le Goaller

License

Bracket is licensed under AGPL-v3.0.

Please note that any contributions also fall under this license.

See LICENSE

Description
No description provided
Readme AGPL-3.0 29 MiB
Languages
TypeScript 51.1%
Python 47.6%
CSS 0.8%
Dockerfile 0.2%