Module not found: Error: Can't resolve '@material-ui/core' and '@material-ui/icons' #2762

jakub-astrahit · 2022-03-13T09:24:19Z

Description

When I use rjsf out-of-the-box, right after installation I get some unnecessary warnings in the console.

Steps to Reproduce

Import form for MUI version 5.
Observe warnings in the console.

Expected behavior

No warnings.

Actual behavior

I use rjsf as follows with Material UI version 5.

import { MuiForm5 as Form } from '@rjsf/material-ui';
  <Form schema={schema}>
    <></>
  </Form>

That gives me the following warning in the console:

WARNING in ../../node_modules/@rjsf/material-ui/dist/material-ui.esm.js 1139:21-49
Module not found: Error: Can't resolve '@material-ui/core' in '/... ... .../node_modules/@rjsf/material-ui/dist'
...
WARNING in ../../node_modules/@rjsf/material-ui/dist/material-ui.esm.js 1140:23-52
Module not found: Error: Can't resolve '@material-ui/icons' in '/... ... .../node_modules/@rjsf/material-ui/dist'

Version

From package.json:

    "@emotion/react": "^11.7.1",
    "@emotion/styled": "^11.6.0",
    "@mui/icons-material": "^5.4.4",
    "@mui/material": "^5.3.1",
    "@rjsf/core": "^4.1.0",
    "@rjsf/material-ui": "^4.1.0",

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

keepeek-rd · 2022-03-14T12:20:44Z

this issue should normally be fixed with version 4.1.0 :( #2721

c0ncentus · 2022-03-15T08:44:25Z

have the same issue

"@material-ui/core": "^4.12.3",
"@material-ui/icons": "^4.11.2",
"@rjsf/core": "^4.1.0",
"@rjsf/material-ui": "^4.1.0",

formatlos · 2022-03-17T14:34:29Z

same issue here
"@mui/core": "5.0.0-alpha.54",
"@mui/icons-material": "^5.4.1",
"@mui/material": "^5.4.1",
"@rjsf/core": "^4.1.0",
"@rjsf/material-ui": "^4.1.0",
"typescript": "^4.5.5"

ggmartins091 · 2022-03-17T19:05:43Z

Not to spam, but I'm having the same issue.

"@emotion/react": "^11.8.1",
"@emotion/styled": "^11.8.1",
"@mui/icons-material": "^5.4.4",
"@mui/lab": "^5.0.0-alpha.71",
"@mui/material": "^5.4.4",
"@mui/styles": "^5.4.4",
"@rjsf/core": "^4.1.0",
"@rjsf/material-ui": "^4.1.0",

joriswitteman · 2022-03-23T13:03:55Z

Same issue when trying to use RJSF 4 with MaterialUI 4.

    "@material-ui/core": "^4.12.3",
    "@material-ui/icons": "^4.11.2",
    "@rjsf/core": "^4.1.0",
    "@rjsf/material-ui": "^4.1.0",

aiibe · 2022-03-28T15:17:31Z

Issues listed above from other users still persisted on version 4.1.1
I am using RJSF with MUIv5

heath-freenome · 2022-03-29T16:38:34Z

This is a known issue with the way Mui 4 and 5 support were built to be side-by-side. There are webpack tricks that can be used to eliminate the warnings.

Webpack 5

Add the following in your webpack.config.js to eliminate the errors for Material-UI v5 when you are only using v4:

// Have webpack 5 set the fallbacks for the resolver for Mui 5 to be false
config.resolve.fallback = { '@mui/material': false, '@mui/icons-material': false };

Add the following in your webpack.config.js to eliminate the errors for Material-UI v4 when you are only using v5:

// Have webpack 5 set the fallbacks for the resolver for Mui 4 to be false
config.resolve.fallback = { '@material-ui/core': false, '@material-ui/icons': false };

Webpack 4

Add the following in your webpack.config.js to eliminate the errors for Material-UI v5 when you are only using v4:

// Alias Material-ui 5 to be Material-ui 4
config.resolve.alias['@mui/material'] = require.resolve('@material-ui/core');
config.resolve.alias['@mui/icons-material'] = require.resolve('@material-ui/icons');

Add the following in your webpack.config.js to eliminate the errors for Material-UI v4 when you are only using v5:

// Alias Material-ui 4 to be Material-ui 5
config.resolve.alias['@material-ui/core'] = require.resolve('@mui/material');
config.resolve.alias['@material-ui/icons'] = require.resolve('@mui/icons-material');

aiibe · 2022-03-30T11:58:15Z

Sadly, React projects initiated with CRA cannot access to Webpack config without ejecting or editing webpack.config.js directly in node_modules.

epicfaace · 2022-03-30T13:30:34Z

@heath-freenome are there ways we can change the require imports in https://github.com/rjsf-team/react-jsonschema-form/blob/master/packages/material-ui/src/Theme5/Mui5Context.tsx and https://github.com/rjsf-team/react-jsonschema-form/blob/master/packages/material-ui/src/Theme/MaterialUIContext.tsx so that they don't give the errors by default? For example, see:

This might also be a solution -- using __webpack_is_included__ -- webpack/webpack#8838 (comment) ???

szubster · 2022-03-31T07:33:33Z

Maybe the material-ui module should be splitted into three different modules? common, material v4 and material v5?

benjdlambert · 2022-03-31T14:25:47Z

This is a known issue with the way Mui 4 and 5 support were built to be side-by-side. There are webpack tricks that can be used to eliminate the warnings.

@heath-freenome is this something that is going to be addressed? Not sure that the webpack bundling hacks are going to work for larger projects.

formatlos · 2022-03-31T14:49:49Z

not to forget that not everybody is using webpack.

there's a discussion on stackoverflow how to handle optional peer dependencies, maybe some of the solutions is sufficient here as well https://stackoverflow.com/questions/54392809/how-do-i-handle-optional-peer-dependencies-when-publishing-a-typescript-package

szubster · 2022-03-31T15:03:51Z

Also, if we move out of dist directory and switch typings in package.json to just ./index.d.ts we should be able to import @rjsf/material-ui/MuiForm not whole @rjsf/material-ui/. Similar to how material-ui packages do.
Are we able to do such change?

MatthewWid · 2022-04-07T06:23:30Z

This is breaking our builds when we are building with Vite for production.

We receive in the DOM:

WARNING: @mui/material or @mui/icons-material is not available

And in the console:

ReferenceError: require is not defined

This occurs whether we import the CommonJS distribution or the ESM distribution. Inspecting the ESM distribution's bundled code you can see that oddly it still includes CommonJS require statements to pull in the Material-UI components individually:

// material-ui.esm.js

try {
  // core
  Box$1 = /*#__PURE__*/require('@mui/material/Box').default;
  Button$1 = /*#__PURE__*/require('@mui/material/Button').default;
  Checkbox$1 = /*#__PURE__*/require('@mui/material/Checkbox').default;
  Divider$1 = /*#__PURE__*/require('@mui/material/Divider').default;
  FormControl$1 = /*#__PURE__*/require('@mui/material/FormControl').default;
  FormControlLabel$1 = /*#__PURE__*/require('@mui/material/FormControlLabel').default;
  FormGroup$1 = /*#__PURE__*/require('@mui/material/FormGroup').default;
  FormHelperText$1 = /*#__PURE__*/require('@mui/material/FormHelperText').default;
  FormLabel$1 = /*#__PURE__*/require('@mui/material/FormLabel').default;
  Grid$1 = /*#__PURE__*/require('@mui/material/Grid').default;
  IconButton$1 = /*#__PURE__*/require('@mui/material/IconButton').default;
  Input$1 = /*#__PURE__*/require('@mui/material/OutlinedInput').default;
  InputLabel$1 = /*#__PURE__*/require('@mui/material/InputLabel').default;
  List$1 = /*#__PURE__*/require('@mui/material/List').default;
  ListItem$1 = /*#__PURE__*/require('@mui/material/ListItem').default;
  ListItemIcon$1 = /*#__PURE__*/require('@mui/material/ListItemIcon').default;
  ListItemText$1 = /*#__PURE__*/require('@mui/material/ListItemText').default;
  MenuItem$1 = /*#__PURE__*/require('@mui/material/MenuItem').default;
  Paper$1 = /*#__PURE__*/require('@mui/material/Paper').default;
  Radio$1 = /*#__PURE__*/require('@mui/material/Radio').default;
  RadioGroup$1 = /*#__PURE__*/require('@mui/material/RadioGroup').default;
  Slider$1 = /*#__PURE__*/require('@mui/material/Slider').default;
  TextField$1 = /*#__PURE__*/require('@mui/material/TextField').default;
  Typography$1 = /*#__PURE__*/require('@mui/material/Typography').default; // icons

  AddIcon$1 = /*#__PURE__*/require('@mui/icons-material/Add').default;
  ArrowDownwardIcon$1 = /*#__PURE__*/require('@mui/icons-material/ArrowDownward').default;
  ArrowUpwardIcon$1 = /*#__PURE__*/require('@mui/icons-material/ArrowUpward').default;
  ErrorIcon$1 = /*#__PURE__*/require('@mui/icons-material/Error').default;
  RemoveIcon$1 = /*#__PURE__*/require('@mui/icons-material/Remove').default;
} catch (_unused) {// no-op
}

Which is causing errors for us as they are not transformed by our build system because it does not assume CommonJS syntax to be present.

We are using Vite v2.8.0 and RJSF /core and /material-ui v4.1.1 but this issue still seems to occur for any version past v4.0.0.

epicfaace · 2022-04-08T02:20:57Z

We'll be discussing this issue further in the next synchronous meeting: https://docs.google.com/document/d/12PjTvv21k6LIky6bNQVnsplMLLnmEuypTLQF8a-8Wss/edit

MatiasCiccone · 2022-04-08T17:33:53Z

Sadly, React projects initiated with CRA cannot access to Webpack config without ejecting or editing webpack.config.js directly in node_modules.

@szubster have you checked https://www.npmjs.com/package/react-app-rewired? I hope that helps you

aiibe · 2022-04-08T17:38:24Z

Sadly, React projects initiated with CRA cannot access to Webpack config without ejecting or editing webpack.config.js directly in node_modules.

@szubster have you checked https://www.npmjs.com/package/react-app-rewired? I hope that helps you

I had already checked that lib. But I’d nice to avoid more deps. Thanks btw.

szubster · 2022-04-08T17:46:58Z

@MatiasCiccone We are not using CRA. We use backstage.

MatiasCiccone · 2022-04-08T18:57:18Z

@MatiasCiccone We are not using CRA. We use backstage.

my bad, I was reading @aiibe message and replied to you.

Sadly, React projects initiated with CRA cannot access to Webpack config without ejecting or editing webpack.config.js directly in node_modules.

@aiibe have you checked react-app-rewired?

szubster · 2022-04-11T14:39:51Z

@epicfaace Any conclusions after synchronous meeting?

epicfaace · 2022-04-11T14:41:07Z

I'm checking with some other library authors to see if there are other, more recommended ways, to include optional dependencies that avoid these problems.

Otherwise, we will just have to split @rjsf/material-ui into two libraries.

dheeraj1447 · 2022-04-12T17:30:56Z

I'm checking with some other library authors to see if there are other, more recommended ways, to include optional dependencies that avoid these problems.

Otherwise, we will just have to split @rjsf/material-ui into two libraries.

Can this be done soon?

epicfaace · 2022-04-15T14:44:36Z

Another option is to have @rjsf/material-ui/4 and @rjsf/material-ui/5. wdyt @heath-freenome ?

ggmartins091 · 2022-05-09T20:49:18Z

That seems to indicate that your production build isn't resolving the imports for mui 5... I'd start there

What does your import of @rjsf/material-ui look like?

I've tried both Form from @rjsf/material-ui/v5 and the withTheme approach aswell:
import { IChangeEvent, withTheme } from '@rjsf/core';
import { Theme } from '@rjsf/material-ui/v5';
const Form = withTheme(Theme);
Both work locally, but when using a production build I see that warning instead of the form.
That seems to indicate that your production build isn't resolving the imports for mui 5... I'd start there

Could please you point me somewhere here? My whole application is based on mui, every component uses mui so it is for sure being resolved on production build, is this something specific do rjsf/material-ui/v5 not being able to resolve mui that I should be digging into?

Right now I'm assuming the error I'm seeing comes from here but I don't see why Mui5Context would be empty here, the stuff it imports are the same I'm using on my application.

ggmartins091 · 2022-05-09T22:24:16Z

Just for reference:
I tested creating a project with vite (which is what my application use) and CRA to test this and the CRA build works perfectly, the vite production build on the other hand doesn't.

I'll dig deeper to try and understand it. I'll share anything I find, should be something to do with rollup's configuration.

tobek · 2022-05-22T21:27:47Z

@ggmartins091 your issue might be that module resolution for some other part of your environment/toolchain is not set up to use the rjsf team's workaround. See the typescript/jest configuration adjustments in the readme here: https://github.com/rjsf-team/react-jsonschema-form/blob/master/packages/material-ui/README.md#material-ui-version-5-1 - you may need to do something similar

tobek · 2022-05-22T21:38:47Z

I have run into 2 issues that prevent the implemented workaround from working:

The workaround is not portable. Importing from @rjsf/material-ui/v5 in typescript package A works locally (after I update tsconfig), but when I build package A and import it into app B, I get Module not found: Can't resolve '@rjsf/material-ui/v5' in ... unless I update tsconfig in app B. Package A is an SDK that will be consumed by third parties, who would then also have to update their typescript/jest/etc configurations in order to use it, which is far from ideal.
- Maybe there's some way to configure the build such that apps consuming package A don't have to make any config changes?
It doesn't seem to work with create-react-app typescript projects. When I put the tsconfig adjustments in, they get removed with the message: compilerOptions.paths must not be set (aliased imports are not supported)

viniciusalvess · 2022-05-25T20:40:45Z

I'm having the same issue using v5 and vite.
When I run the project on localhost, everything works as expected. But when I build and deploy the project, I'm getting the warn.

"@emotion/react": "^11.9.0",
    "@emotion/styled": "^11.8.1",
    "@mui/icons-material": "^5.8.0",
    "@mui/material": "^5.8.1",
    "@mui/system": "^5.8.1",
    "@rjsf/core": "^4.2.0",
    "@rjsf/material-ui": "^4.2.0",

viniciusalvess · 2022-05-31T22:49:10Z

@ggmartins091 Any luck building this package with Vite to production?

ggmartins091 · 2022-06-01T14:12:56Z

@ggmartins091 Any luck building this package with Vite to production?

I did some other testing but with no luck. Tbh I haven't had enough time to look at it.

I don't know if this could be it, but this states that rollup (vite's bundler) doesnt support commonjs and, again, I'm not sure, but if that is true, maybe these requires won't work?

Maybe @heath-freenome could comment on this.

I'm really just shooting at the dark here.

Edit:
Just confirmed, it is the require.

This expection is this:
ReferenceError: require is not defined
at material-ui-v5.esm.js:1198:3

MatthewWid · 2022-06-01T14:55:38Z

@viniciusalvess I resolved this by replacing the requires that @ggmartins091 mentions with import statements and then updating the ESM output bundle file to be the main entry-point in the package.json main field, then republishing it as a private package on an internal private registry for use.

I already mentioned the strange use of require in the ESM bundle earlier in this issue and I see that it indeed appears to be the issue at least for building with Vite.

ggmartins091 · 2022-06-01T17:18:42Z

What I did as a temporary fix was using patch-package I changed the requires to import, I don't know if this could cause any side effects but it works for now, until there is further discussion on this topic.

viniciusalvess · 2022-06-02T06:44:27Z

I tried to use patch-package like you @ggmartins091 mentioned, but it still not working. I can change the text of the warning to make sure my changes are being applied and I can see the changes after the deployment. But using require or import, the outcome is the same for me.
This could be because I'm using yarn workspace. When I have some more time I'll continue trying.

viniciusalvess · 2022-06-02T17:09:19Z

I spent some more time on this issue and here is what worked for me.
I followed ggmartins091 steps using patch-package, moved the imports to the beginning of the file and commented out from line 1196 - 1261. Here is my file.
material-ui-v5.esm.zip
.

heath-freenome · 2022-06-03T15:20:33Z

We are planning a v5 that will be a breaking change for many things, including splitting v4 and v5 into separate packages. This work will likely take several months to complete and we are planning a beta for a while. stay tuned

ggmartins091 · 2022-06-03T15:30:03Z

We are planning a v5 that will be a breaking change for many things, including splitting v4 and v5 into separate packages. This work will likely take several months to complete and we are planning a beta for a while. stay tuned

In the meanwhile no intentions on releasing any fixes for this case where commonjs is not supported?

heath-freenome · 2022-06-03T15:35:38Z

We are planning a v5 that will be a breaking change for many things, including splitting v4 and v5 into separate packages. This work will likely take several months to complete and we are planning a beta for a while. stay tuned

In the meanwhile no intentions on releasing any fixes for this case where commonjs is not supported?

Unfortunately most of our resources (primarily me) are focusing on the new v5 version. If you can find a way to update the current one without patch-package then I encourage you to push a PR with them. It appears that the best (and maybe only) fix requires the upcoming v5 breaking change

ggmartins091 · 2022-06-03T15:59:50Z

We are planning a v5 that will be a breaking change for many things, including splitting v4 and v5 into separate packages. This work will likely take several months to complete and we are planning a beta for a while. stay tuned

In the meanwhile no intentions on releasing any fixes for this case where commonjs is not supported?

Unfortunately most of our resources (primarily me) are focusing on the new v5 version. If you can find a way to update the current one without patch-package then I encourage you to push a PR with them. It appears that the best (and maybe only) fix requires the upcoming v5 breaking change

Maybe I'm missing something and if so let me know, please. But wouldn't changing the requires to imports on MUI5Context and MaterialUiContext fix the problem we are discussing on these last comments?

The problem for some of us is that our bundler does not support commonjs, so isn't that a simple fix? Or is there a specific reason for using require there instead of ESM?

heath-freenome · 2022-06-03T16:26:33Z

We are planning a v5 that will be a breaking change for many things, including splitting v4 and v5 into separate packages. This work will likely take several months to complete and we are planning a beta for a while. stay tuned

In the meanwhile no intentions on releasing any fixes for this case where commonjs is not supported?

Unfortunately most of our resources (primarily me) are focusing on the new v5 version. If you can find a way to update the current one without patch-package then I encourage you to push a PR with them. It appears that the best (and maybe only) fix requires the upcoming v5 breaking change

Maybe I'm missing something and if so let me know, please. But wouldn't changing the requires to imports on MUI5Context and MaterialUiContext fix the problem we are discussing on these last comments?

The problem for some of us is that our bundler does not support commonjs, so isn't that a simple fix? Or is there a specific reason for using require there instead of ESM?

Yeah, the require lets us assign variables inside of the try/catch block scope... The es6 rules require imports to be at the top of files and not inside of any programatic scope. Without being inside of the scope, you would be forced to include both of the material-ui 4 and 5 versions at the same time to avoid import resolution issues. This is why, to solve your problem, we need to break apart the two versions. You are welcome to try experimenting with doing what you suggested and making a PR. Maybe you can find a solution that we haven't figured out?

epicfaace · 2022-06-03T16:31:51Z

@ggmartins091 feel free to join one of our weekly meetings https://docs.google.com/document/d/12PjTvv21k6LIky6bNQVnsplMLLnmEuypTLQF8a-8Wss/edit#heading=h.z0qafypqz305 -- it might be easier to discuss this synchronously.

ggmartins091 · 2022-06-03T17:22:01Z

I totally get what you guys are saying about splitting the package into v4 and v5.

I think my point is not focused on the same problem as the problem solved by splitting the package.

My project, unfortunately, has mui and material-ui installed (v4 and v5) already, so the Warning: @mui/core ... error is caused no because I don't have it installed, but because my bundler does not support commonjs.

So even though I have both material 4 and 5 versions installed (which was one of the ways proposed to avoiding the initial problem of this issue), its gives me that warning because of the requires used on the Context files mentioned prior.

heath-freenome · 2022-06-03T17:29:05Z

I totally get what you guys are saying about splitting the package into v4 and v5.

I think my point is not focused on the same problem as the problem solved by splitting the package.

My project, unfortunately, has mui and material-ui installed (v4 and v5) already, so the Warning: @mui/core ... error is caused no because I don't have it installed, but because my bundler does not support commonjs.

So even though I have both material 4 and 5 versions installed (which was one of the ways proposed to avoiding the initial problem of this issue), its gives me that warning because of the requires used on the Context files mentioned prior.

Actually splitting things WILL solve your problem because then we can switch back to imports rather than requires because we won't need to conditionally include only one material-ui. It sounds like not having both versions is causing errors rather than the warnings that webpack generates?

ggmartins091 · 2022-06-03T18:22:22Z

Now I understand the reason why we use requires, to be able to try/catch it when the specific verison isn't installed. For my project that have both versions it should work normally, my only problem was that require doesn't work with my bundler.

So I fell into that catch, not because @material-ui or @mui wasn't installed, but because require isn't defined.

People with the same problem as me should install both material v4 and v5 and use patch-package approach until the package is split into two separate packages.

heath-freenome · 2022-06-03T19:02:56Z

Is it possible to install a library that polyfills the require API for your bundler?

ggmartins091 · 2022-06-03T19:15:45Z

Is it possible to install a library that polyfills the require API for your bundler?

I tried that with no success, I'm pretty sure that should be achievable, I just didn't give that much time, but it is an alternative.

eleloi · 2022-06-29T09:17:40Z

I spent some more time on this issue and here is what worked for me.
I followed ggmartins091 steps using patch-package, moved the imports to the beginning of the file and commented out from line 1196 - 1261. Here is my file.
material-ui-v5.esm.zip
.

Thank you! That save my project. Could this no be a PR?

heath-freenome · 2022-06-29T16:11:01Z

There is a plan to fix this differently in the upcoming @rjsf v5 version. Stay tuned

izziaraffaele · 2022-07-11T05:01:53Z

I had the same issue with a monorepo setup and the tsconfig suggested in the README wasn't working. Tried pointing to the root node_modules folder and it worked.

{
  ...
  "compilerOptions": {
    ...
    "baseUrl": ".",
    "paths": {
      "@rjsf/material-ui/*": ["../../node_modules/@rjsf/material-ui/dist/*"]
    }
  }
}

heath-freenome · 2022-08-28T17:12:37Z

Fixed in the v5 beta by separating out material ui 5 into its own @rjsf/mui theme. See the 5.x migration guide

lucaswiman · 2022-12-01T00:59:39Z

Just a note that if anyone is coming to this page for the error Failed to resolve entry for package "@rjsf/material-ui". The package may have incorrect main/module/exports specified in its package.json. when trying to follow the contributor's guide, it seems that it just takes a while to compile and yields that error before it compiles.

jakub-astrahit changed the title ~~Module not found: Error: Can't resolve '@material-ui/icons'~~ Module not found: Error: Can't resolve '@material-ui/core' and '@material-ui/icons' Mar 13, 2022

joriswitteman mentioned this issue Mar 23, 2022

Errors with version 4.0 and material-ui 4 #2721

Closed

heath-freenome mentioned this issue Mar 29, 2022

MaterialUIContextProps and Mui5ContextProps not exported #2763

Closed

kachkaev mentioned this issue Mar 29, 2022

Fix false-positive MUI import warnings hashintel/hash#441

Merged

benjdlambert mentioned this issue Mar 31, 2022

Upgrade @rjsf to version 4 backstage/backstage#9852

Closed

5 tasks

jacqueswho added question material-ui material-ui related theme issue labels Apr 7, 2022

kjkent mentioned this issue May 16, 2022

Update @rjsf/material-ui import instructions on Read the Docs #2858

Closed

4 tasks

rupaltotale mentioned this issue Aug 5, 2022

feat(frontend): Add Personal Info route and page using dynamic form element (#43) hack4impact-calpoly/general-vms#60

Merged

heath-freenome closed this as completed Aug 28, 2022

Module not found: Error: Can't resolve '@material-ui/core' and '@material-ui/icons' #2762

Module not found: Error: Can't resolve '@material-ui/core' and '@material-ui/icons' #2762

Comments

jakub-astrahit commented Mar 13, 2022 • edited

Description

Steps to Reproduce

Expected behavior

Actual behavior

Version

keepeek-rd commented Mar 14, 2022

c0ncentus commented Mar 15, 2022

formatlos commented Mar 17, 2022

ggmartins091 commented Mar 17, 2022 • edited

joriswitteman commented Mar 23, 2022

aiibe commented Mar 28, 2022 • edited

heath-freenome commented Mar 29, 2022

Webpack 5

Webpack 4

aiibe commented Mar 30, 2022

epicfaace commented Mar 30, 2022

szubster commented Mar 31, 2022

benjdlambert commented Mar 31, 2022

formatlos commented Mar 31, 2022

szubster commented Mar 31, 2022

MatthewWid commented Apr 7, 2022 • edited

epicfaace commented Apr 8, 2022

MatiasCiccone commented Apr 8, 2022

aiibe commented Apr 8, 2022

szubster commented Apr 8, 2022

MatiasCiccone commented Apr 8, 2022

szubster commented Apr 11, 2022

epicfaace commented Apr 11, 2022

dheeraj1447 commented Apr 12, 2022

epicfaace commented Apr 15, 2022

ggmartins091 commented May 9, 2022 • edited

ggmartins091 commented May 9, 2022 • edited

tobek commented May 22, 2022

tobek commented May 22, 2022

viniciusalvess commented May 25, 2022

viniciusalvess commented May 31, 2022

ggmartins091 commented Jun 1, 2022 • edited

MatthewWid commented Jun 1, 2022 • edited

ggmartins091 commented Jun 1, 2022

viniciusalvess commented Jun 2, 2022

viniciusalvess commented Jun 2, 2022

heath-freenome commented Jun 3, 2022

ggmartins091 commented Jun 3, 2022 • edited

heath-freenome commented Jun 3, 2022 • edited

ggmartins091 commented Jun 3, 2022

heath-freenome commented Jun 3, 2022

epicfaace commented Jun 3, 2022

ggmartins091 commented Jun 3, 2022

heath-freenome commented Jun 3, 2022

ggmartins091 commented Jun 3, 2022 • edited

heath-freenome commented Jun 3, 2022

ggmartins091 commented Jun 3, 2022

eleloi commented Jun 29, 2022

heath-freenome commented Jun 29, 2022

izziaraffaele commented Jul 11, 2022

heath-freenome commented Aug 28, 2022

lucaswiman commented Dec 1, 2022

jakub-astrahit commented Mar 13, 2022 •

edited

ggmartins091 commented Mar 17, 2022 •

edited

aiibe commented Mar 28, 2022 •

edited

MatthewWid commented Apr 7, 2022 •

edited

ggmartins091 commented May 9, 2022 •

edited

ggmartins091 commented May 9, 2022 •

edited

ggmartins091 commented Jun 1, 2022 •

edited

MatthewWid commented Jun 1, 2022 •

edited

ggmartins091 commented Jun 3, 2022 •

edited

heath-freenome commented Jun 3, 2022 •

edited

ggmartins091 commented Jun 3, 2022 •

edited