Watchpack Error (initial scan): Error: ENOTDIR: not a directory in v3 #3322

hrougier · 2024-09-29T18:33:08Z

Describe the bug

Tried to use nextra 3.0.1 and got the following issue (reproduced in codesandbox).

To Reproduce

Go to codesandbox.io
Click on the Start Dev Server terminal
See error and broken UI

Watchpack Error (initial scan): Error: ENOTDIR: not a directory, scandir '/project/sandbox/node_modules/next/dist/pages/_app.js'
 ⚠ ./node_modules/@typescript/vfs/dist/vfs.esm.js
Critical dependency: the request of a dependency is an expression

Import trace for requested module:
./node_modules/@typescript/vfs/dist/vfs.esm.js
./node_modules/twoslash/dist/index.mjs
./node_modules/@shikijs/twoslash/dist/index.mjs
./node_modules/nextra/dist/server/compile.js
./node_modules/nextra/dist/client/components/playground.js
./node_modules/nextra/dist/client/components/index.js
./node_modules/nextra-theme-docs/dist/index.js

Expected behavior

No error in terminal and a working nextra site.

Additional context

Setup from the Getting Started tutorial with the following dependencies versions

{
  "next": "14.2.13",
  "nextra": "3.0.1",
  "nextra-theme-docs": "3.0.1",
  "react": "18.3.1",
  "react-dom": "18.3.1"
}

The text was updated successfully, but these errors were encountered:

marcklingen · 2024-09-29T23:12:47Z

having the same issue, did you find a workaround to fix this?

hrougier · 2024-09-30T16:16:49Z

having the same issue, did you find a workaround to fix this?

Not yet, unlike the minimal codepen reproduction it doesn't work at all on my existing nextra site and only displays an Internal Server Error page instead of a broken UI, with the following stack traces:

 ○ Compiling / ...
Watchpack Error (initial scan): Error: ENOTDIR: not a directory, scandir '/path/to/node_modules/next/dist/pages/_app.js'
 ⨯ ../node_modules/typescript/lib/typescript.js:43173:24
Module not found: Can't resolve 'module'

https://nextjs.org/docs/messages/module-not-found

Import trace for requested module:
../node_modules/twoslash/dist/index.mjs
../node_modules/@shikijs/twoslash/dist/index.mjs
../node_modules/nextra/dist/server/compile.js
../node_modules/nextra/dist/client/components/playground.js
../node_modules/nextra/dist/client/components/index.js
../node_modules/nextra-theme-docs/dist/index.js
../node_modules/next/dist/esm/pages/_app.js

Watchpack Error (initial scan): Error: ENOTDIR: not a directory, scandir '/path/to/node_modules/next/dist/pages/_app.js'
 ⨯ ../node_modules/typescript/lib/typescript.js:43173:24
Module not found: Can't resolve 'module'

https://nextjs.org/docs/messages/module-not-found

Import trace for requested module:
../node_modules/twoslash/dist/index.mjs
../node_modules/@shikijs/twoslash/dist/index.mjs
../node_modules/nextra/dist/server/compile.js
../node_modules/nextra/dist/client/components/playground.js
../node_modules/nextra/dist/client/components/index.js
../node_modules/nextra-theme-docs/dist/index.js
../node_modules/next/dist/esm/pages/_app.js
 ⨯ Error: ENOENT: no such file or directory, open '/path/to/.next/fallback-build-manifest.json'
    at readFileSync (node:fs:448:20)
    at loadManifest (/path/to/node_modules/next/dist/server/load-manifest.js:36:52)
    at loadManifestWithRetries (/path/to/node_modules/next/dist/server/load-components.js:40:51)
    at async loadDefaultErrorComponentsImpl (/path/to/node_modules/next/dist/server/load-default-error-components.js:30:24)
    at async DevServer.getFallbackErrorComponents (/path/to/node_modules/next/dist/server/dev/next-dev-server.js:594:16)
    at async DevServer.renderErrorToResponseImpl (/path/to/node_modules/next/dist/server/base-server.js:2180:40)
    at async DevServer.renderToResponseImpl (/path/to/node_modules/next/dist/server/base-server.js:1996:30)
    at async DevServer.pipeImpl (/path/to/node_modules/next/dist/server/base-server.js:914:25)
    at async NextNodeServer.handleCatchallRenderRequest (/path/to/node_modules/next/dist/server/next-server.js:272:17)
    at async DevServer.handleRequestImpl (/path/to/node_modules/next/dist/server/base-server.js:810:17)
    at async /path/to/node_modules/next/dist/server/dev/next-dev-server.js:339:20
    at async Span.traceAsyncFn (/path/to/node_modules/next/dist/trace/trace.js:154:20)
    at async DevServer.handleRequest (/path/to/node_modules/next/dist/server/dev/next-dev-server.js:336:24)
    at async invokeRender (/path/to/node_modules/next/dist/server/lib/router-server.js:173:21)
    at async handleRequest (/path/to/node_modules/next/dist/server/lib/router-server.js:350:24) {
  errno: -2,
  code: 'ENOENT',
  syscall: 'open',
  path: '/path/to/.next/fallback-build-manifest.json'
}

nshiab · 2024-09-30T17:33:12Z

Same problem when I followed the steps here: https://nextra.site/docs/docs-theme/start

dimaMachina · 2024-09-30T20:01:23Z

try 3.0.2 where the warning Watchpack Error (initial scan): Error: ENOTDIR: not a directory, scandir is gone and styles seems correctly applied

marcklingen · 2024-09-30T20:02:33Z

Thanks for the quick fix @dimaMachina 🙏

did this resolve the issue for you @hrougier? I am still getting these errors on 3.0.2 (build and dev server):

./node_modules/.pnpm/@[email protected][email protected]/node_modules/@typescript/vfs/dist/vfs.esm.js
Critical dependency: the request of a dependency is an expression

Import trace for requested module:
./node_modules/.pnpm/@[email protected][email protected]/node_modules/@typescript/vfs/dist/vfs.esm.js
./node_modules/.pnpm/[email protected][email protected]/node_modules/twoslash/dist/index.mjs
./node_modules/.pnpm/@[email protected][email protected]/node_modules/@shikijs/twoslash/dist/index.mjs
./node_modules/.pnpm/[email protected]_@[email protected][email protected]_@[email protected][email protected]_react_kdvvi7vlst7dzlxuv6gvakrxwi/node_modules/nextra/dist/server/compile.js
./node_modules/.pnpm/[email protected]_@[email protected][email protected]_@[email protected][email protected]_react_kdvvi7vlst7dzlxuv6gvakrxwi/node_modules/nextra/dist/client/components/playground.js
./node_modules/.pnpm/[email protected]_@[email protected][email protected]_@[email protected][email protected]_react_kdvvi7vlst7dzlxuv6gvakrxwi/node_modules/nextra/dist/client/components/index.js

./node_modules/.pnpm/@[email protected][email protected]/node_modules/@typescript/vfs/dist/vfs.cjs.production.min.js
Critical dependency: the request of a dependency is an expression

Import trace for requested module:
./node_modules/.pnpm/@[email protected][email protected]/node_modules/@typescript/vfs/dist/vfs.cjs.production.min.js
./node_modules/.pnpm/@[email protected][email protected]/node_modules/@typescript/vfs/dist/index.js
./node_modules/.pnpm/[email protected][email protected]/node_modules/twoslash/dist/index.mjs
./node_modules/.pnpm/@[email protected][email protected]/node_modules/@shikijs/twoslash/dist/index.mjs
./node_modules/.pnpm/[email protected]_@[email protected][email protected]_@[email protected][email protected]_react_kdvvi7vlst7dzlxuv6gvakrxwi/node_modules/nextra/dist/server/compile.js
./node_modules/.pnpm/[email protected]_@[email protected][email protected]_@[email protected][email protected]_react_kdvvi7vlst7dzlxuv6gvakrxwi/node_modules/nextra/dist/client/components/playground.js
./node_modules/.pnpm/[email protected]_@[email protected][email protected]_@[email protected][email protected]_react_kdvvi7vlst7dzlxuv6gvakrxwi/node_modules/nextra/dist/client/components/index.js
./pages/blog/qa-chatbot-for-langfuse-docs.mdx

package.json

dimaMachina · 2024-09-30T20:11:42Z

this is upstream, false positive warnings from twoslash package https://nextra.site/docs/guide/advanced/twoslash-support

I reported it already microsoft/TypeScript-Website#3022

maybe we should disable twoslash by default

hrougier · 2024-09-30T20:24:14Z

@marcklingen Yes it did resolve the Watchpack warning but I still get these 2:

 ⨯ ../node_modules/typescript/lib/typescript.js:43173:24
Module not found: Can't resolve 'module'
... (see previous comment)

and

Error: ENOENT: no such file or directory, open '/path/to/.next/fallback-build-manifest.json'
... (see previous comment)

Still experimenting to see what might be causing these errors!

@dimaMachina I was about to ask you that, maybe it is possible to make twoslash optional through some configuration option?

marcklingen · 2024-09-30T20:51:28Z

maybe we should disable twoslash by default

Not sure if worth the complexity but would be a good option for me as I do not need twoslash support

Chirag-kalsariya · 2024-09-30T20:52:31Z

"dependencies": {
    "next": "^14.2.13",
    "nextra": "3.0.2",
    "nextra-theme-docs": "3.0.2",
    "react": "^18.3.1",
    "react-dom": "^18.3.1"
},
"devDependencies": {
    "@types/react": "^18.3.10",
    "@types/node": "22.7.4",
    "typescript": "^5.6.2"
}

I used 3.0.2, and still getting broken page with no css style. and Critical dependency error

○ Compiling / ...
 ⚠ ./node_modules/@typescript/vfs/dist/vfs.esm.js
Critical dependency: the request of a dependency is an expression

Import trace for requested module:
./node_modules/@typescript/vfs/dist/vfs.esm.js
./node_modules/twoslash/dist/index.mjs
./node_modules/@shikijs/twoslash/dist/index.mjs
./node_modules/nextra/dist/server/compile.js
./node_modules/nextra/dist/client/components/playground.js
./node_modules/nextra/dist/client/components/index.js
./node_modules/nextra-theme-docs/dist/index.js
 GET / 200 in 51967ms

hrougier · 2024-09-30T20:57:13Z

The error about the .next/fallback-build-manifest.json seems to happen because of the failing twoslash module import, I can confirm I got v3.0.2 to work by removing the following import and its usages:

import { rendererRich, transformerTwoslash } from "@shikijs/twoslash";

from node_modules/nextra/dist/server/compile.js (.next folder must be deleted and next dev server started again).

Now I have other issues with soft navigation when using the type: 'page' in _meta.js but that's another topic.

marcklingen · 2024-09-30T21:04:33Z

I used 3.0.2, and still getting broken page with no css style. and Critical dependency error

In my case this does not affect css, page works completely fine (we use nextra + tailwind), just breaks dev-server navigation (need to try to navigate to each page twice before it actually works) and produces these logs. Production deployment looks completely fine

Chirag-kalsariya · 2024-09-30T21:14:25Z

The error about the .next/fallback-build-manifest.json seems to happen because of the failing twoslash module import, I can confirm I got v3.0.2 to work by removing the following import and its usages:
import { rendererRich, transformerTwoslash } from "@shikijs/twoslash";
from node_modules/nextra/dist/server/compile.js (.next folder must be deleted and next dev server started again).

Now I have other issues with soft navigation when using the type: 'page' in _meta.js but that's another topic.

I try it, and work but In my case when directly go to http://localhost:3000 CSS is not working, but when I navigate pages everything is working fine. I am using npm not pnpm.

Chirag-kalsariya · 2024-09-30T21:19:58Z

I used 3.0.2, and still getting broken page with no css style. and Critical dependency error

In my case this does not affect css, page works completely fine, just breaks dev-server navigation (need to try to navigate to each page twice before it actually works) and produces these logs. Production deployment looks completely fine

Yes, Production deployment looks completely fine. with version 3.0.2. without changing anything in node_modules/nextra/dist/server/compile.js

dimaMachina · 2024-10-02T18:34:32Z

I found how to fix warnings from @typescript/vfs without waiting for upstream fix 🎉

#3330

dimaMachina · 2024-10-02T18:43:44Z

So now it left only warnings from unified

nextra:dev: "Value" is imported from external module "vfile" but never used in "node_modules/unified/index.d.ts".
nextra:dev: "CompileResults" is imported from external module "./lib/index.js" but never used in "node_modules/unified/index.d.ts".

Reported in unifiedjs/unified#250

danielkleinstein · 2024-10-09T11:25:50Z

Can we reopen this issue? I still get the warning after upgrading to 3.0.7 - and it looks like other people are too

danielkleinstein · 2024-10-09T11:27:38Z

For now I'm working with this workaround in next.config.mjs:

import nextra from "nextra";

const withNextra = nextra({
  theme: "nextra-theme-docs",
  themeConfig: "./theme.config.tsx",
});

export default withNextra({
  webpack: (config) => {
    config.module = {
      ...config.module,
      exprContextCritical: false,
    };

    return config;
  },
});

But this isn't ideal.

dimaMachina · 2024-10-09T11:29:04Z

Please share reproduction repo

danielkleinstein · 2024-10-09T11:58:27Z

I can't share the repo itself as it's private - but I tried creating a new repo from scratch as per the instructions here - https://nextra.site/docs/docs-theme/start

I followed the instructions to the letter, but when I ran pnpm run dev:

I got the lack-of-CSS problem mentioned above
I then ran rm -rf .next and pnpm run dev, and the CSS problem resolved itself, but I got this warning:

Module not found: Can't resolve 'source-map-support' in '/Users/danielkleinstein/tmp/nextra/node_modules/.pnpm/[email protected]/node_modules/typescript/lib'

Import trace for requested module:
./node_modules/.pnpm/[email protected]/node_modules/typescript/lib/typescript.js
./node_modules/.pnpm/[email protected][email protected]/node_modules/twoslash/dist/index.mjs
./node_modules/.pnpm/@[email protected][email protected]/node_modules/@shikijs/twoslash/dist/index.mjs
./node_modules/.pnpm/[email protected]_@[email protected][email protected][email protected][email protected][email protected]__r_lgnh5dmjpho45ld7y5jnnfcyza/node_modules/nextra/dist/server/compile.js
./node_modules/.pnpm/[email protected]_@[email protected][email protected][email protected][email protected][email protected]__r_lgnh5dmjpho45ld7y5jnnfcyza/node_modules/nextra/dist/client/components/playground.js
./node_modules/.pnpm/[email protected]_@[email protected][email protected][email protected][email protected][email protected]__r_lgnh5dmjpho45ld7y5jnnfcyza/node_modules/nextra/dist/client/components/index.js
./node_modules/.pnpm/[email protected][email protected][email protected][email protected][email protected][email protected]._asslf2kagsatjgjntmqd5n4xfe/node_modules/nextra-theme-docs/dist/index.js
 GET / 200 in 13593ms

Though this seems to be a separate warning. Couldn't immediately reproduce this issue's warning on the clean repo, sorry

hrougier · 2024-10-09T15:51:53Z

@danielkleinstein I still have the same issue with 3.0.7, my fix for now is to use the patch command of pnpm/yarn/bun to comment the twoslash import and usage from nextra/dist/server/compile.js:

pnpm patch nextra

Comment the twoslash import and usage from dist/server/compile.js

// import { rendererRich, transformerTwoslash } from "@shikijs/twoslash";

// ...

transformers: isRemoteContent ? [] : [
 // transformerTwoslash({
 //   renderer: rendererRich(),
 //   explicitTrigger: true
 // })
],

Commit the patch

pnpm patch-commit <path>

Not ideal but I don't need twoslash and it cannot be disabled right now.

danielkleinstein · 2024-10-10T08:16:27Z

@hrougier Wow, wasn't familiar with pnpm patch - thanks, this helped a lot!

Removing the twoslash dependency explicitly seems to solve a lot of random issues (including the missing CSS issue).

dimaMachina · 2024-10-11T16:56:44Z

For anyone still having this issue - Please provide a working reproduction.

Without reproduction, I cannot help with fixing this issue

mnahkies · 2024-10-11T17:46:25Z

I'm seeing this on this branch mnahkies/openapi-code-generator#251

(example CI failure https://github.com/mnahkies/openapi-code-generator/actions/runs/11296901214/job/31422680072)

# git clone
yarn
cd ./packages/documentation
yarn build # or yarn dev

I can try putting up a minimal reproduction tomorrow if that's better.

dimaMachina · 2024-10-11T18:15:18Z

@mnahkies you have a different error, which must be fixed with https://github.com/shuding/nextra/releases/tag/nextra%403.0.9

Can you confirm that it was fixed with new release?

mnahkies · 2024-10-11T18:51:29Z

@dimaMachina unfortunately that build I linked was from the commit bumping to 3.0.9 - so still an issue for me

It's a fairly vanilla typescript nextra project using nextra-theme-docs

Also sorry I thought this was the same underlying issue as the ENOTDIR thing as I was seeing that at some point alongside the error

dimaMachina · 2024-10-11T20:00:08Z

@mnahkies can't reproduce locally

cloned your repo
updated nextra/nextra-theme-docs to 3.0.9
removed next-seo from theme.config
refactored _meta.json to _meta.js
didn't receive any errors

 ✘ dmytro@192  ~/Desktop/repros/openapi-code-generator   main ±  yarn workspace @nahkies/openapi-code-generator-documentation build
yarn workspace v1.22.17
yarn run v1.22.17
$ next build
 ⚠ Specified "redirects" will not automatically work with "output: export". See more info here: https://nextjs.org/docs/messages/export-no-custom-routes
 ⚠ Specified "redirects" will not automatically work with "output: export". See more info here: https://nextjs.org/docs/messages/export-no-custom-routes
  ▲ Next.js 14.2.13

 ✓ Linting and checking validity of types    
   Creating an optimized production build ...
 ✓ Compiled successfully
 ✓ Collecting page data    
 ✓ Generating static pages (15/15)
 ✓ Collecting build traces    
 ⚠ rewrites, redirects, and headers are not applied when exporting your application, detected (redirects). See more info here: https://nextjs.org/docs/messages/export-no-custom-routes
 ✓ Finalizing page optimization    

Route (pages)                                    Size     First Load JS
┌ ○ /                                            941 B           150 kB
├   /_app                                        0 B             145 kB
├ ● /_meta                                       241 B           145 kB
├ ○ /404                                         1.04 kB         150 kB
├ ○ /getting-started/quick-start                 6.25 kB         155 kB
├ ● /guides/_meta                                247 B           145 kB
├ ○ /guides/client-templates/typescript-angular  7.34 kB         157 kB
├ ○ /guides/client-templates/typescript-axios    7.48 kB         157 kB
├ ○ /guides/client-templates/typescript-fetch    7.58 kB         157 kB
├ ○ /guides/concepts/extract-inline-schemas      4.02 kB         153 kB
├ ○ /guides/server-templates/typescript-koa      8.53 kB         158 kB
├ ○ /overview/about                              3.95 kB         153 kB
├ ○ /overview/compatibility                      6.81 kB         156 kB
├ ○ /reference/architecture                      3.24 kB         152 kB
└ ○ /reference/cli-options                       5.44 kB         155 kB
+ First Load JS shared by all                    156 kB
  ├ chunks/framework-e82a91356956e6c8.js         44.8 kB
  ├ chunks/main-412a9cd0a25897ae.js              32.3 kB
  ├ chunks/pages/_app-bccdaae3d42700a4.js        65.8 kB
  ├ css/a509b722c23f67c3.css                     11.1 kB
  └ other shared chunks (total)                  1.75 kB

○  (Static)  prerendered as static content
●  (SSG)     prerendered as static HTML (uses getStaticProps)

✨  Done in 23.52s.
✨  Done in 23.80s.

same result when I am on renovate/all branch

mnahkies · 2024-10-11T20:44:32Z

I'm thoroughly confused then. More info:

$ yarn -v
4.5.0
$ node -v
v22.9.0
$ uname -r
6.10.12-200.fc40.x86_64

(I can see that your snippet above appears to be using yarn v1.22.17 although that should be irrelevant since I get the error if I invoke next build directly)

The only way I've been able to make it work so far is unconditionally returning [] from the getTransformers function modified in f9cc160

I put some logging in that function, and found it was getting called like so:

{"windowDefined":false,"isRemoteContent":false,"outputFormat":"program"}

From: https://github.com/shuding/nextra/blob/main/packages/nextra/src/server/loader.ts#L162-L169

mnahkies · 2024-10-11T21:12:13Z

I'm wondering if this might somehow be a Linux specific thing, here's a minimal reproduction using docker: https://github.com/mnahkies/nextra-bug-3322-reproduction

dimaMachina · 2024-10-11T21:39:13Z

@mnahkies Oops, yep, I missed to enable corepack, I can reproduce now!

dimaMachina · 2024-10-11T22:45:16Z

@mnahkies thanks for the contribution, fix is coming!

mnahkies · 2024-10-12T10:21:29Z

@dimaMachina can confirm - that fixed it for me, thanks for such a quick turnaround!

hrougier added the bug Something isn't working label Sep 29, 2024

dimaMachina mentioned this issue Sep 30, 2024

remove warning Watchpack Error (initial scan): Error: ENOTDIR: not a directory, scandir 'path-to-your-node_modules/next/dist/pages/_app.js' #3328

Merged

dimaMachina closed this as completed in #3328 Sep 30, 2024

dimaMachina reopened this Sep 30, 2024

dimaMachina mentioned this issue Oct 2, 2024

remove Critical dependency: the request of a dependency is an expression warnings #3330

Merged

dimaMachina closed this as completed Oct 2, 2024

dimaMachina reopened this Oct 9, 2024

dimaMachina mentioned this issue Oct 11, 2024

another attempt to fix Module not found: Can't resolve 'module' #3349

Merged

dimaMachina closed this as completed Oct 11, 2024

mnahkies added a commit to mnahkies/openapi-code-generator that referenced this issue Oct 12, 2024

fix: bump nextra for shuding/nextra#3322 fix

b6c998b

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Watchpack Error (initial scan): Error: ENOTDIR: not a directory in v3 #3322

Watchpack Error (initial scan): Error: ENOTDIR: not a directory in v3 #3322

hrougier commented Sep 29, 2024

marcklingen commented Sep 29, 2024

hrougier commented Sep 30, 2024

nshiab commented Sep 30, 2024

dimaMachina commented Sep 30, 2024

marcklingen commented Sep 30, 2024 •

edited

Loading

dimaMachina commented Sep 30, 2024

hrougier commented Sep 30, 2024 •

edited

Loading

marcklingen commented Sep 30, 2024

Chirag-kalsariya commented Sep 30, 2024

hrougier commented Sep 30, 2024

marcklingen commented Sep 30, 2024 •

edited

Loading

Chirag-kalsariya commented Sep 30, 2024

Chirag-kalsariya commented Sep 30, 2024

dimaMachina commented Oct 2, 2024 •

edited

Loading

dimaMachina commented Oct 2, 2024

danielkleinstein commented Oct 9, 2024

danielkleinstein commented Oct 9, 2024

dimaMachina commented Oct 9, 2024

danielkleinstein commented Oct 9, 2024 •

edited

Loading

hrougier commented Oct 9, 2024 •

edited

Loading

danielkleinstein commented Oct 10, 2024 •

edited

Loading

dimaMachina commented Oct 11, 2024

mnahkies commented Oct 11, 2024

dimaMachina commented Oct 11, 2024

mnahkies commented Oct 11, 2024

dimaMachina commented Oct 11, 2024 •

edited

Loading

mnahkies commented Oct 11, 2024

mnahkies commented Oct 11, 2024

dimaMachina commented Oct 11, 2024

dimaMachina commented Oct 11, 2024

mnahkies commented Oct 12, 2024

Watchpack Error (initial scan): Error: ENOTDIR: not a directory in v3 #3322

Watchpack Error (initial scan): Error: ENOTDIR: not a directory in v3 #3322

Comments

hrougier commented Sep 29, 2024

marcklingen commented Sep 29, 2024

hrougier commented Sep 30, 2024

nshiab commented Sep 30, 2024

dimaMachina commented Sep 30, 2024

marcklingen commented Sep 30, 2024 • edited Loading

dimaMachina commented Sep 30, 2024

hrougier commented Sep 30, 2024 • edited Loading

marcklingen commented Sep 30, 2024

Chirag-kalsariya commented Sep 30, 2024

hrougier commented Sep 30, 2024

marcklingen commented Sep 30, 2024 • edited Loading

Chirag-kalsariya commented Sep 30, 2024

Chirag-kalsariya commented Sep 30, 2024

dimaMachina commented Oct 2, 2024 • edited Loading

dimaMachina commented Oct 2, 2024

danielkleinstein commented Oct 9, 2024

danielkleinstein commented Oct 9, 2024

dimaMachina commented Oct 9, 2024

danielkleinstein commented Oct 9, 2024 • edited Loading

hrougier commented Oct 9, 2024 • edited Loading

danielkleinstein commented Oct 10, 2024 • edited Loading

dimaMachina commented Oct 11, 2024

mnahkies commented Oct 11, 2024

dimaMachina commented Oct 11, 2024

mnahkies commented Oct 11, 2024

dimaMachina commented Oct 11, 2024 • edited Loading

mnahkies commented Oct 11, 2024

mnahkies commented Oct 11, 2024

dimaMachina commented Oct 11, 2024

dimaMachina commented Oct 11, 2024

mnahkies commented Oct 12, 2024

marcklingen commented Sep 30, 2024 •

edited

Loading

hrougier commented Sep 30, 2024 •

edited

Loading

marcklingen commented Sep 30, 2024 •

edited

Loading

dimaMachina commented Oct 2, 2024 •

edited

Loading

danielkleinstein commented Oct 9, 2024 •

edited

Loading

hrougier commented Oct 9, 2024 •

edited

Loading

danielkleinstein commented Oct 10, 2024 •

edited

Loading

dimaMachina commented Oct 11, 2024 •

edited

Loading