Problems with pnpm and the way loaders are resolved #5087

donaldpipowitch · 2017-06-19T06:53:56Z

Do you want to request a feature or report a bug?

bug?

What is the current behavior?

I can't create libs which use webpack and loaders, install these libs with pnpm and try to use them, because the modules can't be found.

It looks like pnpm installs my lib here: /Users/foo/test/ws-pnpm-test/node_modules/.registry.npmjs.org/@mercateo/ws/1.0.2/node_modules/@mercateo/ws.

The loader is here /Users/foo/test/ws-pnpm-test/node_modules/.registry.npmjs.org/string-replace-loader and here /Users/foo/test/ws-pnpm-test/node_modules/.registry.npmjs.org/@mercateo/ws/1.0.2/node_modules/string-replace-loader.

I think webpack only looks here for loaders: /Users/foo/test/ws-pnpm-test/node_modules/string-replace-loader, but this does not exist.

I think webpack resolves loaders in node_modules relative to process.cwd(), but not relative to my lib.

I can't just rewrite my config to something like this:

{
  resolveLoader: {
    modules: [
       // goes up '@mercateo/ws/dist' to match `'/Users/foo/test/ws-pnpm-test/node_modules/.registry.npmjs.org/@mercateo/ws/1.0.2/node_modules/string-replace-loader'`
       // this could lead to different directories, if my lib isn't installed with pnpm
       join(__dirname, '..', '..', '..'),
       // this would match `'/Users/foo/test/ws-pnpm-test/node_modules/.registry.npmjs.org/string-replace-loader'`
       // but I can't be sure, that my users use the official registry and not a private mirror or something like that
       join(process.cwd(), 'node_modules/.registry.npmjs.org'),
      'node_modules'  // default
    ]
  }
}

What is the most robust way to solve this?
Can I specify something like that? resolveLoaders.basedir: __dirname, so all loaders can be resolved relative to my lib?

// cc @zkochan

If the current behavior is a bug, please provide the steps to reproduce.

package.json:

{
  "name": "ws-pnpm-test",
  "version": "1.0.0",
  "private": true,
  "scripts": {
    "ws": "ws"
  },
  "ws": {
    "type": "browser"
  },
  "dependencies": {
    "@mercateo/ws": "^1.0.2"
  }
}

tsconfig.json:

{}

src/index.ts:

console.log('hello');

$ pnpm install
$ npm run -s ws -- build
ERROR in Entry module not found: Error: Can't resolve 'string-replace-loader' in '/Users/foo/test/ws-pnpm-test'

What is the expected behavior?

Build without error.

If this is a feature request, what is motivation or use case for changing the behavior?

Please mention other relevant information such as the browser version, Node.js version, webpack version and Operating System.

Node LTS, Webpack 2.6, pnpm 0.71, Mac OS X.

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

donaldpipowitch · 2017-06-19T07:08:45Z

Maybe I can just use resolveLoaders.modules: [ join(__dirname, '..', '..', '..'), 'node_modules' ]?

If my lib is installed with pnpm the path matches '/Users/foo/test/ws-pnpm-test/node_modules/.registry.npmjs.org/@mercateo/ws/1.0.2/node_modules. For npm and yarn it would match '/Users/foo/test/ws-pnpm-test/node_modules'. Looks okay I guess?

Feel free to close this issue, if this is the intended way.

zkochan · 2017-06-19T07:31:12Z

cc @yegor-sytnyk, @max-devjs

Ref pnpm/pnpm#801

We have issues in lots of applications because webpack can't resolve packages in the node_modules created by pnpm. I think it is because webpack doesn't resolve dependencies the way Node does. Node resolves requires from the real path of a module. That is why the symlink approach pnpm uses works with all Node apps. However, it seems to confuse webpack and some other tools like browserify and eslint.

zkochan · 2017-06-19T07:59:09Z

Also, I believe @andreypopp has looked into these issues in scope of CRA pnpm/pnpm#581

And @vjpr has investigated it a bit

webpack-bot · 2017-12-25T23:02:00Z

This issue had no activity for at least half a year.

It's subject to automatic issue closing if there is no activity in the next 15 days.

andreineculau · 2017-12-26T23:46:36Z

bump

alexander-akait · 2018-06-06T10:56:58Z

Problem still exists? Can you create minimum reproducible test repo?

markerdmann · 2019-02-04T23:48:43Z

I think I'm hitting this issue or something similar in this React project:

https://github.com/dirtprotocol/dirt/tree/master/sampleprojects/sample-web-react

If I install with npm or yarn, everything is fine when I run npm start. If I install with pnpm, I get this error:

/Users/sendrecv/sproj/dirt/packages/lib/dist/services/StaticContractProvider.js
Module not found: Can't resolve '@dirt/contracts' in '/Users/sendrecv/sproj/dirt/packages/lib/dist/services'

mariotee · 2019-02-28T02:47:35Z

i also get a similar issue with pnpm

this webpack.config.js works when i have no node_modules and run npm install
however it does not work when i have no node_modules and run pnpm install

const HtmlWebPackPlugin = require("html-webpack-plugin")
const path = require("path")

const htmlWebpackPlugin = new HtmlWebPackPlugin(
{
  template: "./public/index.html",
  filename: "index.html",
})

module.exports =
{
  entry: ["./src/index.js"],
  devServer: {
    historyApiFallback: true,
    overlay: true,
  },
  resolve: {
    modules: [
      path.resolve(__dirname, "node_modules"),
      path.resolve(__dirname, "src")
    ],
  },
  module: {
    rules: [
      {
        test: /\.js$/,
        exclude: /node_modules/,
        use: {
          loader: "babel-loader",
        },
      },
      {
        test: /\.css$/,
        use: [
          { loader: "style-loader" },
          {
            loader: "css-loader",
            options:
            {
              modules: true,
              importLoaders: 1,
              localIdentName: "[name]_[local]_[hash:base64]",              
            },
          },
        ],
      },
    ],
  },
  plugins: [htmlWebpackPlugin],
}

also my package.json

{
  "name": "mydashboard",
  "version": "1.0.0",
  "description": "",
  "scripts": {
    "start": "webpack-dev-server --mode development --hot --port 3000",
    "test": "echo \"Error: no test specified\" && exit 1"
  },
  "keywords": [],
  "author": "",
  "license": "ISC",
  "devDependencies": {
    "@babel/cli": "^7.2.3",
    "@babel/core": "^7.3.4",
    "@babel/preset-env": "^7.3.4",
    "@babel/preset-react": "^7.0.0",
    "babel-loader": "^8.0.5",
    "css-loader": "^2.1.0",
    "html-webpack-plugin": "^3.2.0",
    "style-loader": "^0.23.1",
    "webpack": "^4.29.5",
    "webpack-cli": "^3.2.3",
    "webpack-dev-server": "^3.2.1"
  },
  "dependencies": {
    "react": "^16.8.3",
    "react-dom": "^16.8.3"
  }
}

nmccready · 2019-04-16T22:13:10Z

@sokra any ideas? This issue is still prevalent and old. pnpm is very promising and this is blocker.

viceice · 2019-04-30T12:12:41Z

webpack should have a peeDependency to events, because hot module loading requires it

webpack/hot/emitter.js

Line 1 in 81cf088

var EventEmitter = require("events");

NikitaIT · 2019-09-13T10:39:16Z

failed in pnpm 3.8, too

alexander-akait · 2019-09-13T10:43:29Z

/cc @sokra i think we need add to peeDependency optional dep events

alexander-akait · 2019-09-13T10:43:41Z

@NikitaIT what is problem?

NikitaIT · 2019-09-13T11:15:59Z

@evilebottnawi

it all started with this error Error: Cannot find module 'typescript/package.json' with pnpm vuejs/vue-cli#4571
i update pnpm to 3.8.1 and solve it
after build I found an error Module not found: Error: Can't resolve 'ts-loader' and same errors for tslib and @types/node.
after forse install tslib and @types/node in package.json my app started
but failed in runtime with Module not found: Error: Can't resolve 'ts-loader'
after install ts-loader same as in vue-cli deps, i found Module build failed (from ../common/temp/node_modules/.registry.npmjs.org/babel-loader/8.0.6_@babel+core@7.6.0+webpack@4.12.0/node_modules/babel-loader/lib/index.js):
I gave up and switched to rush + npm.

alexander-akait · 2019-09-13T11:23:59Z

@NikitaIT i think problem in vue-cli, webpack doesn't provide ts-loader out of box

NikitaIT · 2019-09-13T11:30:06Z

@evilebottnawi i know, but i followed pnpm/pnpm#1678 and this problem mark as related.
I have Module not found: Error: Can't resolve 'ts-loader' when loader was already installed as a dependency for cli-plugin-typescript.

wbern · 2019-10-16T20:39:12Z

It's a shame this hasn't been resolved yet. I love using pnpm because it treats dependencies in a sane way and it's fast. I also like the simplicity of vue-cli and the power of webpack.

Could we attempt to fix this somehow? I don't even know who should change.

This caught my eye in pnpm/pnpm#1678

I think the best/cleanest/most portable solution is to use resolveLoader.alias and require.resolve to map loaders directly to absolute paths. (i.e. config.resolveLoader.alias.set('babel-loader$', require.resolve('babel-loader')))

Any help is appreciated here @evilebottnawi .

fengerzh · 2019-10-17T03:25:21Z

Have you tried to put a file .npmrc in your project root folder? The content is just like this:

shamefully-hoist=true

wbern · 2019-10-17T05:51:03Z

@fengerzh in my case I'm using rush, which will break if I try to do that I think. So all the shameful options are not an option for me. In my monorepo I would prefer not to break the boundaries between the packages anyway.

alexander-akait · 2019-10-17T11:41:09Z

@wbern What is problem? webpack should works (some plugins/loaders/tools can don't work), what is error or example of error?

ExE-Boss · 2019-10-28T17:53:14Z

@fengerzh
It still occurs even with shamefully-hoist=true.

@evilebottnawi

ERROR in Entry module not found: Error: Can't resolve 'babel-loader' in '…\Mozilla\kuma'

Regardless of shamefully-hoist

alexander-akait · 2020-10-27T11:53:39Z

Should be yes, feel free to test it and report if you have problems

With strict package managers such as pnpm or Yarn PnP, transitive dependencies are *not* hoisted to the root node_modules folder. This means that a webpack config defined within a package like '@nrwl/cypress' cannot resolve loaders like 'ts-loader', unless 'ts-loader' is declared in the workspace's own package.json. This is a problem because the workspace might define a different version of 'ts-loader', incompatible with the version declared by '@nrwl/cypress/package.json'. The workspace should not need to declare a dependency on 'ts-loader' anyway. See also: * pnpm/pnpm#801 * webpack/webpack#5087

* fix(core): resolve webpack loaders with `require.resolve()` With strict package managers such as pnpm or Yarn PnP, transitive dependencies are *not* hoisted to the root node_modules folder. This means that a webpack config defined within a package like '@nrwl/cypress' cannot resolve loaders like 'ts-loader', unless 'ts-loader' is declared in the workspace's own package.json. This is a problem because the workspace might define a different version of 'ts-loader', incompatible with the version declared by '@nrwl/cypress/package.json'. The workspace should not need to declare a dependency on 'ts-loader' anyway. See also: * pnpm/pnpm#801 * webpack/webpack#5087 * fix(core): resolve absolute 'raw-loader' path When replacing the 'raw-loader' rule in the `getStylesPartial` function, check for the absolute path of 'raw-loader' rather than just the name.

MondoGao · 2021-01-11T09:42:47Z

beep

MondoGao · 2021-01-11T09:43:12Z

it there a workaround in webpack@1?

sprockow · 2021-04-04T12:36:58Z

If it's unclear from the above concersation, the resolution problems with webpack loaders were fixed when I upgraded to webpack@5 (while using node@ˆ14 and pnpm@5.18) . I'm not familiar enough with webpack 5 to know why this is the case, but I was able to repro the issue by reverting the change and then reconfirmed the fix by applying the change again.

ckken · 2021-04-22T08:12:56Z

same problem

wbern · 2021-04-22T10:05:03Z

I think the way to solve this, if you intend to use a config package that provides a webpack config for you, is to use require.resolve for all of your loader references, like for example require.resolve('babel-loader') instead of plain babel-loader as a string in the webpack config.

I don't have these issues anymore, as long as I use the above.

If you don't have control over the package you get the configuration from, you should probably open an issue with them, because require.resolve makes more sense to do from their side rather than webpack's side. Webpack only reads loaders from working directory, changing that would be quite a breaking change, I believe.

ckken · 2021-04-22T12:04:29Z

has workspace demo or use with lerna demo

With strict package managers such as pnpm or Yarn PnP, transitive dependencies are *not* hoisted to the root node_modules folder. This means that a webpack config defined within a package like '@nrwl/cypress' cannot resolve loaders like 'ts-loader', unless 'ts-loader' is declared in the workspace's own package.json. This is a problem because the workspace might define a different version of 'ts-loader', incompatible with the version declared by '@nrwl/cypress/package.json'. The workspace should not need to declare a dependency on 'ts-loader' anyway. See also: * pnpm/pnpm#801 * webpack/webpack#5087

* fix(core): resolve webpack loaders with `require.resolve()` With strict package managers such as pnpm or Yarn PnP, transitive dependencies are *not* hoisted to the root node_modules folder. This means that a webpack config defined within a package like '@nrwl/cypress' cannot resolve loaders like 'ts-loader', unless 'ts-loader' is declared in the workspace's own package.json. This is a problem because the workspace might define a different version of 'ts-loader', incompatible with the version declared by '@nrwl/cypress/package.json'. The workspace should not need to declare a dependency on 'ts-loader' anyway. See also: * pnpm/pnpm#801 * webpack/webpack#5087 * fix(core): resolve absolute 'raw-loader' path When replacing the 'raw-loader' rule in the `getStylesPartial` function, check for the absolute path of 'raw-loader' rather than just the name.

vankop · 2021-09-15T19:26:21Z

Should work with webpack@5. Feel free to report new issue with reproducible repo.

icecream17 · 2021-09-24T01:26:43Z

https://github.com/icecream17/solver/runs/3694840400
I'm getting this error in create-react-app, react-scripts version ^5.0.0-next.37 and webpack 5.41.1 according to pnpm-lock.yaml.

icecream17 · 2021-09-24T01:44:27Z

Repro that's easy to do yourself (but not necessarily minimal):

npx create-react-app@next --scripts-version=@next --template=typescript@next my-ts-app
cd my-ts-app
Remove package-lock.json and node_modules
- The command is different based on os, but if it matters I'm on windows vscode so rm -Force node_modules in the terminal and Backspace on the package-lock file.
pnpm install
pnpm run build

Terminal output

Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.

Try the new cross-platform PowerShell https://aka.ms/pscore6

PS C:\Users\Steven\Documents\code\js\test> npx create-react-app@next --scripts-version=@next --template=typescript@next my-ts-app
Need to install the following packages:
  create-react-app@next
Ok to proceed? (y) y
npm WARN deprecated tar@2.2.2: This version of tar is no longer supported, and will not receive security updates. Please upgrade asap.

Creating a new React app in C:\Users\Steven\Documents\code\js\test\my-ts-app.

Installing packages. This might take a couple of minutes.
Installing react, react-dom, and react-scripts with cra-template-typescript...


added 1675 packages in 5m

163 packages are looking for funding
  run `npm fund` for details

Initialized a git repository.

Installing template dependencies using npm...

added 45 packages, and changed 1 package in 12s

164 packages are looking for funding
  run `npm fund` for details

We detected TypeScript in your project (src\App.test.tsx) and created a tsconfig.json file for you.

Your tsconfig.json has been populated with default values.

Removing template package using npm...


removed 1 package, and audited 1720 packages in 4s

164 packages are looking for funding
  run `npm fund` for details

3 moderate severity vulnerabilities

To address all issues (including breaking changes), run:
  npm audit fix --force

Run `npm audit` for details.

Created git commit.

Success! Created my-ts-app at C:\Users\Steven\Documents\code\js\test\my-ts-app
Inside that directory, you can run several commands:

  npm start
    Starts the development server.

  npm run build
    Bundles the app into static files for production.

  npm test
    Starts the test runner.
    Removes this tool and copies build dependencies, configuration files
    and scripts into the app directory. If you do this, you can’t go back!

We suggest that you begin by typing:

  cd my-ts-app
  npm start
Happy hacking!
PS C:\Users\Steven\Documents\code\js\test> cd my-ts-app
PS C:\Users\Steven\Documents\code\js\test\my-ts-app> rm -F node_modules
Remove-Item : Parameter cannot be processed because the parameter name 'F' is ambiguous. Possible matches include: -Filter -Force.
At line:1 char:4
+    ~~
    + CategoryInfo          : InvalidArgument: (:) [Remove-Item], ParameterBindingException
    + FullyQualifiedErrorId : AmbiguousParameter,Microsoft.PowerShell.Commands.RemoveItemCommand
 
PS C:\Users\Steven\Documents\code\js\test\my-ts-app> rm -Force node_modules

Confirm
The item at C:\Users\Steven\Documents\code\js\test\my-ts-app\node_modules has children and the Recurse parameter was not specified. If you continue, all children will be removed with the item. Are you sure you want to 
 continue?
[Y] Yes  [A] Yes to All  [N] No  [L] No to All  [S] Suspend  [?] Help (default is "Y"):
PS C:\Users\Steven\Documents\code\js\test\my-ts-app> pnpm install
 WARN  @testing-library/user-event@12.8.3 requires a peer of @testing-library/dom@>=7.21.4 but none was installed.
Packages: +1340
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++  
Packages are hard linked from the content-addressable store to the virtual store.
  Content-addressable store is at: C:\Users\Steven\.pnpm-store\v3
  Virtual store is at:             node_modules/.pnpm
node_modules/.pnpm/core-js-pure@3.18.0/node_modules/core-js-pure: Running postinstall script, done in 199ms
node_modules/.pnpm/core-js@3.18.0/node_modules/core-js: Running postinstall script, done in 198ms
node_modules/.pnpm/ejs@2.7.4/node_modules/ejs: Running postinstall script, done in 241ms
Cannot link binary 'jest' of 'jest-cli' to 'C:\Users\Steven\Documents\code\js\test\my-ts-app\node_modules\.pnpm\jest@26.6.0\node_modules\jest\node_modules\.bin': binary of 'jest' is already linked

dependencies:
+ @testing-library/jest-dom 5.14.1
+ @testing-library/react 11.2.7 (12.1.0 is available)
+ @testing-library/user-event 12.8.3 (13.2.1 is available)
+ @types/jest 26.0.24 (27.0.2 is available)
+ @types/node 12.20.26 (16.9.6 is available)
+ @types/react 17.0.24
+ @types/react-dom 17.0.9
+ react 17.0.2
+ react-dom 17.0.2
+ react-scripts 5.0.0-next.37
+ typescript 4.4.3
+ web-vitals 1.1.2 (2.1.0 is available)
PS C:\Users\Steven\Documents\code\js\test\my-ts-app> pnpm run build

> my-ts-app@0.1.0 build C:\Users\Steven\Documents\code\js\test\my-ts-app
> react-scripts build

Creating an optimized production build...
Failed to compile.

Module not found: Error: Can't resolve 'source-map-loader' in 'C:\Users\Steven\Documents\code\js\test\my-ts-app'


 ELIFECYCLE  Command failed with exit code 1.
PS C:\Users\Steven\Documents\code\js\test\my-ts-app>

Screenshot

Repo: https://github.com/icecream17/my-ts-app

Technically, icecream17/solver@a09eefb is also a repo showing this.
So you can compare solver's pnpm-lock to my-ts-app's pnpm-lock here: https://www.diffchecker.com/kcu6McIU

vjpr · 2021-09-24T02:13:56Z

Easy fix is to install source-map-loader at the top of your monorepo/project.

icecream17 · 2021-09-24T02:15:42Z

I kinda fixed it in package.json, but now react-scripts gets an error. I will try your idea

{
  "pnpm": {
    "overrides": {
      "webpack": "^5.51.0"
    }
  }
}

EDIT: Weirdly this package.json solution doesn't work, there's still the source-map-loader problem

icecream17 · 2021-09-24T02:29:33Z

Unfortunately when source-map-loader is installed, there's another error

alexander-akait · 2021-09-24T09:34:06Z

something wrong with postcss-normalize

mikob · 2022-04-29T22:34:48Z

make sure you have resolve.symlinks set to true

misha-erm · 2022-06-16T13:54:07Z

I think the way to solve this, if you intend to use a config package that provides a webpack config for you, is to use require.resolve for all of your loader references, like for example require.resolve('babel-loader') instead of plain babel-loader as a string in the webpack config.

I don't have these issues anymore, as long as I use the above.

Wow, you saved my day... Was very frustrated by that issue but require.resolve made the thing for me
Thank you @wbern

In my scenario I have a monorepo with separate packages for babel-preset and frontend so I was able to easily wrap all babel-loaders with require.resolve

wrightwriter · 2023-06-13T17:38:13Z

Fixed with this in .npmrc in current version of webpack (+ svelte and typescript):

node-linker=hoisted
shamefully-hoist=true

donaldpipowitch mentioned this issue Jun 19, 2017

Interoperability with other tools pnpm/pnpm#811

Closed

zkochan mentioned this issue Jun 19, 2017

Backport preserve-symlinks fix to enhanced-resolve@0.9 for webpack@1 webpack/enhanced-resolve#45

Closed

zkochan mentioned this issue Jun 26, 2017

automatically install peerDependencies pnpm/pnpm#827

Closed

webpack-bot added the inactive label Dec 25, 2017

webpack-bot removed the inactive label Dec 26, 2017

alexander-akait added the X2: answer required label Jun 6, 2018

marcelcremer mentioned this issue Nov 22, 2018

Problems with Angular CLI 6 pnpm/pnpm#1260

Closed

zkochan mentioned this issue Apr 24, 2019

shamefully-flatten not compatible with @vue/cli-service pnpm/pnpm#1678

Closed

NikitaIT mentioned this issue Sep 14, 2019

[rush] Let's get NPM 6 working with Rush microsoft/rushstack#886

Open

hiroppy mentioned this issue Feb 16, 2021

Can't resolve packages when node_modules are symlinked hiroppy/fusuma#386

Open

2 tasks

unknownterritory mentioned this issue Aug 6, 2021

npx sb init doesn't work for monorepos storybookjs/storybook#12995

Closed

Tomyail mentioned this issue Aug 11, 2021

fix style-loader can't resolve when using pnpm ai/size-limit#242

Merged

vankop closed this as completed Sep 15, 2021

icecream17 mentioned this issue Sep 24, 2021

Update webpack version / pnpm compatibility facebook/create-react-app#11480

Closed

rxliuli mentioned this issue Apr 21, 2022

yarn => pnpm graphql/graphiql#2323

Closed

kormide mentioned this issue Nov 8, 2022

refactor: use pnpm to run the build-web script aspect-forks/sourcegraph#1

Merged

justintemps mentioned this issue Jan 17, 2023

[Bug]: Dependencies collide in pnpm monorepo with two SB projects of differing versions storybookjs/storybook#20659

Closed

edumserrano mentioned this issue Jun 24, 2023

pnpm causes node-gyp rebuild failures pnpm/pnpm#2135

Open

Problems with pnpm and the way loaders are resolved #5087

Problems with pnpm and the way loaders are resolved #5087

Comments

donaldpipowitch commented Jun 19, 2017

donaldpipowitch commented Jun 19, 2017

zkochan commented Jun 19, 2017

zkochan commented Jun 19, 2017

webpack-bot commented Dec 25, 2017

andreineculau commented Dec 26, 2017

alexander-akait commented Jun 6, 2018

markerdmann commented Feb 4, 2019

mariotee commented Feb 28, 2019

nmccready commented Apr 16, 2019

viceice commented Apr 30, 2019

NikitaIT commented Sep 13, 2019

alexander-akait commented Sep 13, 2019

alexander-akait commented Sep 13, 2019

NikitaIT commented Sep 13, 2019

alexander-akait commented Sep 13, 2019

NikitaIT commented Sep 13, 2019 • edited

wbern commented Oct 16, 2019

fengerzh commented Oct 17, 2019

wbern commented Oct 17, 2019

alexander-akait commented Oct 17, 2019

ExE-Boss commented Oct 28, 2019 • edited

alexander-akait commented Oct 27, 2020

MondoGao commented Jan 11, 2021

MondoGao commented Jan 11, 2021

sprockow commented Apr 4, 2021 • edited

ckken commented Apr 22, 2021

wbern commented Apr 22, 2021 • edited

ckken commented Apr 22, 2021

vankop commented Sep 15, 2021

icecream17 commented Sep 24, 2021

icecream17 commented Sep 24, 2021 • edited

vjpr commented Sep 24, 2021

icecream17 commented Sep 24, 2021 • edited

icecream17 commented Sep 24, 2021 • edited

alexander-akait commented Sep 24, 2021 • edited

mikob commented Apr 29, 2022

misha-erm commented Jun 16, 2022

wrightwriter commented Jun 13, 2023 • edited

NikitaIT commented Sep 13, 2019 •

edited

ExE-Boss commented Oct 28, 2019 •

edited

sprockow commented Apr 4, 2021 •

edited

wbern commented Apr 22, 2021 •

edited

icecream17 commented Sep 24, 2021 •

edited

icecream17 commented Sep 24, 2021 •

edited

icecream17 commented Sep 24, 2021 •

edited

alexander-akait commented Sep 24, 2021 •

edited

wrightwriter commented Jun 13, 2023 •

edited