Error: Cannot read property 'hashReferences' of undefined #4145

kevincox · 2020-02-16T11:17:52Z

🐛 bug report

When adding a synchronous dependency I get the following error:

 🚨 Build failed.
Error: Cannot read property 'hashReferences' of undefined
TypeError: Cannot read property 'hashReferences' of undefined
    at getBundlesIncludedInHash (/builds/kevincox/playerone/node_modules/@parcel/core/lib/PackagerRunner.js:455:47)
    at getBundlesIncludedInHash (/builds/kevincox/playerone/node_modules/@parcel/core/lib/PackagerRunner.js:459:24)
    at getBundlesIncludedInHash (/builds/kevincox/playerone/node_modules/@parcel/core/lib/PackagerRunner.js:459:24)
    at assignComplexNameHashes (/builds/kevincox/playerone/node_modules/@parcel/core/lib/PackagerRunner.js:447:27)
    at PackagerRunner.writeBundles (/builds/kevincox/playerone/node_modules/@parcel/core/lib/PackagerRunner.js:101:5)
    at process._tickCallback (internal/process/next_tick.js:68:7)

🎛 Configuration (.babelrc, package.json, cli command)

All the state can be see in https://gitlab.com/kevincox/playerone/-/merge_requests/1.

In that PR I attempt to remove the workaround (using async imports) and you can see that it fails to build.

🤔 Expected Behavior

The build should work as intended.

💁 Possible Solution

This may be related to the fact that this library is imported from two places. The current graph looks like this (when experiencing the bug).

main.js
- sync ga.js
- async options.js
options.js
- sync ga.js

Software	Version(s)
Parcel	2.0.0-nightly.113
Node	v13.8.0
npm	6.13.6
Operating System	Linux

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

mischnic · 2020-02-16T11:57:59Z

Could you try again with the latest parcel@nightly release? The hashing system was recently overhauled.

kevincox · 2020-02-16T12:10:55Z

Same issue.

% npx parcel --version
2.0.0-nightly.113
% npx parcel build --no-cache -- src/index.pug
🚨 Build failed.
Error: Cannot read property 'hashReferences' of undefined
TypeError: Cannot read property 'hashReferences' of undefined
    at getBundlesIncludedInHash (/home/kevincox/p/playerone/node_modules/@parcel/core/lib/PackagerRunner.js:455:47)
    at getBundlesIncludedInHash (/home/kevincox/p/playerone/node_modules/@parcel/core/lib/PackagerRunner.js:459:7)
    at getBundlesIncludedInHash (/home/kevincox/p/playerone/node_modules/@parcel/core/lib/PackagerRunner.js:459:7)
    at assignComplexNameHashes (/home/kevincox/p/playerone/node_modules/@parcel/core/lib/PackagerRunner.js:447:31)
    at PackagerRunner.writeBundles (/home/kevincox/p/playerone/node_modules/@parcel/core/lib/PackagerRunner.js:101:5)
    at async Parcel.build (/home/kevincox/p/playerone/node_modules/@parcel/core/lib/Parcel.js:376:7)
    at async Parcel.run (/home/kevincox/p/playerone/node_modules/@parcel/core/lib/Parcel.js:253:18)
    at async Command.run (/home/kevincox/p/playerone/node_modules/parcel/lib/cli.js:190:7)

Banou26 · 2020-02-19T13:57:21Z

This error happens practically if not every time you change a configuration property from the package.json or elsewhere.
To fix it most of the time just deleting the cache folder seems to fix it for me.
Not sure why it's doing that for you because you have the --no-cache flag.

kevincox · 2020-02-19T14:07:15Z

To be honest I've been in the habit of removing the cache after every build as it seems to cause a lot of issues. So cache definitely isn't the problem here.

padmaia · 2020-02-20T02:16:58Z

Thanks for having an easily reproducible example @kevincox! I've opened a PR that I believe should solve this issue. Temporarily, it looks like building with --no-scope-hoist resolves the issue until a fix is merged.

padmaia · 2020-02-20T03:21:27Z

@Banou26 I think what you are referring to may be fixed by #4189, so keep an eye out on that one.

ubershmekel · 2020-06-02T11:24:46Z

I think I'm getting this error when my package.json has an invalid "main" field. Though I'm not sure what parcel considers valid. I'm just pointing my main at "main": "dist/index.html" which doesn't work while "main": "index.html" which unfortunately overwrites my real main file does complete a build.

× Build failed.
Error: Cannot read property 'hashReferences' of undefined
TypeError: Cannot read property 'hashReferences' of undefined
    at getBundlesIncludedInHash (C:\Users\yuv\Downloads\gfloyd-backup\gh-website\node_modules\@parcel\core\lib\PackagerRunner.js:490:47)
    at getBundlesIncludedInHash (C:\Users\yuv\Downloads\gfloyd-backup\gh-website\node_modules\@parcel\core\lib\PackagerRunner.js:494:7)
    at getBundlesIncludedInHash (C:\Users\yuv\Downloads\gfloyd-backup\gh-website\node_modules\@parcel\core\lib\PackagerRunner.js:494:7)
    at assignComplexNameHashes (C:\Users\yuv\Downloads\gfloyd-backup\gh-website\node_modules\@parcel\core\lib\PackagerRunner.js:482:31)
    at PackagerRunner.writeBundles (C:\Users\yuv\Downloads\gfloyd-backup\gh-website\node_modules\@parcel\core\lib\PackagerRunner.js:110:5)
    at async Parcel.build (C:\Users\yuv\Downloads\gfloyd-backup\gh-website\node_modules\@parcel\core\lib\Parcel.js:375:7)
    at async Parcel.run (C:\Users\yuv\Downloads\gfloyd-backup\gh-website\node_modules\@parcel\core\lib\Parcel.js:250:18)
    at async Command.run (C:\Users\yuv\Downloads\gfloyd-backup\gh-website\node_modules\parcel\lib\cli.js:155:7)

brettinternet · 2020-07-05T19:25:45Z

I was getting this error on parcel@next (2.0.0-beta.1) using the --dist-dir flag on something like parcel build ./src/index.html --dist-dir=build, but not on parcel@nightly (2.0.0-nightly.322)

mischnic · 2020-07-06T08:42:45Z

Can someone else confirm that this is fixed?

ross-pfahler · 2020-07-08T17:34:10Z

I'm receiving the error when when two builds in a monorepo share the default cache location -- in this case the cache dir is at the root of the repository.

If add --cache-dir=./.parcel-cache to the builds, I can work around the issue.

schlagi123 · 2020-08-06T16:06:36Z

Can someone else confirm that this is fixed?

In the beta I have the same problem. In the version 2.0.0-nightly.358 it works fine.

RPDeshaies · 2020-08-06T17:49:30Z

I'm on 2.0.0-beta.1 and just encountered the issue in my bitbucket pipeline build

I have a similar structure as @ross-pfahler (monorepo with two packages build built by parcel at the same time)

Haven't tried 2.0.0-nigthly.3658 though

cifkao · 2020-08-15T17:18:36Z

I'm getting this error with 2.0.0-nightly.366. EDIT: --no-scope-hoist solves the problem for me.

In my case it happens when I try to import a file using a named pipeline, e.g. import css from 'bundle-text:./style.css', and only when I try to build a JS target. When referencing the JS file from HTML, the error does not occur.

cifkao · 2020-08-15T17:39:36Z

It would be great to at least display a more informative error message (showing which bundle is referenced that is not found).

mischnic · 2020-08-15T19:21:32Z

In my case it happens when I try to import a file using a named pipeline, e.g. import css from 'bundle-text:./style.css', and only when I try to build a JS target. When referencing the JS file from HTML, the error does not occur.

Can you reproduce this consistently? Could you provide a full code sample?

It would be great to at least display a more informative error message (showing which bundle is referenced that is not found).

We should rather fix the bug itself....

cifkao · 2020-08-15T20:59:13Z

Can you reproduce this consistently? Could you provide a full code sample?

Sure: https://gist.github.com/cifkao/badeda38164e362a147b571053920520

parcel serve index.html works fine (the CSS file contents get printed onto the console), but parcel build index.js fails with this error.

parcel-bundler/parcel#4145

mischnic · 2020-08-17T10:49:07Z

At least in @cifkao's example, this is caused by inline bundles not being processed (as they shouldn't)

parcel/packages/core/core/src/PackagerRunner.js

Line 116 in 64ebc37

let bundles = bundleGraph.getBundles().filter(bundle => !bundle.isInline);

so bundleInfoMap[someInlineBundle.id] is undefiend.
But they are still listed in the hashReferences of their parent bundles:

parcel/packages/core/core/src/PackagerRunner.js

Line 658 in 64ebc37

for (let hashRef of bundleInfoMap[bundleId].hashReferences) {

and then bundleInfoMap[someInlineBundle.id].hashReferences fails. I'm not quite sure if they should just be skipped or handled in some other way.

dgkimpton · 2020-08-20T21:29:13Z

I also get this error now too, but with JS instead of CSS.

What seems to have triggered it for me is using ES6 static imports from inside an ES6 dynamic import which I had also imported in the document itself.

The following minimal example reproduces:

{edit} as a gist: https://gist.github.com/dgkimpton/278657a777eb898075b9551ff38606c2

package.json

{
 "name": "parcel-test",
 "version": "1.0.0",
 "scripts": {
  "assemble": "parcel build index.html"
 },
 "devDependencies": {
  "parcel": "^2.0.0-nightly.372"
 }
}

index.html

<!DOCTYPE html>
<html>
<body>
	<script type="module">
		import { something } from './othermodule.mjs';
		document.addEventListener('load', () => {
			something();
			import('./module.mjs').then((m) => m.doStuff());
		});
	</script>
</body>
</html>

module.mjs

import { something } from './othermodule.mjs';

export function doStuff() {
	something();
}

othermodule.mjs

export function something() {
	console.warn('hmmm');
}

Software	Version(s)
Parcel	[email protected]
Node	v14.4.0
npm	6.14.5
Operating System	Windows 10/git bash

npm run assemble

� Build failed.
Error: Cannot read property 'hashReferences' of undefined
TypeError: Cannot read property 'hashReferences' of undefined
    at getBundlesIncludedInHash (E:\code\web\parcel-error\node_modules\@parcel\core\lib\PackagerRunner.js:529:47)
    at getBundlesIncludedInHash (E:\code\web\parcel-error\node_modules\@parcel\core\lib\PackagerRunner.js:533:7)
    at getBundlesIncludedInHash (E:\code\web\parcel-error\node_modules\@parcel\core\lib\PackagerRunner.js:533:7)
    at assignComplexNameHashes (E:\code\web\parcel-error\node_modules\@parcel\core\lib\PackagerRunner.js:521:31)
    at PackagerRunner.writeBundles (E:\code\web\parcel-error\node_modules\@parcel\core\lib\PackagerRunner.js:112:5)
    at async Parcel.build (E:\code\web\parcel-error\node_modules\@parcel\core\lib\Parcel.js:398:7)
    at async Parcel.run (E:\code\web\parcel-error\node_modules\@parcel\core\lib\Parcel.js:273:18)
    at async Command.run (E:\code\web\parcel-error\node_modules\parcel\lib\cli.js:234:7)

SpeedySH · 2020-08-25T08:03:47Z

I also get this error now too, but with JS instead of CSS.

What seems to have triggered it for me is using ES6 static imports from inside an ES6 dynamic import which I had also imported in the document itself.

The following minimal example reproduces:

{edit} as a gist: https://gist.github.com/dgkimpton/278657a777eb898075b9551ff38606c2

package.json

{
 "name": "parcel-test",
 "version": "1.0.0",
 "scripts": {
  "assemble": "parcel build index.html"
 },
 "devDependencies": {
  "parcel": "^2.0.0-nightly.372"
 }
}

index.html

<!DOCTYPE html>
<html>
<body>
	<script type="module">
		import { something } from './othermodule.mjs';
		document.addEventListener('load', () => {
			something();
			import('./module.mjs').then((m) => m.doStuff());
		});
	</script>
</body>
</html>

module.mjs

import { something } from './othermodule.mjs';

export function doStuff() {
	something();
}

othermodule.mjs

export function something() {
	console.warn('hmmm');
}

Software Version(s)
Parcel [email protected]
Node v14.4.0
npm 6.14.5
Operating System Windows 10/git bash

npm run assemble

� Build failed.
Error: Cannot read property 'hashReferences' of undefined
TypeError: Cannot read property 'hashReferences' of undefined
    at getBundlesIncludedInHash (E:\code\web\parcel-error\node_modules\@parcel\core\lib\PackagerRunner.js:529:47)
    at getBundlesIncludedInHash (E:\code\web\parcel-error\node_modules\@parcel\core\lib\PackagerRunner.js:533:7)
    at getBundlesIncludedInHash (E:\code\web\parcel-error\node_modules\@parcel\core\lib\PackagerRunner.js:533:7)
    at assignComplexNameHashes (E:\code\web\parcel-error\node_modules\@parcel\core\lib\PackagerRunner.js:521:31)
    at PackagerRunner.writeBundles (E:\code\web\parcel-error\node_modules\@parcel\core\lib\PackagerRunner.js:112:5)
    at async Parcel.build (E:\code\web\parcel-error\node_modules\@parcel\core\lib\Parcel.js:398:7)
    at async Parcel.run (E:\code\web\parcel-error\node_modules\@parcel\core\lib\Parcel.js:273:18)
    at async Command.run (E:\code\web\parcel-error\node_modules\parcel\lib\cli.js:234:7)

Yep this my problem too, i think we can't use ES6 Export/Import in Parcel. Feels Bad. Do you have any solution for this stuff?

arb000r · 2020-08-30T10:21:29Z

Also bumping this as an issue I am experiencing. Seems to be when main is unset in package.json?

EDIT: Latest nightly is working

jeffpeck10x · 2021-02-11T01:02:55Z

I just encountered this (on 2.0.0-nightly.573+31f431d9) and the --no-scope-hoist suggestion fixed it, although I am not clear what introduced it. I am importing svg's, which is possibly related? 🤷

mischnic · 2021-02-25T19:40:26Z

Another reproduction:

<script type="module">
  import * as b from "./b.js";
  console.log(b);
</script>
<script src="./a.js" type="module"></script>

// a.js
import * as b from "./b.js";
console.log(b);

// b.js
export const a = 1;

artemjackson · 2021-02-26T15:14:09Z

If building for ESM there is no solution or workaround :(
Meanwhile the issue got one year old 🎉

ghost · 2021-06-16T01:22:17Z

I have a build where src/navbar.tsx is the entry point. This gets compiled to dist/navbar.js. I was getting the hashReferences error.

I had in my package.json:

{
  "main": "./dist/navbar.js",
}

When I remove the main: property from my package.json, the error goes away and my bundle works correctly (without --no-cache and --no-scope-hoist). Same error when using module: Hopefully this information might be of use.

devongovett · 2021-07-09T06:12:25Z

I can't reproduce with @mischnic's case in the latest nightly anymore. @GrantAtStreamba what version of Parcel are you using and do you have any more details on what could reproduce it?

devongovett · 2021-07-25T22:06:24Z

Going to close this since it seems to be working now. If you manage to reproduce it still, please let us know.

kevincox · 2021-10-14T12:16:23Z

The original case is still present https://gitlab.com/kevincox/playerone/-/merge_requests/1. I have rebased the example against Parcel 2.0.0.

I have also found a new case on Parcel 2.0.0 that worked previously. https://gitlab.com/kevincox/playerone/-/merge_requests/65 which appears to be triggered by this import https://gitlab.com/kevincox/playerone/-/blob/72879318ae5db83cb3174871e50b281c297a5b95/src/a/options.ts#L1

danieltroger · 2022-01-31T16:38:28Z

Also experiencing this issue when trying to workaround #7609 by using bundle-text: instead :(

🚨 Build failed.

Error: Cannot read properties of undefined (reading 'hashReferences')

  TypeError: Cannot read properties of undefined (reading 'hashReferences')
  at getBundlesIncludedInHash ([project_dir]/.yarn/cache/@parcel-core-npm-2.2.1-62c0c81716-f06b61c184.zip/node_modules/@parcel/core/lib/requests/WriteBundlesRequest.js:147:47)
  at getBundlesIncludedInHash ([project_dir]/.yarn/cache/@parcel-core-npm-2.2.1-62c0c81716-f06b61c184.zip/node_modules/@parcel/core/lib/requests/WriteBundlesRequest.js:151:7)
  at assignComplexNameHashes ([project_dir]/.yarn/cache/@parcel-core-npm-2.2.1-62c0c81716-f06b61c184.zip/node_modules/@parcel/core/lib/requests/WriteBundlesRequest.js:140:105)
  at Object.run ([project_dir]/.yarn/cache/@parcel-core-npm-2.2.1-62c0c81716-f06b61c184.zip/node_modules/@parcel/core/lib/requests/WriteBundlesRequest.js:115:5)
  at async RequestTracker.runRequest ([project_dir]/.yarn/cache/@parcel-core-npm-2.2.1-62c0c81716-f06b61c184.zip/node_modules/@parcel/core/lib/RequestTracker.js:725:20)
  at async Object.run ([project_dir]/.yarn/cache/@parcel-core-npm-2.2.1-62c0c81716-f06b61c184.zip/node_modules/@parcel/core/lib/requests/ParcelBuildRequest.js:74:20)
  at async RequestTracker.runRequest ([project_dir]/.yarn/cache/@parcel-core-npm-2.2.1-62c0c81716-f06b61c184.zip/node_modules/@parcel/core/lib/RequestTracker.js:725:20)
  at async Parcel._build ([project_dir]/.yarn/cache/@parcel-core-npm-2.2.1-62c0c81716-f06b61c184.zip/node_modules/@parcel/core/lib/Parcel.js:397:11)
  at async Parcel.run ([project_dir]/.yarn/cache/@parcel-core-npm-2.2.1-62c0c81716-f06b61c184.zip/node_modules/@parcel/core/lib/Parcel.js:276:18)
  at async run ([project_dir]/.yarn/cache/parcel-npm-2.2.1-088c07d8bf-081fdc011a.zip/node_modules/parcel/lib/cli.js:374:7)

danieltroger · 2022-01-31T16:41:21Z

For me, falling back to fs.readFileSync worked as an ugly workaround :)

Stvad · 2022-04-29T01:31:54Z

Another confirmation for bundle-text: causing the problem. It used to work for me in 2.3.2, but upon upgrading to 2.5.0 I'm hitting this issue

Stvad · 2022-04-29T02:08:25Z

For me falling back on fs does not work, as I actually want Parcel to process imports in the CSS first =\
shoonia/parcel-transformer-css-to-string#6 does not work for similar reasons =\

Stvad · 2022-04-29T02:26:27Z

Ah interestingly - it only happens in watch mode but not for build, with following configurations. will check what is causing the difference:

	"build": "parcel build source/manifest.json --no-content-hash --no-source-maps --dist-dir distribution --no-cache --detailed-report 0",
	"watch": "parcel watch source/manifest.json --dist-dir distribution --no-cache --no-hmr",

Stvad · 2022-04-29T02:29:54Z

so removing --no-hmr seems to have resolved this for me 🤷‍♂️

Stvad · 2022-05-08T22:38:19Z

But if I were to remove --no-content-hash from the build command, I start hitting this issue in the build command 🙈

calclavia · 2022-05-20T16:06:29Z

Running into the same issue during parcel build. --no-content-hash fixes it.

everdimension · 2022-07-04T11:16:39Z

Same issue
parcel watch works fine, parcel build fails.

I'm using the web-extension config
I am using 'bundle-text:' import at one place

--no-content-hash helped.

[Jul 11, 2022] Update:

The above doesn't really work. It makes the build command finish execution without errors, but the resulting build turns out to be broken.
The issue is with the code surrounding the bundle-text: import. The other (normal) import in the file doesn't seem to work and I get a runtime error:
Cannot find module '81IKK'
(The latter I guess is just a hashed name of a module from node_modules)

avalanche1 · 2022-07-19T18:26:21Z

Has anyone been able to circumvent the issue?
Because the --no-content-hash solution, as stated by @everdimension , doesn't really work.

Stvad · 2022-07-19T18:32:58Z

@everdimension @avalanche1 I think you may be hitting another bug - see #8071

mark-monteiro · 2022-08-29T21:47:07Z

@everdimension @avalanche1 I think you may be hitting another bug - see #8071

For reference, a workaround in the linked issue can be found in this comment. I've also outlines that solution below.

As mentioned in everdimension's comment, adding --no-content-hash removes the build error but introduces a runtime error Cannot find module '#####'. The solution is to specify --no-content-hash and then also disable code splitting by adding the following to your package.json file:

  "@parcel/bundler-default": {
    "minBundles": 10000000,
    "minBundleSize": 3000,
    "maxParallelRequests": 20
  }

Keep in mind that this solution removes code-splitting so you will end up with larger individual files. If you're developing a web extension this is generally not an issue since the files are loaded locally anyways. However, Firefox does have a hard limit of 4MB per file ([1], [2]), which could prevent this solution from working on the Firefox Addons site.

mark-monteiro · 2022-08-29T21:53:05Z

@everdimension @avalanche1 I think you may be hitting another bug - see #8071

For reference, a workaround in the linked issue can be found in this comment. I've also outlined that solution below.

As mentioned in everdimension's comment, adding --no-content-hash removes the build error but introduces a runtime error Cannot find module '#####'. The solution is to specify --no-content-hash and then also disable code splitting by adding the following to your package.json file:

  "@parcel/bundler-default": {
    "minBundles": 10000000,
    "minBundleSize": 3000,
    "maxParallelRequests": 20
  }

Keep in mind that this solution removes code-splitting so you will end up with larger individual files. If you're developing a web extension this is generally not an issue since the files are loaded locally anyways. However, Firefox does have a hard limit of 4MB per file ([1], [2]), which could prevent this solution from working on the Firefox Addons site.

Again, this is all outlined in various comments in the linked issue (#8071), which may the better place to track progress on a fix for this problem.

avalanche1 · 2022-09-04T13:14:02Z

@mischnic Will this get priority?
Jumping through the hoops just to make the basic f-nality work is distressing.

DeMoorJasper added the 🐛 Bug label Feb 16, 2020

mischnic added 🕐 Waiting ✨ Parcel 2 labels Feb 16, 2020

DeMoorJasper added ✔️ Confirmed Bug and removed 🕐 Waiting labels Feb 16, 2020

padmaia mentioned this issue Feb 20, 2020

Use stable ids in names of inline bundles #4188

Closed

1 task

padmaia mentioned this issue Jun 26, 2020

Remove empty bundles and bundle groups #4805

Merged

lgarron added a commit to cubing/cubing.js that referenced this issue Aug 16, 2020

SVG import not working.

1fb32a8

parcel-bundler/parcel#4145

mischnic mentioned this issue Aug 24, 2020

Parcel ignored --dist-dir flag #5063

Closed

ncaq mentioned this issue Oct 15, 2020

[aws-lambda-nodejs] docker build is not working aws/aws-cdk#10881

Closed

mischnic mentioned this issue Jan 29, 2021

Fix 'hashReferences' of undefined for varying referenced bundle resolutions #5736

Merged

mischnic mentioned this issue Feb 19, 2021

parcel build ignores .parcelrc? #5882

Open

Andrew-Dyachenko mentioned this issue Jun 9, 2021

"Name already registered with serializer" with parcel@next #4064

Closed

devongovett added this to the v2.0.0-rc.0 milestone Jul 8, 2021

devongovett closed this as completed Jul 25, 2021

mischnic reopened this Oct 14, 2021

101arrowz mentioned this issue Apr 19, 2022

Webextension fixes #7958

Merged

Stvad mentioned this issue May 9, 2022

Parcel WebExtension fails to bundle modules under some conditions (build + mv2, or mv3 & --no-scope-hoist) #8071

Closed

fregante mentioned this issue Dec 9, 2023

Parcel: Cannot read properties of undefined (reading 'hashReferences') fregante/my-recurrent-errors#6

Open

Error: Cannot read property 'hashReferences' of undefined #4145

Error: Cannot read property 'hashReferences' of undefined #4145

Comments

kevincox commented Feb 16, 2020 • edited by DeMoorJasper Loading

🐛 bug report

🎛 Configuration (.babelrc, package.json, cli command)

🤔 Expected Behavior

💁 Possible Solution

mischnic commented Feb 16, 2020

kevincox commented Feb 16, 2020

Banou26 commented Feb 19, 2020 • edited Loading

kevincox commented Feb 19, 2020 • edited Loading

padmaia commented Feb 20, 2020

padmaia commented Feb 20, 2020

ubershmekel commented Jun 2, 2020

brettinternet commented Jul 5, 2020 • edited Loading

mischnic commented Jul 6, 2020 • edited Loading

ross-pfahler commented Jul 8, 2020 • edited Loading

schlagi123 commented Aug 6, 2020

RPDeshaies commented Aug 6, 2020

cifkao commented Aug 15, 2020 • edited Loading

cifkao commented Aug 15, 2020

mischnic commented Aug 15, 2020

cifkao commented Aug 15, 2020

mischnic commented Aug 17, 2020 • edited Loading

dgkimpton commented Aug 20, 2020 • edited Loading

SpeedySH commented Aug 25, 2020

arb000r commented Aug 30, 2020 • edited Loading

jeffpeck10x commented Feb 11, 2021

mischnic commented Feb 25, 2021

artemjackson commented Feb 26, 2021

ghost commented Jun 16, 2021

devongovett commented Jul 9, 2021

devongovett commented Jul 25, 2021

kevincox commented Oct 14, 2021 • edited Loading

danieltroger commented Jan 31, 2022 • edited Loading

danieltroger commented Jan 31, 2022

Stvad commented Apr 29, 2022

Stvad commented Apr 29, 2022

Stvad commented Apr 29, 2022

Stvad commented Apr 29, 2022

Stvad commented May 8, 2022

calclavia commented May 20, 2022

everdimension commented Jul 4, 2022 • edited Loading

avalanche1 commented Jul 19, 2022

Stvad commented Jul 19, 2022

mark-monteiro commented Aug 29, 2022

mark-monteiro commented Aug 29, 2022 • edited Loading

avalanche1 commented Sep 4, 2022

kevincox commented Feb 16, 2020 •

edited by DeMoorJasper

Loading

Banou26 commented Feb 19, 2020 •

edited

Loading

kevincox commented Feb 19, 2020 •

edited

Loading

brettinternet commented Jul 5, 2020 •

edited

Loading

mischnic commented Jul 6, 2020 •

edited

Loading

ross-pfahler commented Jul 8, 2020 •

edited

Loading

cifkao commented Aug 15, 2020 •

edited

Loading

mischnic commented Aug 17, 2020 •

edited

Loading

dgkimpton commented Aug 20, 2020 •

edited

Loading

arb000r commented Aug 30, 2020 •

edited

Loading

kevincox commented Oct 14, 2021 •

edited

Loading

danieltroger commented Jan 31, 2022 •

edited

Loading

everdimension commented Jul 4, 2022 •

edited

Loading

mark-monteiro commented Aug 29, 2022 •

edited

Loading