Extension fails with pnpm command not found #148903

doubleplusc · 2022-05-04T22:20:26Z

I previously commented on microsoft/vscode-eslint#1462 but OP's problem was fixed so the issue closed. My problem persists even after a restart, so I am creating a new issue.

I have pnpm installed on Linux via npm install -g pnpm. pnpm works fine in the vscode integrated terminal and standalone terminals.

The extension fails with the following error on load:

Uncaught exception received.
Error: Command failed: pnpm root -g
/bin/sh: line 1: pnpm: command not found

    at checkExecSyncError (node:child_process:835:11)
    at execSync (node:child_process:909:15)
    at node:electron/js2c/asar_bundle:5:12692
    at Object.get (/home/doubleplusc/.vscode-oss/extensions/dbaeumer.vscode-eslint-2.2.2/server/out/eslintServer.js:1:172258)
    at /home/doubleplusc/.vscode-oss/extensions/dbaeumer.vscode-eslint-2.2.2/server/out/eslintServer.js:1:174308
    at /home/doubleplusc/.vscode-oss/extensions/dbaeumer.vscode-eslint-2.2.2/server/out/eslintServer.js:1:174323

pnpm root -g returns
/home/doubleplusc/.local/share/pnpm/global/5/node_modules

Thanks!

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

dbaeumer · 2022-05-05T07:38:29Z

How do you start VS Code? Can you try starting it from a terminal in which pnpm works and see if you get the same error?

doubleplusc · 2022-05-05T16:44:12Z

I always start it via my DE's application menu.
I did what you suggested, I opened a terminal (with working pnpm) and opened VSCode. The extension now works as intended.
I can start VSCode from the terminal for the time being, but it's really strange that starting via terminal vs non-terminal would have different behavior. Any chance this can be fixed?

S3bt3r · 2022-05-06T11:42:25Z

I have the same problem. In general, there are always various problems with regard to the shell.
In my opinion, the cause of the problem is that the plugin always starts its own instance of "/bin/sh" instead of creating an instance of the default automation profile shell.
Furthermore, the VSCode internal node is probably used and not the one from the environment. I think so because the node version in the plugin is always different from my environment.

Why do I think so? Many who use Node use NVM or something similar.
This is typically only configured for the shell in which you are working. In my case zsh.

I have made many attempts to solve problems of this type, unfortunately I usually fail.
Since I'm using Debian in WSL, /bin/sh points to dash.
The way the plugin uses /bin/sh, the shell isn't customizable either. Because changes in /etc/profile or ~/.profile have no effect on it.

Proof of this:

# Plugin
Error: Command failed: pnpm root -g
/bin/sh: line 1: pnpm: command not found

#/bin/zsh
pnpm root -g
/home/seri/.local/share/pnpm/global/5/node_modules

#/bin/zsh
/bin/sh -c "pnpm root -g"
/home/seri/.local/share/pnpm/global/5/node_modules

#/bin/zsh
/bin/sh
pnpm root -g
/home/seri/.local/share/pnpm/global/5/node_modules

I think it would be best if the plugin simply creates an instance of the shell from the automation profile.

dbaeumer · 2022-05-06T12:34:57Z

@joaomoreno not sure anymore if this is you or @bpasero.

What they actually see is when the start VS Code from the Desktop the environment setup is not complete hence result in cases where ESLint doesn't see pnpm although it is on the path in the terminal. Everything works fine if VS Code is started from within the terminal.

S3bt3r · 2022-05-06T21:05:18Z

I start vs code always via code . from my zsh (wsl) and the plugin fails with pnpm not found.

dbaeumer · 2022-05-09T07:53:58Z

@Asesjix does pnpm work in the terminal you start code from

S3bt3r · 2022-05-09T08:17:20Z

@dbaeumer Yes absolutely, hence my suggestion to use the shell from the automation profile.

Maybe it's helpful information.
I also noticed that the plugin node is used in version 16.13. In my terminal Node is in version 16.15 (node -v).
The same version is only used when I specify the path to Node via the settings.
"eslint.runtime": "/home/seri/.nvm/versions/node/v16.15.0/bin/node"

My setup is quite simple and not extensively configured.

I am using Windows with WSL running Debian.
In Debian I installed zsh and set it as the default terminal.

Then I installed NVM.
With NVM I install Node in the version in which I need it.
Typically with nvm install --lts --default.
It means that the last LTS version will be installed and set as the default.
This means that in my shell node -v specifies the version installed via NVM.

Then I install pnpm with npm install -g pnpm.

To develop, I then start VS Code with code . via my terminal in which node and pnpm work.

That's it.

According to these docs except I'm using zsh and pnpm.
https://docs.microsoft.com/en-us/windows/dev-environment/javascript/nodejs-on-wsl

darthsoup · 2022-05-09T11:23:47Z

Did you guys update to the newest pnpm version? It now needs a alias in the bash config

Try this in your console:
pnpm setup

S3bt3r · 2022-05-09T19:06:35Z

I know and already did that.

MIchaelJier · 2022-05-18T02:52:02Z

reload vscode is working for me

joaomoreno · 2022-05-18T13:26:06Z

@doubleplusc Do you still hit this?

doubleplusc · 2022-05-19T02:47:07Z

Hi @joaomoreno, thanks for following up. I still have the issue on the latest versions of pnpm 7.1.0 and vscode 1.67.2.

joaomoreno · 2022-05-20T13:14:18Z

The problem here is somewhere in your bashrc (or equivalent). There's something in your rc shell script which makes loading it very slow. Do you not get a warning about that on startup?

doubleplusc · 2022-05-20T15:43:14Z

I don't see any warnings except pnpm. The below image is all I see. Problems, Terminal, and Debug Console don't have any information.

I just cleared everything in my .bashrc except for 3 lines related to setting node and pnpm paths and restarted the system, but it didn't do anything.

524c · 2022-05-21T20:31:39Z

Hello, here the problem is with eslint. When I try to save any file I get an error. When I run the same command in terminal, everything works fine. I'm using vscode in ssh development mode, the server being a raspberry and the client a Macos.

joaomoreno · 2022-05-23T07:30:37Z

@doubleplusc Can you check the Log (Main) output?

devyourcar · 2022-05-23T08:17:02Z

Here's my output:

[Info  - 20:16:14] ESLint server is starting
[Info  - 20:16:14] ESLint server running in node v16.13.0
[Info  - 20:16:14] ESLint server is running.
Uncaught exception received.
Error: Command failed: pnpm root -g
    at checkExecSyncError (node:child_process:846:11)
    at execSync (node:child_process:920:15)
    at node:electron/js2c/asar_bundle:5:12704
    at Object.get (/Users/abcd/.vscode/extensions/dbaeumer.vscode-eslint-2.2.3/server/out/eslintServer.js:1:175173)
    at /Users/abcd/.vscode/extensions/dbaeumer.vscode-eslint-2.2.3/server/out/eslintServer.js:1:177223
    at /Users/abcd/.vscode/extensions/dbaeumer.vscode-eslint-2.2.3/server/out/eslintServer.js:1:177238
Uncaught exception received.
Error: Command failed: pnpm root -g
    at checkExecSyncError (node:child_process:846:11)
    at execSync (node:child_process:920:15)
    at node:electron/js2c/asar_bundle:5:12704
    at Object.get (/Users/abcd/.vscode/extensions/dbaeumer.vscode-eslint-2.2.3/server/out/eslintServer.js:1:175173)
    at /Users/abcd/.vscode/extensions/dbaeumer.vscode-eslint-2.2.3/server/out/eslintServer.js:1:177223
    at /Users/abcd/.vscode/extensions/dbaeumer.vscode-eslint-2.2.3/server/out/eslintServer.js:1:177238

doubleplusc · 2022-05-23T15:03:44Z

@doubleplusc Can you check the Log (Main) output?

@joaomoreno
I get the same output below whether I am opening from application menu (pnpm fails) or from terminal (pnpm does not fail). These lines are probably not part of the problem.

[2022-05-23 07:52:43.480] [main] [info] window#load: attempt to load window (id: 1)
[2022-05-23 07:52:43.539] [main] [info] update#setState idle
[2022-05-23 07:52:43.560] [main] [info] ExtensionHostStarterWorker created
[2022-05-23 07:52:43.566] [main] [error] SyntaxError: Unexpected string in JSON at position 171
    at JSON.parse (<anonymous>)
    at St.afterWindowOpen (/opt/vscodium-bin/resources/app/out/vs/code/electron-main/main.js:75:75767)
[2022-05-23 07:52:44.483] [main] [info] window#load: window reported ready (id: 1)
[2022-05-23 07:52:44.627] [main] [info] Starting extension host with pid 35273 (fork() took 31 ms).
[2022-05-23 07:52:44.627] [main] [info] ExtensionHostStarterWorker.start() took 33 ms.
[2022-05-23 07:53:13.541] [main] [info] update#setState checking for updates
[2022-05-23 07:53:13.600] [main] [info] update#setState idle

joaomoreno · 2022-05-24T14:04:31Z

@doubleplusc I see you're using VSCodium. Can you reproduce this with VS Code? Or VS Code Insiders? If so, can you please send that output instead?

doubleplusc · 2022-05-24T14:41:00Z

@doubleplusc I see you're using VSCodium. Can you reproduce this with VS Code? Or VS Code Insiders? If so, can you please send that output instead?

@joaomoreno Same output on VSCode. The others in this thread who posted their error messages are using VSCode and VSCode Server, so this is not a distribution-specific problem.

EDIT: And the Log (Main) output from VSCode.

[2022-05-24 07:43:27.922] [main] [info] window#load: attempt to load window (id: 1)
[2022-05-24 07:43:27.969] [main] [info] update#setState idle
[2022-05-24 07:43:27.993] [main] [info] ExtensionHostStarterWorker created
[2022-05-24 07:43:28.755] [main] [info] window#load: window reported ready (id: 1)
[2022-05-24 07:43:28.990] [main] [info] Starting extension host with pid 80759 (fork() took 9 ms).
[2022-05-24 07:43:28.991] [main] [info] ExtensionHostStarterWorker.start() took 11 ms.
[2022-05-24 07:43:57.971] [main] [info] update#setState checking for updates
[2022-05-24 07:43:58.015] [main] [info] update#setState idle

kelly-tock · 2022-05-24T20:04:14Z

I have a slightly different scenario, but seems related:

[Info  - 3:01:42 PM] ESLint server is starting
[Info  - 3:01:42 PM] ESLint server running in node v16.13.2
[Info  - 3:01:42 PM] ESLint server is running.
[Info  - 3:01:43 PM] ESLint library loaded from: /Users/kelly/admin-pnpm/node_modules/.pnpm/eslint@8.16.0/node_modules/eslint/lib/api.js
2022-05-24T20:01:43.838Z eslint:rules Loading rule 'brace-style' (remaining=286)
2022-05-24T20:01:43.843Z eslint:rules Loading rule 'comma-dangle' (remaining=285)
2022-05-24T20:01:43.849Z eslint:rules Loading rule 'dot-notation' (remaining=284)
2022-05-24T20:01:43.853Z eslint:rules Loading rule 'indent' (remaining=283)
2022-05-24T20:01:43.855Z eslint:rules Loading rule 'init-declarations' (remaining=282)
2022-05-24T20:01:43.856Z eslint:rules Loading rule 'keyword-spacing' (remaining=281)
2022-05-24T20:01:43.858Z eslint:rules Loading rule 'lines-between-class-members' (remaining=280)
2022-05-24T20:01:43.870Z eslint:rules Loading rule 'no-dupe-class-members' (remaining=279)
2022-05-24T20:01:43.872Z eslint:rules Loading rule 'no-duplicate-imports' (remaining=278)
2022-05-24T20:01:43.874Z eslint:rules Loading rule 'no-empty-function' (remaining=277)
2022-05-24T20:01:43.877Z eslint:rules Loading rule 'no-extra-parens' (remaining=276)
2022-05-24T20:01:43.880Z eslint:rules Loading rule 'no-extra-semi' (remaining=275)
2022-05-24T20:01:43.899Z eslint:rules Loading rule 'no-invalid-this' (remaining=274)
2022-05-24T20:01:43.901Z eslint:rules Loading rule 'no-loop-func' (remaining=273)
2022-05-24T20:01:43.902Z eslint:rules Loading rule 'no-loss-of-precision' (remaining=272)
2022-05-24T20:01:43.902Z eslint:rules Loading rule 'no-magic-numbers' (remaining=271)
2022-05-24T20:01:43.927Z eslint:rules Loading rule 'no-restricted-imports' (remaining=270)
2022-05-24T20:01:43.961Z eslint:rules Loading rule 'no-unused-expressions' (remaining=269)
2022-05-24T20:01:43.964Z eslint:rules Loading rule 'no-useless-constructor' (remaining=268)
2022-05-24T20:01:43.969Z eslint:rules Loading rule 'object-curly-spacing' (remaining=267)
2022-05-24T20:01:43.993Z eslint:rules Loading rule 'quotes' (remaining=266)
2022-05-24T20:01:44.003Z eslint:rules Loading rule 'semi' (remaining=265)
2022-05-24T20:01:44.006Z eslint:rules Loading rule 'space-before-blocks' (remaining=264)
2022-05-24T20:01:44.007Z eslint:rules Loading rule 'space-infix-ops' (remaining=263)
Uncaught exception received.
Error: Failed to load plugin 'jsx-a11y' declared in '.eslintrc.js » @tock/eslint-config': Cannot find module 'eslint-plugin-jsx-a11y'
Require stack:
- /Users/kelly/admin-pnpm/consumer/__placeholder__.js
Referenced from: /Users/kelly/admin-pnpm/tock-eslint-config/index.js
    at Function.Module._resolveFilename (node:internal/modules/cjs/loader:933:15)
    at Function.resolve (node:internal/modules/cjs/helpers:108:19)
    at Object.resolve (/Users/kelly/admin-pnpm/node_modules/.pnpm/@eslint+eslintrc@1.3.0/node_modules/@eslint/eslintrc/dist/eslintrc.cjs:2325:46)
    at ConfigArrayFactory._loadPlugin (/Users/kelly/admin-pnpm/node_modules/.pnpm/@eslint+eslintrc@1.3.0/node_modules/@eslint/eslintrc/dist/eslintrc.cjs:3376:33)
    at ConfigArrayFactory._loadExtendedPluginConfig (/Users/kelly/admin-pnpm/node_modules/.pnpm/@eslint+eslintrc@1.3.0/node_modules/@eslint/eslintrc/dist/eslintrc.cjs:3196:29)
    at ConfigArrayFactory._loadExtends (/Users/kelly/admin-pnpm/node_modules/.pnpm/@eslint+eslintrc@1.3.0/node_modules/@eslint/eslintrc/dist/eslintrc.cjs:3117:29)
    at ConfigArrayFactory._normalizeObjectConfigDataBody (/Users/kelly/admin-pnpm/node_modules/.pnpm/@eslint+eslintrc@1.3.0/node_modules/@eslint/eslintrc/dist/eslintrc.cjs:3058:25)
    at _normalizeObjectConfigDataBody.next (<anonymous>)
    at ConfigArrayFactory._normalizeObjectConfigData (/Users/kelly/admin-pnpm/node_modules/.pnpm/@eslint+eslintrc@1.3.0/node_modules/@eslint/eslintrc/dist/eslintrc.cjs:3003:20)
    at _normalizeObjectConfigData.next (<anonymous>)

pnpm version 7.1.5, installed via npm i -g.

settings.json:

 "eslint.runtime": "/Users/kelly/Library/Caches/fnm_multishells/9686_1653421493848/bin/node",
  "eslint.alwaysShowStatus": true,
  "eslint.workingDirectories": [ "./consumer", "./dashboard" ],
  "eslint.packageManager": "pnpm",

joaomoreno · 2022-05-25T06:55:39Z

@bpasero I can't seem to find the necessary steps to debug a bad user env. Can you give @doubleplusc instructions on how he can debug it further? I'll make sure to add it to my Saved Replies so I don't send these issues to you anymore.

Meanwhile: @doubleplusc, this is related to your bashrc or equivalent. I suggest commenting out somethings over there until you figure out which thing makes the bug reproduce.

doubleplusc · 2022-05-25T21:13:34Z

@joaomoreno If reproducing is a problem, I've uploaded a VM image (3.5GB download, 7.7GB once imported) that can reproduce the error. It's a fresh OS with pnpm installed and the .bashrc cleared except for some path setting lines. user/pass is test/test.

https://drive.google.com/file/d/1LMcQ0qClLVzn__2Dt_pNJMfadCc8OinW/view?usp=sharing

Open EndeavourOS menu on the bottom left -> Development -> Visual Studio Code. asd.js should be opened on launch, and Output will eventually show the error.

bpasero · 2022-05-27T07:01:34Z

If you run code --verbose we print shell env related messages to the console. Look for resolveShellEnv and getUnixShellEnvironment.

doubleplusc · 2022-05-28T14:50:22Z

I added --verbose into the .desktop file Exec line and added Terminal=true.
I have attached the output.

verbose.log

These are the lines with resolveShellEnv. There are no log lines for getUnixShellEnvironment.

[main 2022-05-28T14:30:27.995Z] resolveShellEnv(): skipped (VSCODE_CLI is set)
[main 2022-05-28T14:30:30.722Z] resolveShellEnv(): skipped (VSCODE_CLI is set)
[main 2022-05-28T14:30:31.087Z] resolveShellEnv(): skipped (VSCODE_CLI is set)
[2508:0528/103031.675230:INFO:CONSOLE(29)] "%cTRACE color: #888 resolveShellEnv(): skipped (VSCODE_CLI is set)", source: vscode-file://vscode-app/opt/visual-studio-code/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js (29)
[main 2022-05-28T14:30:57.800Z] resolveShellEnv(): skipped (VSCODE_CLI is set)

bpasero · 2022-05-29T05:36:28Z

If you run VSCode from a terminal, we do not resolve the shell environment (as indicated by VSCODE_CLI). This makes sense because we only need to resolve the shell environment when you run from the dock for example. So I do not think this is related to shell environment resolution at all.

joaomoreno · 2022-06-02T05:55:10Z

So I do not think this is related to shell environment resolution at all.

It definitely feels like shell environment resolution specific because:

I have pnpm installed on Linux via npm install -g pnpm. pnpm works fine in the vscode integrated terminal and standalone terminals.

And:

I did what you suggested, I opened a terminal (with working pnpm) and opened VSCode. The extension now works as intended.

@doubleplusc Can you try code --verbose --force-user-env?

doubleplusc · 2022-06-02T07:01:38Z

@joaomoreno Good news! I added --force-user-env into my .desktop file, and it worked! ESLint is now running. Thanks for your help.

Is this something that should be fixed in VSCode or the downstream packaging?

bpasero · 2022-06-02T08:09:55Z

@doubleplusc to clarify, when you reported the output where VSCODE_CLI is set, how do you launch VSCode in that case? From the command line? And if so, anything special about the command line?

doubleplusc · 2022-06-02T14:59:55Z

@bpasero I launch via my application menu, it's the only time I get the error. Below is the .desktop file used by the application menu, everything came with the install except for Terminal=true and --verbose --force-user-env.
The terminal is xfce4-terminal on a Arch-based distro. I'm using VSCodium, but I was able to reproduce the issue with a fresh install of VSCode as well. I have not personally changed any terminal configurations.

[Desktop Entry]
Version=1.1
Type=Application
Name=VSCodium
GenericName=Text Editor
Comment=Code Editing. Redefined.
Icon=vscodium
Exec=/opt/vscodium-bin/bin/codium --verbose --force-user-env --unity-launch %F
Terminal=true
Actions=new-empty-window;
MimeType=text/plain;inode/directory;
Categories=Development;IDE;
Keywords=vscode;
StartupNotify=true
StartupWMClass=VSCodium

[Desktop Action new-empty-window]
Name=New Empty Window
Exec=/opt/vscodium-bin/bin/codium --no-sandbox --new-window %F

.desktop file for VSCode:

[Desktop Entry]
Version=1.1
Type=Application
Name=Visual Studio Code
GenericName=Text Editor
Comment=Code Editing. Refined.
Icon=visual-studio-code
Exec=/usr/bin/code --verbose --force-user-env --unity-launch %F
Terminal=true
Actions=new-empty-window;
MimeType=text/plain;inode/directory;application/x-visual-studio-code-workspace;
Categories=Development;IDE;TextEditor;
Keywords=vscode;
StartupWMClass=Code

[Desktop Action new-empty-window]
Name=New Empty Window
Exec=/usr/bin/code --no-sandbox --new-window %F

joaomoreno · 2022-06-02T15:38:07Z

What does /usr/bin/code point to? Is it a symlink?

doubleplusc · 2022-06-02T15:45:20Z

It's a shell script.

#!/bin/bash

XDG_CONFIG_HOME=${XDG_CONFIG_HOME:-~/.config}

# Allow users to override command-line options
if [[ -f $XDG_CONFIG_HOME/code-flags.conf ]]; then
   CODE_USER_FLAGS="$(sed 's/#.*//' $XDG_CONFIG_HOME/code-flags.conf | tr '\n' ' ')"
fi

# Launch
exec /opt/visual-studio-code/bin/code $CODE_USER_FLAGS "$@"

joaomoreno · 2022-06-08T05:44:29Z

Is VSCODE_CLI perhaps set in your usual user environment?

Can you do one more experiment? Instead of adding --force-user-env to the app launcher, remove it and add --verbose instead. Then, look into the Main logs and search for resolveShellEnv.

doubleplusc · 2022-06-08T17:35:14Z

I don't see VSCODE_CLI in my bash configurations and I've never touched it myself.

The log has only one line with resolveShellEnv this time.

[main 2022-06-08T17:16:53.219Z] resolveShellEnv(): skipped (VSCODE_CLI is set)

joaomoreno · 2022-06-10T09:59:46Z

Alright. I have no clue why in your system you explicitly need --force-user-env, but it mustn't happen to other users otherwise we'd hear a lot more about it. Let's close this for now since you're unblocked. Thanks for your help!

Gastonite · 2022-06-12T07:57:02Z

Hello, from a fresh installation in Ubuntu 22.04, I'm not able to make eslint extension work anymore.

I've the same problem as @doubleplusc, but when I add the --force-user-env flag, nothing changes and the message in output panel is the same:

Uncaught exception received.
Error: Command failed: pnpm root -g
at checkExecSyncError (node:child_process:835:11)
at execSync (node:child_process:909:15)
at node:electron/js2c/asar_bundle:5:12704
at Object.get (/home/user/.vscode-oss/extensions/dbaeumer.vscode-eslint-2.2.2/server/out/eslintServer.js:1:172258)
at /home/user/.vscode-oss/extensions/dbaeumer.vscode-eslint-2.2.2/server/out/eslintServer.js:1:174308
at /home/user/.vscode-oss/extensions/dbaeumer.vscode-eslint-2.2.2/server/out/eslintServer.js:1:174323

FYI it doesn't work when I run it from terminal or from .desktop launcher, and:

node and npm were installed with n 16
pnpm was installed with npm i -g pnpm,

I've been using this tool for a long time and never had any problems, until today, how can I get eslint plugin working again?

Gastonite · 2022-06-12T08:15:32Z

Ok, I solved the problem:

I removed the "eslint.packageManager": "pnpm" line from my settings file and voilà

ifiknew · 2022-06-13T08:31:41Z

run

pnpm root -g
pnpm setup

and restart your vscode may solve this

RafaelVidaurre · 2022-06-21T07:43:23Z

I am getting this issue too, I had to disable "eslint.packageManager": "pnpm" but this causes issues for other team members.

hlspablo · 2022-07-09T13:26:23Z

I had the same error, upgrating VSCode to latest version (1.69) solved the problem

dbaeumer added the info-needed Issue requires more information from poster label May 5, 2022

dbaeumer transferred this issue from microsoft/vscode-eslint May 6, 2022

dbaeumer assigned joaomoreno May 6, 2022

dbaeumer removed the info-needed Issue requires more information from poster label May 6, 2022

joaomoreno added the info-needed Issue requires more information from poster label May 18, 2022

bpasero added the workbench-os-integration Native OS integration issues label Jun 2, 2022

joaomoreno closed this as not planned Won't fix, can't repro, duplicate, stale Jun 10, 2022

github-actions bot locked and limited conversation to collaborators Jul 26, 2022

Extension fails with pnpm command not found #148903

Extension fails with pnpm command not found #148903

Comments

doubleplusc commented May 4, 2022

dbaeumer commented May 5, 2022

doubleplusc commented May 5, 2022

S3bt3r commented May 6, 2022 • edited Loading

dbaeumer commented May 6, 2022

S3bt3r commented May 6, 2022 • edited Loading

dbaeumer commented May 9, 2022

S3bt3r commented May 9, 2022 • edited Loading

darthsoup commented May 9, 2022

S3bt3r commented May 9, 2022

MIchaelJier commented May 18, 2022

joaomoreno commented May 18, 2022

doubleplusc commented May 19, 2022

joaomoreno commented May 20, 2022

doubleplusc commented May 20, 2022

524c commented May 21, 2022 • edited Loading

joaomoreno commented May 23, 2022

devyourcar commented May 23, 2022 • edited Loading

doubleplusc commented May 23, 2022

joaomoreno commented May 24, 2022 • edited Loading

doubleplusc commented May 24, 2022 • edited Loading

kelly-tock commented May 24, 2022

joaomoreno commented May 25, 2022 • edited Loading

doubleplusc commented May 25, 2022

bpasero commented May 27, 2022

doubleplusc commented May 28, 2022

bpasero commented May 29, 2022

joaomoreno commented Jun 2, 2022 • edited Loading

doubleplusc commented Jun 2, 2022

bpasero commented Jun 2, 2022

doubleplusc commented Jun 2, 2022

joaomoreno commented Jun 2, 2022

doubleplusc commented Jun 2, 2022

joaomoreno commented Jun 8, 2022 • edited Loading

doubleplusc commented Jun 8, 2022

joaomoreno commented Jun 10, 2022

Gastonite commented Jun 12, 2022 • edited Loading

Gastonite commented Jun 12, 2022

ifiknew commented Jun 13, 2022

RafaelVidaurre commented Jun 21, 2022

hlspablo commented Jul 9, 2022 • edited Loading

S3bt3r commented May 6, 2022 •

edited

Loading

S3bt3r commented May 6, 2022 •

edited

Loading

S3bt3r commented May 9, 2022 •

edited

Loading

524c commented May 21, 2022 •

edited

Loading

devyourcar commented May 23, 2022 •

edited

Loading

joaomoreno commented May 24, 2022 •

edited

Loading

doubleplusc commented May 24, 2022 •

edited

Loading

joaomoreno commented May 25, 2022 •

edited

Loading

joaomoreno commented Jun 2, 2022 •

edited

Loading

joaomoreno commented Jun 8, 2022 •

edited

Loading

Gastonite commented Jun 12, 2022 •

edited

Loading

hlspablo commented Jul 9, 2022 •

edited

Loading