tsconfig.json(2,14): error TS6053: File '@tsconfig/node18/tsconfig.json' not found #2085

sammo · 2024-06-06T12:40:04Z

Hi -

I'm trying to start a new wasp project but running into this error on wasp db migrate-dev command.

Do you know what the issue could be?

✅ --- Database successfully set up. ----------------------------------------------

🐝 --- Building SDK... ------------------------------------------------------------

[ Wasp ] tsconfig.json(2,14): error TS6053: File '@tsconfig/node18/tsconfig.json' not found.
[ Wasp ] ../../../../node_modules/@testing-library/jest-dom/types/jest.d.ts(1,23): error TS2688: Cannot find type definition file for 'jest'.
[ Wasp ] ../../../../node_modules/@testing-library/jest-dom/types/jest.d.ts(9,27): error TS2304: Cannot find name 'expect'.
[ Wasp ] ../../../../node_modules/vitest/node_modules/vite/dist/node/index.d.ts(5,41): error TS2307: Cannot find module 'rollup/parseAst' or its corresponding type declarations.
[ Wasp ] There are types at '.../mySaasApp/node_modules/vitest/node_modules/rollup/dist/parseAst.d.ts', but this result could not be resolved under your current 'moduleResolution' setting. Consider updating to 'node16', 'nodenext', or 'bundler'.

❌ --- [Error] Your wasp project failed to compile: -------------------------------

SDK build failed with exit code: 2

❌ --- [Error] Compilation of wasp project failed: --------------------------------

1 errors found

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

Martinsos · 2024-06-06T13:15:21Z

Edit: see how to solve this here: #2085 (comment)

@sammo this seems quite weird!

It could help if you could provide following info: your OS, wasp version, node version, how did you start the project (I guess from open-saas? Doing wasp new -t saas?).

In the meantime, pls try running wasp clean and see if that helps -> if it does, let us know.

sammo · 2024-06-06T16:21:29Z

@Martinsos thanks for the quick reply.
I'm using

ubuntu 24.04
wasp 0.13.2
node 18.9.1

I started the project by running these commands:

curl -sSL https://get.wasp-lang.dev/installer.sh | sh
wasp new mySaasApp -t todo-ts

I'll wasp clean

sammo · 2024-06-06T16:23:46Z

@Martinsos I just ran wasp new -t saas and it worked!

Thank you for the help.

Martinsos · 2024-06-06T17:59:12Z

Great @sammo ! I am still curious what caused the initial issue, do you have any idea? How did you create the project first time?

EDIT: Sorry, I missed the message above, I see now how you started the project!
It is important to notice that you started Wasp from different template now -> saas is much richer than todo-ts. However, todo-ts should also work!

Would you mind trying creating project with wasp new myTodoApp -t todo-ts and seeing if you get the error again or if it is again? If it happens again, we will make sure to look deeper into it. I did try it just to be sure on my machine right now, but it works for my setup at the moment, for todo-ts.

sammo · 2024-06-06T18:19:13Z

@Martinsos I found out from my .zsh_history this error was raised by wasp db migrate-dev

That's how I replicated it

wasp new mySaasApp2 -t todo-ts
cd mySaasApp2
wasp db migrate-dev

And I got this error

🐝 --- Compiling wasp project... --------------------------------------------------

[  Wasp  ] Starting npm install
[  Wasp  ] Still installing npm dependencies!
[  Wasp  ] Installation going great - we'll get there soon!
[  Wasp !] npm WARN deprecated [email protected]: Use your platform's native atob() and btoa() methods instead
[  Wasp !] npm WARN deprecated [email protected]: Use your platform's native DOMException instead
[  Wasp  ] 
[  Wasp  ] added 462 packages, and audited 463 packages in 18s
[  Wasp  ] 
[  Wasp  ] 101 packages are looking for funding
[  Wasp  ]   run `npm fund` for details
[  Wasp  ] 
[  Wasp  ] 2 moderate severity vulnerabilities
[  Wasp  ] 
[  Wasp  ] Some issues need review, and may require choosing
[  Wasp  ] a different dependency.
[  Wasp  ] 
[  Wasp  ] Run `npm audit` for details.
[ Client ] Starting npm install
[ Server ] Starting npm install
[ Client ] 
[ Client ] added 117 packages, and audited 118 packages in 3s
[ Client ] 
[ Client ] 14 packages are looking for funding
[ Client ]   run `npm fund` for details
[ Client ] 
[ Client ] found 0 vulnerabilities
[ Server ] Still installing npm dependencies!
[ Server!] npm WARN deprecated [email protected]: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
[ Server!] npm WARN deprecated [email protected]: Rimraf versions prior to v4 are no longer supported
[ Server!] npm WARN deprecated [email protected]: Glob versions prior to v9 are no longer supported
[ Server ] 
[ Server ] added 372 packages, and audited 373 packages in 6s
[ Server ] 
[ Server ] 121 packages are looking for funding
[ Server ]   run `npm fund` for details
[ Server ] 
[ Server ] 4 moderate severity vulnerabilities
[ Server ] 
[ Server ] To address all issues (including breaking changes), run:
[ Server ]   npm audit fix --force
[ Server ] 
[ Server ] Run `npm audit` for details.
✅ --- Successfully completed npm install. ----------------------------------------


🐝 --- Setting up database... -----------------------------------------------------


[   Db  !] Error: P1003
[   Db  !] 
[   Db  !] Database dev.db does not exist at /.../mySaasApp2/.wasp/out/db/./dev.db
[   Db  !] 
[   Db   ] Environment variables loaded from .env
[   Db   ] Prisma schema loaded from ../db/schema.prisma
[   Db   ] 
[   Db   ] ✔ Generated Prisma Client (4.16.2 | library) to ./../../../node_modules/@prisma/client in 63ms
[   Db   ] You can now start using Prisma Client in your code. Reference: https://pris.ly/d/client
[   Db   ] ```
[   Db   ] import { PrismaClient } from '@prisma/client'
[   Db   ] const prisma = new PrismaClient()
[   Db   ] ```
✅ --- Database successfully set up. ----------------------------------------------


🐝 --- Building SDK... ------------------------------------------------------------


[  Wasp  ] tsconfig.json(2,14): error TS6053: File '@tsconfig/node18/tsconfig.json' not found.
[  Wasp  ] ../../../../node_modules/@testing-library/jest-dom/types/jest.d.ts(1,23): error TS2688: Cannot find type definition file for 'jest'.
[  Wasp  ] ../../../../node_modules/@testing-library/jest-dom/types/jest.d.ts(9,27): error TS2304: Cannot find name 'expect'.
[  Wasp  ] ../../../../node_modules/vitest/node_modules/vite/dist/node/index.d.ts(5,41): error TS2307: Cannot find module 'rollup/parseAst' or its corresponding type declarations.
[  Wasp  ]   There are types at '/.../mySaasApp2/node_modules/vitest/node_modules/rollup/dist/parseAst.d.ts', but this result could not be resolved under your current 'moduleResolution' setting. Consider updating to 'node16', 'nodenext', or 'bundler'.

❌ --- [Error] Your wasp project failed to compile: -------------------------------

- SDK build failed with exit code: 2


❌ --- [Error] Compilation of wasp project failed: --------------------------------

1 errors found

Martinsos · 2024-06-06T19:45:00Z

Awesome thanks! Just to confirm, this are not logs from the first time, you actually managed to replicate this again?

I wonder if this has something to do with node 18 hm, we will be looking into it.

Martinsos · 2024-06-10T11:34:56Z

One more user reported the same issue: wasp-lang/open-saas#173 .

@aliammari1, it could help if you could provide following info: your OS, wasp version, node version, how did you start the project (open saas? specific template? Mage?).

In the meantime, pls try running wasp clean and see if that helps -> if it does, let us know.

Martinsos · 2024-06-10T11:41:20Z

And here is the third report: #2091 !

Super short info from it:

OS: Linux 6.1.0-21-amd64 Debian 6.1.90-1 (2024-05-03) x86_64 GNU/Linux
Browser: chrome
Version: chrome 125.0.6422.141
Wasp: 0.13.2
Node v18.19.0

wasp clean didn't help them.

Interesting data so far is:

Both reports are from Ubuntu (we don't know about thrid report yet).
Error is mentioning node18 and two of the users reported using node 18.

I this this is very likely connected to node 18, not sure how yet or why it started happening now. Ubuntu is probably not the cause, but probably the "delivery method", in the sense that the users are using a version of Ubuntu that comes with node 18 by default.

Martinsos · 2024-06-10T11:43:04Z

@grsh50 , could you please try switching to node 20 (e.g. using nvm) and try running Wasp again?

@aliammari1 which node version are you using? If you are using 18, could you also try switching to 20 and tell us if that helps?

grsh50 · 2024-06-10T12:36:39Z

grosh@buh:~/Documents/src/repo/newWasp/myTodoApp$ wasp db migrate-dev

🐝 --- Compiling wasp project... --------------------------------------------------


✅ --- Successfully completed npm install. ----------------------------------------


🐝 --- Setting up database... -----------------------------------------------------


[   Db  !] Error: P1003
[   Db  !] 
[   Db  !] Database dev.db does not exist at /home/grosh/Documents/src/repo/newWasp/myTodoApp/.wasp/out/db/./dev.db
[   Db  !] 
✅ --- Database successfully set up. ----------------------------------------------


🐝 --- Building SDK... ------------------------------------------------------------


[  Wasp  ] tsconfig.json(2,14): error TS6053: File '@tsconfig/node18/tsconfig.json' not found.
[  Wasp  ] ../../../../node_modules/@testing-library/jest-dom/types/jest.d.ts(1,23): error TS2688: Cannot find type definition file for 'jest'.
[  Wasp  ] ../../../../node_modules/@testing-library/jest-dom/types/jest.d.ts(9,27): error TS2304: Cannot find name 'expect'.
[  Wasp  ] ../../../../node_modules/vitest/node_modules/vite/dist/node/index.d.ts(5,41): error TS2307: Cannot find module 'rollup/parseAst' or its corresponding type declarations.
[  Wasp  ]   There are types at '/home/grosh/Documents/src/repo/newWasp/myTodoApp/node_modules/vitest/node_modules/rollup/dist/parseAst.d.ts', but this result could not be resolved under your current 'moduleResolution' setting. Consider updating to 'node16', 'nodenext', or 'bundler'.

❌ --- [Error] Your wasp project failed to compile: -------------------------------

- SDK build failed with exit code: 2


❌ --- [Error] Compilation of wasp project failed: --------------------------------

1 errors found
grosh@buh:~/Documents/src/repo/newWasp/myTodoApp$ node --version
v20.14.0

Martinsos · 2024-06-10T14:27:39Z

Ok so it also happens with node 20, didn't expect that! Thanks, we will be looking into this in the following days and will be posting updates here!

Martinsos · 2024-06-10T14:30:24Z

Note for devs: we currently always go with @tsconfig/node18, even if people use node 20 or later, because we have this 18 currently on th lower limit for what Wasp supports. In the future we will be basing it on engines in package.json.

Martinsos · 2024-06-10T14:41:05Z

Note for devs: I tried replicating this on my machine but failed, all works so far. Specifically, I reinstalled latest version of Wasp and ran wasp new MyTestApp -t todo-ts and then wasp db migrate-dev. I also tried cleaning the whole npm cache with npm cache clean --force to simulate a more "fresher" situation, but that also didn't help, it still works.
I did this first test with node 20, I tried doing it also with node 18.19 but also couldn't replicate. This is on Arch Linux.

aliammari1 · 2024-06-10T14:51:31Z

@grsh50 , could you please try switching to node 20 (e.g. using nvm) and try running Wasp again?

@aliammari1 which node version are you using? If you are using 18, could you also try switching to 20 and tell us if that helps?

thank you sir, the problem was my node version. I updated it from 18 to 20 and it worked

Martinsos · 2024-06-10T17:35:57Z

@grsh50 , could you please try switching to node 20 (e.g. using nvm) and try running Wasp again?
@aliammari1 which node version are you using? If you are using 18, could you also try switching to 20 and tell us if that helps?

thank you sir, the problem was my node version. I updated it from 18 to 20 and it worked

Thanks for letting me know!

This does make things even more complex though hah, because one user got it fixed by installing another template, while one user fixed it with using another node version, and finally none of these helped third user! Hm. Almost sounds like it is getting fixed randomly.

grsh50 · 2024-06-11T07:43:43Z

Thank you for your support! :)

I ran wasp new todo -t todo-ts, and it worked.

This time, compiling the Wasp project took longer, but the SDK build was almost instant.

Could the issue be related to the Node version used to create the new project?
The previous logs were from a project created on Node 18.19, and only the wasp db migrate-dev command was executed on Node 20.14.

Update:
The MAGE app now runs.

Martinsos · 2024-06-12T14:56:50Z

Thank you for your support! :)

I ran wasp new todo -t todo-ts, and it worked.

This time, compiling the Wasp project took longer, but the SDK build was almost instant.

Could the issue be related to the Node version used to create the new project? The previous logs were from a project created on Node 18.19, and only the wasp db migrate-dev command was executed on Node 20.14.

Update: The MAGE app now runs.

Oh that's an interesting hypothesis indeed!

AHa, wait, now even the older app runs? Ok, now we have no idea again what is causing this :D.

Is there any way you can replicate the initial problem again? For example going to node 18 again, and trying to run that Mage app, or maybe new app based on todo-ts?

@sammo above managed to replicate it doing wasp new MyCoolApp -t todo-ts with node 18, if you can also do that consistently, that gives us something solid to work from.

Martinsos · 2024-06-13T16:40:49Z

One more report: https://discord.com/channels/686873244791210014/1250815248395669504/1250815248395669504 .

User was using node 18, but new data point is that they managed to fix it by adding

 "devDependencies": {
    "@tsconfig/node18": "latest",

to their package.json.

What also worked was switching to node 20, then that dev dependency was not needed, same like other users.

grsh50 · 2024-06-13T23:15:27Z

I ran some test builds with todo's and saas templates on node versions 18.19.0 and 18.19.1 and everything works fine.

Update:
I tried the case I mentioned earlier - changing the node version after creating the template.
Everything works fine.

$ node --version
v18.19.0
$ wasp new
$ nvm use 20.14.0
$ wasp db start
$ wasp db migrate-dev

Martinsos · 2024-06-14T12:23:32Z

I ran some test builds with todo's and saas templates on node versions 18.19.0 and 18.19.1 and everything works fine.

Ah come on :)! I am kidding, thanks a lot, but am still surprised by inconsistency of this bug. Still, we will figure it out, one way or another!

infomiho · 2024-06-27T08:42:08Z

This is the only similar issue I found while searching around the internet: TypeStrong/ts-node#2076

It seems to be related to ts-node which jest uses under the hood to resolve the tsconfig.json. This was caused by some internal API changes in TS 5.2+ version. I'm really not sure if we have similar issues as reported there. I've tested also on Ubuntu with Node 18 and couldn't reproduce it.

Martinsos · 2024-06-27T09:08:37Z

This is the only similar issue I found while searching around the internet: TypeStrong/ts-node#2076

It seems to be related to ts-node which jest uses under the hood to resolve the tsconfig.json. This was caused by some internal API changes in TS 5.2+ version. I'm really not sure if we have similar issues as reported there. I've tested also on Ubuntu with Node 18 and couldn't reproduce it.

It being triggered by changes in TS version makes sense, as it started happened suddenly, that is very likely the cause! We need to pin down that TS version tighter.

I would still like to better understand the exact thing that happens, but I think we have a good bet what is the cause now.

sodic · 2024-07-02T15:32:45Z

It seems to be related to ts-node which jest uses under the hood to resolve the tsconfig.json.

That's not it (at least I think it isn't). ts-node is nowhere to be found in node_modules. From what I see, Jest isn't using it.

@infomiho What made you think we were using ts-node?
If it was this comment, it was probably a misunderstanding - the comment talks about Jest TS configuration files (not tsconfig.json files).

Regardless, I tried installing ts-node both globally and in the repo, with the hopes of jest using it if it's available, but no luck. Unless I missed something, I think it's safe to say this isn't related to ts-node.

I'll now try reproducing it with different versions of TypeScript.

sodic · 2024-07-03T09:53:25Z

Next time this happens, we should ask our users for a zip of their projects (or at least their package.json and package-lock.json files).

Martinsos · 2024-07-03T12:54:23Z

@sodic it is not any kind of special projects though, they say above they merely had it happen on creating a new Wasp project from the template. So maybe package-lock.json files would offer something unique for their installation, but the rest, including package.json, shouldn't be anything unique. Notice that even if they share their package-lock.json, it still won't capture what was installed for the purposes of the framework code (or will it?).

Martinsos · 2024-07-03T15:53:42Z

Some quick analysis of information we have so far:

OS: Ubuntu, Debian, unknown, unknown
everybody had the issue due to creating a Wasp project with node 18.
different fixes that worked for people:
- wasp clean && wasp new -t saas while staying on node 18
- switching to node 20 and running the project again
- creating project again with node 20 and then running it
- adding tsconfig/node18 directly to package.json as a dev dep
once things get working for people, they continue working

It seems that there is a situation, when using node 18, that results in tsconfig/node18 not getting installed, and then stuff fails. And it seems that to get out of it, you need to shake things up a bit, and the most efficient way is to switch to node 20, but it seems like sometimes something else also helps.

sodic · 2024-07-03T16:07:03Z

Ideas:

The file most likely really is missing (i.e., it's not an error in the code trying to find the file) because:
1. TSC crashes immediately after not being able to find the file.
2. One user added it to devDependencies at the root of the project, which fixed the problem immediately.
Our best guess is that, sometimes, the @tscofig/node18 doesn't get installed to top-level node_modules.

Other thoughts:

The SDK lists tsconfig/node18 as a devDependency. How come it's ever installed (devDependencies shouldn't be installed for packages)? Is it because it's a linked package?
The server also lists tsconfig/node18 as a devDependency. I forgot how NPM install works if the package is already installed in scope (I think it just duplicates it)?
The central question: Why do we ever get tsconfig/node18 installed in top-level node_modules. Do we just get lucky that some other package includes it as a regular dependency? Does NPM install devDependencies for SDK? Does this also happen in production?
Implement npm workspaces #1653 might fix this problem.

One problem I noticed:

It seems we treat the SDK as a dependency (i.e., we don't run npm install inside its folder, it's installed indirectly through the root package.json), but we also treat it as a project (i.e., we build it). This is wrong and might be related to this problem. In other words, tsconfig/node18 is possibly being installed by luck.

sodic · 2024-07-04T08:08:29Z

For users running into this: Please zip the entire project that exhibits this behavior and send it to us :)

Moamethic · 2024-07-16T20:20:54Z

Hi
I tried everything discussed here and nothing worked for me, so here is the download link to my project zip:
https://mega.nz/file/YH1AgBLa#URDfK1Pyv0zpD8JcoZz-OqxJIx_o-YrMTjSjH3w7PO8

P.S: Sorry for the large file size, I just included everything for better diagnosis.

infomiho · 2024-07-16T20:50:13Z

@Moamethic Hey, thank you for the info. Could you share the error message you see?

Moamethic · 2024-07-16T20:52:33Z

@Moamethic Hey, thank you for the info. Could you share the error message you see?

Sure.

🐝 --- Building SDK... ------------------------------------------------------------


[  Wasp  ] tsconfig.json(2,14): error TS6053: File '@tsconfig/node18/tsconfig.json' not found.
[  Wasp  ] ../../../../node_modules/@testing-library/jest-dom/types/jest.d.ts(1,23): error TS2688: Cannot find type definition file for 'jest'.
[  Wasp  ] ../../../../node_modules/@testing-library/jest-dom/types/jest.d.ts(9,27): error TS2304: Cannot find name 'expect'.
[  Wasp  ] ../../../../node_modules/vitest/node_modules/vite/dist/node/index.d.ts(5,41): error TS2307: Cannot find module 'rollup/parseAst' or its corresponding type declarations.
[  Wasp  ]   There are types at '/root/my-proj/app/node_modules/vitest/node_modules/rollup/dist/parseAst.d.ts', but this result could not be resolved under your current 'moduleResolution' setting. Consider updating to 'node16', 'nodenext', or 'bundler'.

❌ --- [Error] Your wasp project failed to compile: -------------------------------

- SDK build failed with exit code: 2


❌ --- [Error] Compilation of wasp project failed: --------------------------------

1 errors found

infomiho · 2024-07-16T21:09:23Z

And also, which Node version and Wasp version are you using? Thank you for reporting this 👍

Until we find out the root cause, did you maybe try using Node 20 + running wasp clean and wasp start again?

Moamethic · 2024-07-16T21:18:49Z

And also, which Node version and Wasp version are you using? Thank you for reporting this 👍

Until we find out the root cause, did you maybe try using Node 20 + running wasp clean and wasp start again?

At first I was using node 18, then I installed nvm and tried with node 20 using wasp clean, but the issue still persists. I installed wasp using curl -sSL https://get.wasp-lang.dev/installer.sh | sh two hours ago, so I'm using the current latest version for sure. And I run it on Ubuntu 24.04.

Martinsos · 2024-07-22T12:05:15Z

Another one: https://discord.com/channels/686873244791210014/1263530383379796111/1263615673678958612

Martinsos · 2024-07-24T10:00:10Z

Another hit: https://discord.com/channels/686873244791210014/1265303458626539523/1265303458626539523 .

sodic · 2024-07-26T11:52:24Z

@Moamethic Hey, I'm looking at your code now.

Can you maybe share the NPM version you used when you hit the bug (if you remember)?

Moamethic · 2024-07-26T11:55:17Z

@Moamethic Hey, I'm looking at your code now.

Can you maybe share the NPM version you used when you hit the bug (if you remember)?

Unfortunately I don't remember.

santolucito · 2024-08-08T10:25:49Z

What also worked was switching to node 20, then that dev dependency was not needed, same like other users.

I also ran into the issue on Node 18, and switching to Node 20 fixed it

sodic · 2024-08-08T13:57:16Z

@santolucito Please tell me you remember your NPM version when it was broken 🙏

santolucito · 2024-08-08T14:06:57Z

I have no idea. I had spun up a Digital Ocean server and went through the install steps normally. I can redo this quickly if you want and check things. Just let me know what you want to know.

sodic · 2024-08-08T14:43:07Z

@santolucito If you could reproduce the bug in a Digital Ocean setup, tell me the versions of:

node
npm
wasp

And zip your project code - I'd be eternally grateful! I just hope you'll be able to reproduce it. This bug's pretty hard to catch.

santolucito · 2024-08-08T15:14:39Z

@sodic I sent you an email to the email listed on your profile.

sodic · 2024-08-08T15:42:13Z

Thanks @santolucito, you're a life-saver!

The bug happens only with NPM versions older v9.5.0. I can reproduce it with any version of Node (18.x.x or 20.x.x), as long as I use an old enough installation of npm.

To fix the problem, update your NPM version to v9.5.0 or higher. I recommend updating it to the latest version.

In a regular setup:

npm install -g npm@latest

If you're using nvm:

nvm install-latest-npm

After that, run wasp clean, and you're good to go!

Since the bug only happens with NPM versions older than 2.5 years, and we know how to fix it, I'm closing the issue.
This problem does indicate something is off in our installation configuration, but that's already tracked here: #2150.
We should also warn users when they're using an NPM version that Wasp doesn't work with, tracked here: #2113.

sammo closed this as completed Jun 6, 2024

Martinsos reopened this Jun 6, 2024

Martinsos added the bug Something isn't working label Jun 6, 2024

Martinsos transferred this issue from wasp-lang/open-saas Jun 6, 2024

grsh50 mentioned this issue Jun 8, 2024

Project failed to compile #2091

Closed

Martinsos mentioned this issue Jun 10, 2024

SDK Build Error wasp-lang/open-saas#173

Closed

Martinsos changed the title ~~wasp db migrate-dev throws an error~~ tsconfig.json(2,14): error TS6053: File '@tsconfig/node18/tsconfig.json' not found Jun 13, 2024

sodic self-assigned this Jul 2, 2024

sodic mentioned this issue Jul 3, 2024

Reconsider how we treat and build the SDK #2150

Open

sodic closed this as completed Aug 8, 2024

sodic mentioned this issue Aug 8, 2024

Improve error message when correct version of npm isn't in PATH #2113

Open

sodic mentioned this issue Nov 21, 2024

wasp db migrate-dev fails on a fresh install wasp-lang/open-saas#319

Closed

tsconfig.json(2,14): error TS6053: File '@tsconfig/node18/tsconfig.json' not found #2085

tsconfig.json(2,14): error TS6053: File '@tsconfig/node18/tsconfig.json' not found #2085

Comments

sammo commented Jun 6, 2024

Martinsos commented Jun 6, 2024 • edited by sodic Loading

sammo commented Jun 6, 2024

sammo commented Jun 6, 2024 • edited Loading

Martinsos commented Jun 6, 2024 • edited Loading

sammo commented Jun 6, 2024 • edited Loading

Martinsos commented Jun 6, 2024

Martinsos commented Jun 10, 2024 • edited Loading

Martinsos commented Jun 10, 2024 • edited Loading

Martinsos commented Jun 10, 2024

grsh50 commented Jun 10, 2024

Martinsos commented Jun 10, 2024

Martinsos commented Jun 10, 2024

Martinsos commented Jun 10, 2024

aliammari1 commented Jun 10, 2024

Martinsos commented Jun 10, 2024

grsh50 commented Jun 11, 2024 • edited Loading

Martinsos commented Jun 12, 2024

Martinsos commented Jun 13, 2024

grsh50 commented Jun 13, 2024 • edited Loading

Martinsos commented Jun 14, 2024

infomiho commented Jun 27, 2024

Martinsos commented Jun 27, 2024

sodic commented Jul 2, 2024

sodic commented Jul 3, 2024

Martinsos commented Jul 3, 2024

Martinsos commented Jul 3, 2024

sodic commented Jul 3, 2024 • edited Loading

sodic commented Jul 4, 2024

Moamethic commented Jul 16, 2024

infomiho commented Jul 16, 2024

Moamethic commented Jul 16, 2024 • edited Loading

infomiho commented Jul 16, 2024

Moamethic commented Jul 16, 2024

Martinsos commented Jul 22, 2024

Martinsos commented Jul 24, 2024

sodic commented Jul 26, 2024

Moamethic commented Jul 26, 2024

santolucito commented Aug 8, 2024

sodic commented Aug 8, 2024 • edited Loading

santolucito commented Aug 8, 2024 • edited Loading

sodic commented Aug 8, 2024

santolucito commented Aug 8, 2024

sodic commented Aug 8, 2024 • edited Loading

Martinsos commented Jun 6, 2024 •

edited by sodic

Loading

sammo commented Jun 6, 2024 •

edited

Loading

Martinsos commented Jun 6, 2024 •

edited

Loading

sammo commented Jun 6, 2024 •

edited

Loading

Martinsos commented Jun 10, 2024 •

edited

Loading

Martinsos commented Jun 10, 2024 •

edited

Loading

grsh50 commented Jun 11, 2024 •

edited

Loading

grsh50 commented Jun 13, 2024 •

edited

Loading

sodic commented Jul 3, 2024 •

edited

Loading

Moamethic commented Jul 16, 2024 •

edited

Loading

sodic commented Aug 8, 2024 •

edited

Loading

santolucito commented Aug 8, 2024 •

edited

Loading

sodic commented Aug 8, 2024 •

edited

Loading