[Investigation]: Support React 19 #29805

yannbf · 2024-12-04T11:52:12Z

JReinhold · 2024-12-04T12:32:15Z

I don't think we want to upgrade any direct dependencies, as that would be a breaking change, at least if we did it in @storybook/addon-docs or storybook.
We also shouldn't upgrade devDependencies in addons, and especially not addon-kit, because the manager will still be using React 18, so the addons' React version is ignored. Meaning if you're building an addon with React 19 APIs, they won't work as soon as that addon is bundled into the manager at runtime.

ianzone · 2024-12-06T09:19:26Z

it's released now

silverwind · 2024-12-06T10:59:27Z

Would appreciate if these peerDependencies could be updated to support the released version:

storybook/code/renderers/react/package.json

Lines 96 to 97 in 052f6ce

    
           "react": "^16.8.0 || ^17.0.0 || ^18.0.0 || ^19.0.0-beta", 
        
           "react-dom": "^16.8.0 || ^17.0.0 || ^18.0.0 || ^19.0.0-beta",

yannbf · 2024-12-06T13:27:28Z

Hey @silverwind they should support both React 19 prereleases and ^19.0.0. Are you having any problems?

silverwind · 2024-12-06T14:04:38Z

Ah, you are right, it's not an issue. I wasn't aware that prerelease ranges are satisified by release versions. This works with npm for me without getting a peerDependencies error:

{
  "dependencies": {
    "@storybook/react": "8.4.7",
    "react": "19.0.0"
  }
}

kerryj89 · 2024-12-08T22:01:32Z

It seems TOOL and TOOLEXTRA do not work with addon on React 19 and cause the following error which probably doesn't mean much to you, but anywhow:

Uncaught TypeError: Cannot read properties of undefined (reading 'A')
    at Y (manager-bundle.js:7:726)
    at J (manager-bundle.js:12:268)
    at P.jsx (manager-bundle.js:16:979)
    at render (manager-bundle.js:16:1915)
    at Xh (globals-runtime.js:3339:13)
    at Wk (globals-runtime.js:5796:23)
    at Vk (globals-runtime.js:5549:13)
    at Uk (globals-runtime.js:5541:27)
    at Jk (globals-runtime.js:5530:9)
    at Ok (globals-runtime.js:5306:81)

If I downgrade to React 18.x it works as expected.

Reproduction:

// .storybook/manager.tsx

import { addons, types } from '@storybook/manager-api';

addons.register('test', () => {
  addons.add('test', {
    type: types.TOOLEXTRA,
    title: 'test',
    paramKey: 'test',
    render: (props: any) => <>test</>,
  });
});

terrymun · 2024-12-09T13:27:35Z

Can confirm that post-React19 upgrade, everything works with the latest version of Storybook (8.4.7) with the exception of our in-house addons: we have encountered the same error as @kerryj89. Temporarily disabling the addon works for now 👍

stevensacks · 2024-12-10T09:24:20Z

I'm getting this error when I try to launch Storybook with React 19:

@storybook/core v8.4.7

SB_CORE-SERVER_0007 (MainFileEvaluationError): Storybook couldn't evaluate your .storybook/main.ts file.

Original error:
Error: Cannot find module 'esbuild'
Require stack:
- /node_modules/esbuild-register/dist/node.js
- /node_modules/@storybook/core/dist/common/index.cjs
- /node_modules/storybook/dist/proxy.cjs
- /node_modules/storybook/bin/index.cjs
    at Module._resolveFilename (node:internal/modules/cjs/loader:1225:15)
    at Module._load (node:internal/modules/cjs/loader:1051:27)
    at Module.require (node:internal/modules/cjs/loader:1311:19)
    at require (node:internal/modules/helpers:179:18)
    at Object.<anonymous> (/node_modules/esbuild-register/dist/node.js:4653:16)
    at Module._compile (node:internal/modules/cjs/loader:1469:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1548:10)
    at Module.load (node:internal/modules/cjs/loader:1288:32)
    at Module._load (node:internal/modules/cjs/loader:1104:12)
    at Module.require (node:internal/modules/cjs/loader:1311:19)
    at loadMainConfig (./node_modules/@storybook/core/dist/common/index.cjs:17511:11)
    at async buildDevStandalone (./node_modules/@storybook/core/dist/core-server/index.cjs:37134:11)
    at async withTelemetry (./node_modules/@storybook/core/dist/core-server/index.cjs:35757:12)
    at async dev (./node_modules/@storybook/core/dist/cli/bin/index.cjs:2591:3)
    at async s.<anonymous> (./node_modules/@storybook/core/dist/cli/bin/index.cjs:2643:74)

WARN Broken build, fix the error above.
WARN You may need to refresh the browser.

This is my main.ts config:

import type {StorybookConfig} from '@storybook/react-vite';
import {mergeConfig} from 'vite';
import tsconfigPaths from 'vite-tsconfig-paths';

const config: StorybookConfig = {
  addons: [
    '@storybook/addon-links',
    {
      name: '@storybook/addon-essentials',
      options: {
        backgrounds: false,
        grid: false,
        measure: false,
        outline: false,
      },
    },
    '@storybook/addon-interactions',
  ],

  docs: {},

  framework: {
    name: '@storybook/react-vite',
    options: {
      builder: {
        viteConfigPath: '.storybook/vite.config.ts',
      },
    },
  },

  stories: ['../app/**/*.stories.tsx'],

  viteFinal: async (viteConfig) =>
    mergeConfig(viteConfig, {
      plugins: [tsconfigPaths()],
    }),
};

export default config;

yannbf · 2024-12-10T15:15:14Z

Thanks a lot for reporting @kerryj89 @terrymun! I have a PR that will fix that issue: #30003

@stevensacks is React 19 the only variable that makes this fail? I don't see a connection with the error message you provided. Could you please try downgrading to React 18 and see whether it works?

Tottzi · 2024-12-11T13:28:27Z

Hei Yo,
I still face this issue but only with one addon.
// 'storybook-addon-apollo-client',
This does not work, only gives the
Uncaught TypeError: Cannot read properties of undefined (reading 'A')
at Y (manager-bundle.js:7:726)
at J (manager-bundle.js:12:268)
at P.jsx (manager-bundle.js:16:979)
at render (manager-bundle.js:16:1915)
at Xh (globals-runtime.js:3339:13)
at Wk (globals-runtime.js:5796:23)
at Vk (globals-runtime.js:5549:13)
at Uk (globals-runtime.js:5541:27)
at Jk (globals-runtime.js:5530:9)
at Ok (globals-runtime.js:5306:81)

mrginglymus · 2024-12-11T15:11:09Z

There are a number of bundled dependencies in storybook that have incompatible types (mostly due to still using the global JSX namespace); I've started a PR to fix the ones I've spotted so far here: #30031

Sidnioulz · 2024-12-12T08:24:15Z

Thanks for the quick fix @yannbf!

Do you know if this is being backported to 8.4? Or will it be in 8.5+?

gvillo · 2024-12-13T15:48:18Z

+1

yannbf · 2024-12-19T10:40:21Z

Thanks for the quick fix @yannbf!

Do you know if this is being backported to 8.4? Or will it be in 8.5+?

Most of the work we are doing is towards 8.5, which is currently in beta so should be released soon!

savanesoff · 2024-12-23T17:19:25Z

Thanks for the quick fix @yannbf!
Do you know if this is being backported to 8.4? Or will it be in 8.5+?

Most of the work we are doing is towards 8.5, which is currently in beta so should be released soon!

When can we expect this to be avaialble?
This is a magor issue as a lot depends on automation.
Is there a way to run a beta instad?

terrymun · 2024-12-23T17:21:27Z

Thanks for the quick fix @yannbf!
Do you know if this is being backported to 8.4? Or will it be in 8.5+?

Most of the work we are doing is towards 8.5, which is currently in beta so should be released soon!

When can we expect this to be avaialble? This is a magor issue as a lot depends on automation. Is there a way to run a beta instad?

If you're in a pinch you can always give the latest beta release for 8.5.0 a try: https://github.com/storybookjs/storybook/releases/tag/v8.5.0-beta.5

savanesoff · 2024-12-23T17:33:19Z

Thanks for the quick fix @yannbf!
Do you know if this is being backported to 8.4? Or will it be in 8.5+?

Most of the work we are doing is towards 8.5, which is currently in beta so should be released soon!

When can we expect this to be avaialble? This is a magor issue as a lot depends on automation. Is there a way to run a beta instad?

If you're in a pinch you can always give the latest beta release for 8.5.0 a try: https://github.com/storybookjs/storybook/releases/tag/v8.5.0-beta.5

Thanks for speedy reply @terrymun
I've never had the opportunity to install/use unreleased npm registry packages. Any pointers on how I go about using beta?
Thanks again!

terrymun · 2024-12-23T17:36:58Z

@savanesoff 8.5.0-beta.5 has been released: check the releases page or npmjs. You install it just like how you'd install a specific version of any dependency, e.g. if you're npm then it's just npm install [email protected]

savanesoff · 2024-12-23T17:39:26Z

@savanesoff You install it just like how you'd install a specific version of any dependency, e.g. if you're npm then it's just npm install [email protected]

Oh my... LOL. Thanks! 😄
I was searching for it in NPM registry and coulnd't find it, untill I really looked for it 😇 My bad...
You're a saviour!

rrogowski · 2024-12-30T16:40:00Z

Hi there! Will React 19 be supported for Storybook 7? Or is an upgrade to Storybook 8 required?

zeppelinnn · 2025-01-16T19:31:39Z

Hey @Boonstra, thanks for the reply! I added a new commit to bump dependencies to the beta version you mentioned (in the example repo I shared) but i'm still seeing the same error. I believe this is specific to the @storybook/experimental-nextjs-vite framework - if i try to use @storybook/nextjs framework it works fine.
Could you please check again? Thank you!

Right, I also can't get the Storybook in your repository to run without that error coming up.

I've tried to upgrade to [email protected] but still experiencing the same issue (original report)

We're blocked on upgrading to react 19 due to this error - any update on progress or an ETA would be greatly appreciated!

JReinhold · 2025-01-20T09:13:06Z

I've tried to upgrade to [email protected] but still experiencing the same issue (original report)

We're blocked on upgrading to react 19 due to this error - any update on progress or an ETA would be greatly appreciated!

@zeppelinnn the reason you're experiencing this issue, is because you're still using Next.js v14 which doesn't support React 19.

Storybook's Next.js integration (@storybook/nextjs and @storybook/experimental-nextjs-vite) uses the React version that Next.js comes precompiled with, and that version must match what you define in Storybook. In your apps/docs and and apps/web you have "next": "^14.2.3", which only supports React 18. While you also have "react": "19.0.0" there, that doesn't actually make a difference because Next.js ships its own version of React, so you're lying to yourself. You can see this if you do something like this in your Next.js application today:

'use client';
import React from 'react';

function SomeClientComponent() {
  React.useEffect(() => {
    console.log('React version:', React.version);
  }, [])
  return null;
}

You'll get React version: 18.3.0-canary-178c267a4e-20241218 in your console.

There are two ways to solve this:

Install next@^15 as a devDependency in your ui package, and Storybook will use that correctly then. Then the UI package will not depend on your next package being hoisted from apps and docs. Though your UI will now support Next.js 15 and React 19, your app still won't, so you could run into trouble there.

You can see I did this here which made things work again: JReinhold/react-19-storybook-nextjs-vite@19a2a92

As a side note, you should also install react and react-dom as devDependencies to your ui package. Even though they are currently listed as peerDependencies, your UI package is not self-contained, which is a common footgun. It only really works right now because Yarn hoists React from your other packages, but that can easily change in the future. If dependencies changes in your other packages, the UI package will break, which is not something you want. It's best practice to list explicit versions of any peer dependencies you have as dev dependencies.

Upgrade to Next.js v15 in your apps and docs, so they actually come shipped with React 19.

In reality you probably want to do both.

Demianeen · 2025-01-22T13:13:56Z

Did anyone managed to fix type issue with StoryFn type with function declaration? I mean this error:

     ├╴  'StoryComponent' cannot be used as a JSX component.
     │      Its type 'AnnotatedStoryFn<ReactRenderer, ReactRenderer>' is not a valid JSX element type.
     │        Type 'AnnotatedStoryFn<ReactRenderer, ReactRenderer>' is not assignable to type '(props: any) => ReactNode | Promise<ReactNode>'.
     │          Target signature provides too few arguments. Expected 2 or more, but got 1. ts (2786) [7, 5]

It works with arrow function expression with DecoratorFunction<ReactRenderer> but I don't think we can assign type like this to function declaration.

mrginglymus · 2025-01-22T15:47:45Z

Might be fixed by #30031?

akibarika · 2025-01-22T22:43:06Z

Howdy folks, I have run into a few issues with Addon-a11y 8.5.0 and React 19:
 FAIL  src/stories/Components/Foo/Foo.stories.tsx
  ● Foo/Foo › Default › smoke-test

    page.evaluate: Error: Axe is already running. Use `await axe.run()` to wait for the previous run to finish before starting a new run.
I will also note that addon-ally will fail when running npx storybook@next upgrade.
npm ERR! Found: @storybook/[email protected]
npm ERR! node_modules/@storybook/addon-a11y
npm ERR!   dev @storybook/addon-a11y@"^8.6.0-alpha.0" from the root project
Thanks so much for all the work, and have a great day! I can open up an issue on this if required!

I had a same issue, and I don't think it relates with React 19. I think it's the issue with upgrading to 8.5.0

Tottzi · 2025-01-23T07:03:34Z

For me a Next upgrade to v15.1.5 caused that a11y addon fail. It complains for the same Axe thing
Error: Axe is already running. Use await axe.run() to wait for the previous run to finish before starting a new run.

Flambe · 2025-01-23T15:57:15Z

The Axe is already running issue isn't related to React (unless it's related to the storybook UI itself). My app is built in Vue and I've got the same issue after updating to 8.5.*

valentinpalkovic · 2025-01-23T18:52:54Z

@Flambe please open a separate issue. Ideally with an reproduction.

zeppelinnn · 2025-01-23T21:05:45Z

I've tried to upgrade to [email protected] but still experiencing the same issue (original report)
We're blocked on upgrading to react 19 due to this error - any update on progress or an ETA would be greatly appreciated!

@zeppelinnn the reason you're experiencing this issue, is because you're still using Next.js v14 which doesn't support React 19.

Storybook's Next.js integration (@storybook/nextjs and @storybook/experimental-nextjs-vite) uses the React version that Next.js comes precompiled with, and that version must match what you define in Storybook. In your apps/docs and and apps/web you have "next": "^14.2.3", which only supports React 18. While you also have "react": "19.0.0" there, that doesn't actually make a difference because Next.js ships its own version of React, so you're lying to yourself. You can see this if you do something like this in your Next.js application today:

'use client';
import React from 'react';

function SomeClientComponent() {
React.useEffect(() => {
console.log('React version:', React.version);
}, [])
return null;
}
You'll get React version: 18.3.0-canary-178c267a4e-20241218 in your console.

There are two ways to solve this:

Install next@^15 as a devDependency in your ui package, and Storybook will use that correctly then. Then the UI package will not depend on your next package being hoisted from apps and docs. Though your UI will now support Next.js 15 and React 19, your app still won't, so you could run into trouble there.

You can see I did this here which made things work again: JReinhold/react-19-storybook-nextjs-vite@19a2a92

As a side note, you should also install react and react-dom as devDependencies to your ui package. Even though they are currently listed as peerDependencies, your UI package is not self-contained, which is a common footgun. It only really works right now because Yarn hoists React from your other packages, but that can easily change in the future. If dependencies changes in your other packages, the UI package will break, which is not something you want. It's best practice to list explicit versions of any peer dependencies you have as dev dependencies.

Upgrade to Next.js v15 in your apps and docs, so they actually come shipped with React 19.

In reality you probably want to do both.

that worked, thank you for the help!

akibarika · 2025-01-23T21:10:22Z

I have also posted a discussion (#30351) with my fix. The root cause of mine is multi-worker

Eyad-A · 2025-01-24T23:06:35Z

Is Storybook 7 suppose to work with React 19? I recently upgraded Next.js 14 => 15 and React 18 => 19, and that broke Storybook for us. When I launch storybook, I get react_dom__WEBPACK_IMPORTED_MODULE_0__.unmountComponentAtNode is not a function.

According to react doc, unmountComponentAtNode has been deprecated.

The above happens with @storybook/nextjs 7.0.22. If I upgrade it to 8.5.1, I get this error instead:
SB_CORE-SERVER_0002 (CriticalPresetLoadError): Storybook failed to load the following preset: @storybook/nextjs/preset.

Current setup:

"storybook": "^7.0.22",
"typescript": "^5.1.6",
"react": "^19.0.0",
"react-dom": "^19.0.0",
"next": "^15.1.6",
"@storybook/nextjs": "^7.0.22",
"@storybook/react": "^8.4.7",

terrymun · 2025-01-24T23:17:04Z

@Eyad-A Storybook 7 has been released quite awhile ago and I do not expect it to be updated to support React 19. You need to upgrade to Storybook 8.5+

valentinpalkovic · 2025-01-26T10:37:49Z

That’s correct. We only patch back critical security fixes to the previous major version.

mathiaslaramee · 2025-01-29T08:23:42Z

Is it in the plans to also upgrade

storybook/code/addons/docs/package.json

Lines 104 to 105 in 052f6ce

    
           "react": "^16.8.0 || ^17.0.0 || ^18.0.0", 
        
           "react-dom": "^16.8.0 || ^17.0.0 || ^18.0.0",

?

valentinpalkovic · 2025-01-29T17:07:34Z

Yes! It seems to be forgotten. Do you want to open a PR?

Storybook has decided to replace react-confetti by neoconfetti, this change is pending. But, the react-confetti authors have updated the react 19 dependency problem. Temporary, we can have react-confetti updated through package-lock until Storybook publishes the new change. alampros/react-confetti#159 (comment) storybookjs/storybook#29805

maddyahmad · 2025-01-31T15:42:10Z

Hi, I have updated react to v19, and after that I am getting an error. I have also updated to v8.5.2, but nothing works.

My component is
import { SnackbarProvider } from "@/store/SnackbarContext";
import { StoryFn } from "@storybook/react";
import { render } from "@testing-library/react";
import { merge } from "lodash";
import React, { createContext, useContext } from "react";
import { Theme, defaultThemeConstants } from '../utils/theme';

interface ThemeProviderProps {
theme?: Theme
children?: React.ReactNode
}

const defaultTheme: Theme = { ...defaultThemeConstants }

const ThemeContext = createContext<Theme | undefined>(undefined)

export const ThemeProvider: React.FC = (props) => {
return (
<ThemeContext.Provider value={merge(defaultTheme, props.theme)}>
{props.children}
</ThemeContext.Provider>
)
}

export const withThemeProvider = (Story: StoryFn) => (

);

After upgrading react to v19, I am getting an error in withThemeProvider
'Story' cannot be used as a JSX component.
Its type 'AnnotatedStoryFn<ReactRenderer, Args>' is not a valid JSX element type.
Type 'AnnotatedStoryFn<ReactRenderer, Args>' is not assignable to type '(props: any) => ReactNode'.
Target signature provides too few arguments. Expected 2 or more, but got 1.ts(2786)
(parameter) Story: AnnotatedStoryFn<ReactRenderer, Args>.

For you reference, this is an example of how I am using it
import { withThemeProvider } from '@/theme/ThemeProvider';
import { Meta, StoryObj } from '@storybook/react';

const meta: Meta = {
title: 'title',
component: Component,
parameters: {
layout: 'centered',
actions: { argTypesRegex: '^on.*' },
docs: {
description: {
component: My doc //
}
}
},
tags: ["autodocs"],
};

export default meta;

type Story = StoryObj;

export const Usage: Story = {
args: {
},
render: (args) => (
My Component //
),
decorators: [withThemeProvider],
};

mathiaslaramee · 2025-02-04T08:43:42Z

Yes! It seems to be forgotten. Do you want to open a PR?

I'm trying but struggling a bit since this is a dependencies update and not just a peerDependencies update. Giving me some troubles when trying to install the dependencies after I specify the new react version.

@JReinhold also mentioned in his first reply that changing this specifically in @storybook/addon-docs is a breaking change.
Any thoughts? @valentinpalkovic

mrginglymus · 2025-02-04T11:21:54Z

@maddyahmad 8.6.0-alpha.3 might fix those problems; that contains a lot of type fixes.

mellm0 · 2025-02-13T04:39:28Z

Hi!

It seems we are still getting this issue with the latest Storybook. From debugging, it seems to be when we import a component from an external library inside the addon.

import { LiveProvider } from 'react-live';
 <LiveProvider code={state.code} theme={theme}></LiveProvider>

The error I am seeing is similar to the ones posted previously

globals-runtime.js:2661 Uncaught TypeError: Cannot read properties of undefined (reading 'A')
    at p (manager-bundle.js:7:744)
    at k (manager-bundle.js:12:280)
    at Co.jsx (manager-bundle.js:16:980)
    at y2 (manager-bundle.js:160:1924)
    at Xh (globals-runtime.js:3339:13)
    at Wk (globals-runtime.js:5796:23)
    at Vk (globals-runtime.js:5549:13)
    at Uk (globals-runtime.js:5541:27)
    at Jk (globals-runtime.js:5530:9)
    at Ok (globals-runtime.js:5306:81)

Unfortunately I am not sure how to un-minify the manager-bundle.js to investigate more.

shilman · 2025-02-13T08:41:30Z

Closing and locking this issue since it has become a bit of a dumping ground.

If you have a specific React 19 issue, please file it separately with a reproduction and we'll be happy to take a look!

yannbf added bug dependencies react labels Dec 4, 2024

yannbf added this to Core Team Projects Dec 4, 2024

yannbf mentioned this issue Dec 6, 2024

Support React 19 alampros/react-confetti#159

Closed

yannbf mentioned this issue Dec 10, 2024

Core: Fix bundling of React #30003

Merged

8 tasks

castastrophe mentioned this issue Dec 10, 2024

chore(deps-dev): bump react from 18.3.1 to 19.0.0 adobe/spectrum-css#3436

Closed

JesusTheHun mentioned this issue Dec 11, 2024

Support React 19 JesusTheHun/storybook-addon-remix-react-router#83

Closed

Sidnioulz mentioned this issue Dec 12, 2024

Bug: React 19 crash with Storybook 8.4 Sidnioulz/storybook-addon-tag-badges#37

Closed

josiahayres mentioned this issue Dec 15, 2024

React 19 support josiahayres/storybook-addon-mantine#12

Closed

devinvillarosa mentioned this issue Jan 20, 2025

[UI v2] fix: Fix Storybook decorators typings PrefectHQ/prefect#16781

Merged

4 tasks

certainlyakey mentioned this issue Jan 20, 2025

Most of the story tests failing when used with storybook/[email protected] chanzuckerberg/axe-storybook-testing#103

Closed

lifeiscontent mentioned this issue Jan 23, 2025

Storybook crashes client side when using storybook-addon-apollo-client with React 19 lifeiscontent/storybook-addon-apollo-client#124

Closed

akibarika mentioned this issue Jan 27, 2025

[Bug]: Regression in test-storybook after upgrading to 8.5.x: Axe is already running error #30385

Closed

shilman added this to the 9.0 milestone Jan 29, 2025

minami-minami mentioned this issue Feb 6, 2025

feat: support react 19 kodai3/storybook-addon-launchdarkly#15

Merged

shilman closed this as completed Feb 13, 2025

github-project-automation bot moved this to Done in Core Team Projects Feb 13, 2025

storybookjs locked as off-topic and limited conversation to collaborators Feb 13, 2025

[Investigation]: Support React 19 #29805

[Investigation]: Support React 19 #29805

Comments

yannbf commented Dec 4, 2024 • edited Loading

Describe the bug

To users:

JReinhold commented Dec 4, 2024 • edited Loading

ianzone commented Dec 6, 2024

silverwind commented Dec 6, 2024 • edited Loading

yannbf commented Dec 6, 2024 • edited Loading

silverwind commented Dec 6, 2024 • edited Loading

kerryj89 commented Dec 8, 2024 • edited Loading

terrymun commented Dec 9, 2024

stevensacks commented Dec 10, 2024 • edited Loading

yannbf commented Dec 10, 2024

Tottzi commented Dec 11, 2024

mrginglymus commented Dec 11, 2024

Sidnioulz commented Dec 12, 2024

gvillo commented Dec 13, 2024

yannbf commented Dec 19, 2024

savanesoff commented Dec 23, 2024

terrymun commented Dec 23, 2024

savanesoff commented Dec 23, 2024 • edited Loading

terrymun commented Dec 23, 2024 • edited Loading

savanesoff commented Dec 23, 2024

rrogowski commented Dec 30, 2024

zeppelinnn commented Jan 16, 2025

JReinhold commented Jan 20, 2025 • edited Loading

Demianeen commented Jan 22, 2025

mrginglymus commented Jan 22, 2025

akibarika commented Jan 22, 2025

Tottzi commented Jan 23, 2025

Flambe commented Jan 23, 2025

valentinpalkovic commented Jan 23, 2025

zeppelinnn commented Jan 23, 2025

akibarika commented Jan 23, 2025

Eyad-A commented Jan 24, 2025

terrymun commented Jan 24, 2025

valentinpalkovic commented Jan 26, 2025

mathiaslaramee commented Jan 29, 2025

valentinpalkovic commented Jan 29, 2025

maddyahmad commented Jan 31, 2025 • edited Loading

mathiaslaramee commented Feb 4, 2025 • edited Loading

mrginglymus commented Feb 4, 2025

mellm0 commented Feb 13, 2025 • edited Loading

shilman commented Feb 13, 2025

yannbf commented Dec 4, 2024 •

edited

Loading

JReinhold commented Dec 4, 2024 •

edited

Loading

silverwind commented Dec 6, 2024 •

edited

Loading

yannbf commented Dec 6, 2024 •

edited

Loading

silverwind commented Dec 6, 2024 •

edited

Loading

kerryj89 commented Dec 8, 2024 •

edited

Loading

stevensacks commented Dec 10, 2024 •

edited

Loading

savanesoff commented Dec 23, 2024 •

edited

Loading

terrymun commented Dec 23, 2024 •

edited

Loading

JReinhold commented Jan 20, 2025 •

edited

Loading

maddyahmad commented Jan 31, 2025 •

edited

Loading

mathiaslaramee commented Feb 4, 2025 •

edited

Loading

mellm0 commented Feb 13, 2025 •

edited

Loading