Don't output empty JS files #151

TomS- · 2018-05-17T10:13:13Z

I have seen people use the Extract plugin and name the file the same to prevent a useless .js file, however, naming the file the same in this instance gives the error:
Conflict: Multiple assets emit to the same filename main.js

I only want to take a CSS file and run it though autoprefix and minify, I don't need it to output a JS file.

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

alexander-akait · 2018-05-17T10:28:36Z

@TomS- can you create minimum reproducible test repo?

TomS- · 2018-05-17T10:34:35Z

@evilebottnawi Yup, I'll set it up this evening

TomS- · 2018-05-18T09:56:19Z

https://github.com/TomS-/minicss Sorry for the delay

tiendq · 2018-05-21T12:48:42Z

@TomS- I'm not sure I understand your issue. Do you want to not output tailwind.js from importing tailwind.css because there is already a tailwind.js in your source?

TomS- · 2018-05-21T16:39:01Z

@tiendq I don't want Webpack to output a JS file for CSS. It seems strange to me for it to do that. At the moment I'm getting the CSS file and a JS file. I'm coming from Gulp so maybe it's just I don't understand Webpack.

tiendq · 2018-05-22T00:39:39Z

@TomS- I don't want it too :)

paulmasek · 2018-06-07T04:44:31Z

+1 Mainly because it'll probably fix Va1/browser-sync-webpack-plugin#69

GiancarlosIO · 2018-06-13T19:38:04Z

+1

alexander-akait · 2018-06-15T10:22:54Z

Weppack is js bundle, i can not imagine why this might be necessary, please provide use case

thewebsitedev · 2018-06-16T21:34:10Z

Same issue. I have a PHP application but I am managing assets with Webpack. With Webpack 4 & MiniCssExtractPlugin, generating CSS files is a pain at the moment. I need to directly load CSS file.

Part of my config:

{
    mode: "development",
    entry: {
        "admin": "./assets/admin/src/scss/theme.scss"
    },
    module: {
        rules: [
            {
                test: /\.(sa|sc|c)ss$/,
                use: [
	            MiniCssExtractPlugin.loader,
                    'css-loader',
                    'sass-loader'
                ],
            },
        ]
    },
    plugins: [
        new MiniCssExtractPlugin({
            filename: "[name].css",
            chunkFilename: "[id].css"
        })
    ],
    output: {
        path: path.resolve(__dirname, 'assets/admin/dist/css')
    }
},

Files generated are: admin.css & admin.js.

I don't need admin.js file. It's useless in my case.

bregenspan · 2018-06-18T15:17:03Z

The cause of this is probably webpack/webpack#7300, which has been added to the Webpack 4.x milestone.

paynecodes · 2018-06-21T20:11:42Z

This issue is biting me as well. Feel free to close this if this plugin can't offer an alternative. Btw, webpack/webpack#7300 has been retagged with Webpack 5.x, so we won't likely see a fix in webpack until then.

alexander-akait · 2018-06-22T10:51:17Z

We search way to fix it inside plugin

danechitoaie · 2018-06-30T14:02:48Z

Having same issue. I'm using webpack to compile both JS and SCSS and different entries (i.e. not requiring the css inside JS) and for each .css file generated I also get a .js file.

Igloczek · 2018-07-04T01:15:05Z

Same as webpack-contrib/extract-text-webpack-plugin#518

Igloczek · 2018-07-04T01:28:37Z

My temporary solution is to use this plugin - https://github.com/medfreeman/ignore-assets-webpack-plugin
Works with v4, but use deprecated methods.

danechitoaie · 2018-07-04T07:20:23Z

I had to make my own plugin:

class MiniCssExtractPluginCleanup {
    apply(compiler) {
        compiler.hooks.emit.tapAsync("MiniCssExtractPluginCleanup", (compilation, callback) => {
            Object.keys(compilation.assets)
                .filter(asset => {
                    return ["*/scss/**/*.js", "*/scss/**/*.js.map"].some(pattern => {
                        return minimatch(asset, pattern);
                    });
                })
                .forEach(asset => {
                    delete compilation.assets[asset];
                });

            callback();
        });
    }
}

It's very specific for my use case and has things hardcoded and I even have just put it directly in the webpack.config.js file (so not published on npm) but maybe it can be integrated somehow in some version directly into mini-css-extract-plugin? And made configurable with some additional options.

riccardomessineo · 2018-07-10T08:27:15Z

To give you another "solution", I'm currently just excluding the useless .js on the bundled index.html:

        plugins: [
            new HtmlWebpackPlugin({
                template: './app/index_webpack.html',
                excludeAssets: [/partials.*.js/],
            }),
            new HtmlWebpackExcludeAssetsPlugin()
        ],

Igloczek · 2018-07-10T08:45:14Z

@riccardomessineo correct me if I'm wrong, but it still generates those files, but don't add them to the html file, right?

riccardomessineo · 2018-07-10T08:47:08Z

@Igloczek you're perfectly right.
It does not resolve the issue, I just wanted to provide another workaround.

fqborges · 2018-08-21T16:38:24Z

I faced the same issue of having a style only entry (css/sass/less) generating an extra .js file, and ended up creating a webpack plugin to remove the js file from the compilation.

I published it on npm as webpack-fix-style-only-entries. You can find the source code on https://github.com/fqborges/webpack-fix-style-only-entries.

:-) shamelessly promoting my package :-)

michael-ciniawsky · 2018-08-24T13:58:50Z

I have seen people use the Extract plugin and name the file the same to prevent a useless .js file, however, naming the file the same in this instance gives the error:
Conflict: Multiple assets emit to the same filename main.js

Use { filename: '[name].css' }. The empty JS File is going away (in webpack >= v5.0.0), but this needs to be fixed in webpack core itself

alexander-akait · 2018-08-24T14:11:58Z

@michael-ciniawsky bug, still open before it was fixed in webpack

artemkochnev · 2018-08-27T15:40:37Z

@fqborges I'm trying to use your plugin, but I'm running into a problem where the file is getting passed as * instead of the actual file path.

For example, if I add a console.log(resources, file), I get a bunch of results like this: [ '<redacted>/src/app/css/pages/Home.scss' ] '*'

Do you know why this might be happening? The webpack docs on what gets passed for the chunkAsset hook are fairly light...

themojilla · 2018-11-19T10:21:26Z

@riccardomessineo
HtmlWebpackExcludeAssetsPlugin broke the app.

riccardomessineo · 2018-11-19T10:27:19Z

Sorry to hear that...
As I pointed before, it was just a workaround and not a viable clean final solution.

tflori · 2018-12-25T10:49:42Z

@danechitoaie thx for the tip!

I've just created a more abstract class to do this:

class Without {
    constructor(patterns) {
        this.patterns = patterns;
    }

    apply(compiler) {
        compiler.hooks.emit.tapAsync("MiniCssExtractPluginCleanup", (compilation, callback) => {
            Object.keys(compilation.assets)
                .filter(asset => {
                    let match = false,
                        i = this.patterns.length
                    ;
                    while (i--) {
                        if (this.patterns[i].test(asset)) {
                            match = true;
                        }
                    }
                    return match;
                }).forEach(asset => {
                    delete compilation.assets[asset];
                });

            callback();
        });
    }
}

module.exports = {
    mode: process.env.NODE_ENV || 'development',
    resolve: {
        extensions: ['.scss', '.css']
    },
    module: {
        rules: [
            {
                test: /\.scss$/,
                use: [
                    MiniCssExtractPlugin.loader,
                    'css-loader',
                    'sass-loader',
                ],
            },
        ],
    },
    plugins: [
        new MiniCssExtractPlugin({
            filename: '[name]',
        }),
        new Without([/\.css\.js(\.map)?$/]), // just give a list with regex patterns that should be excluded
    ],
};

Jorenm · 2019-01-11T21:27:21Z

I forked disable-output-webpack-plugin to allow me to conditionally remove the outputs (https://github.com/Jorenm/disable-output-webpack-plugin/tree/options)

I use it with this config, which works like a charm:

var stylusCompiler = {
	name: 'stylus',
	entry: {
		above_fold: './src/css/above_fold.styl',
		site: './src/css/site.styl'
	},
	output: {
		path: path.resolve(__dirname, 'dist/css'),
	},
	module: {
		rules: [
			{
				test: /\.styl$/,
				use: [
					{
						loader: MiniCssExtractPlugin.loader,
						options: {
							// you can specify a publicPath here
							// by default it use publicPath in webpackOptions.output
							publicPath: '../'
						}
					},
					{
						loader: "css-loader" // translates CSS into CommonJS
					},
					{
						loader: "stylus-loader", // compiles Stylus to CSS
						options: {
							use: [
								require('nib')(),
								require('rupture')()
							]
						}
					},
				]
			},
		]
	},
	plugins: [
		new MiniCssExtractPlugin({
			filename: '[name].bundled.css',
		}),
		new DisableOutputWebpackPlugin({
			test: /\.js$/
		})
	],
	optimization: {
		minimizer: [new OptimizeCSSAssetsPlugin({})],
	}
};

wzc0x0 · 2019-01-14T04:05:29Z

@danechitoaie thx for the tip!

I've just created a more abstract class to do this:

class Without {
constructor(patterns) {
this.patterns = patterns;
}
apply(compiler) {
    compiler.hooks.emit.tapAsync("MiniCssExtractPluginCleanup", (compilation, callback) => {
        Object.keys(compilation.assets)
            .filter(asset => {
                let match = false,
                    i = this.patterns.length
                ;
                while (i--) {
                    if (this.patterns[i].test(asset)) {
                        match = true;
                    }
                }
                return match;
            }).forEach(asset => {
                delete compilation.assets[asset];
            });

        callback();
    });
}
}

module.exports = {
mode: process.env.NODE_ENV || 'development',
resolve: {
extensions: ['.scss', '.css']
},
module: {
rules: [
{
test: /.scss$/,
use: [
MiniCssExtractPlugin.loader,
'css-loader',
'sass-loader',
],
},
],
},
plugins: [
new MiniCssExtractPlugin({
filename: '[name]',
}),
new Without([/.css.js(.map)?$/]), // just give a list with regex patterns that should be excluded
],
};

very well ! Thanks !

leonexcc · 2019-04-11T08:00:02Z

I use Symfony Encore and have to fix the entrypoints too. But this should also work with a normal Webpack.

My approach to this problem:

class MiniCssExtractPluginCleanup {
    apply(compiler) {
        compiler.hooks.emit.tapAsync("MiniCssExtractPluginCleanup", (compilation, callback) => {
            let jsFile = /\.js$/;

            compilation.entrypoints.forEach((entrypoint) => {
                entrypoint.chunks.forEach((chunk) => {
                    if (chunk.files.length > 1) {
                        let notEmptyJsModules = chunk.getModules().filter(module => {
                            return module.constructor.name === 'NormalModule'
                                && module.originalSource().source() !== '// extracted by mini-css-extract-plugin';
                        });

                        if (notEmptyJsModules.length === 0) {
                            chunk.files = chunk.files.filter(file => {
                                if (jsFile.test(file)) {
                                    delete compilation.assets[file];
                                    return false;
                                } else return true;
                            });
                        }
                    }
                });
            });

            callback()
        });
    }
}

and i use it with:

.addPlugin(new MiniCssExtractPluginCleanup(), -11)

alexander-akait · 2019-04-11T11:13:19Z

Fixed for webpack@5, anyway you can send a PR with fix it on mini-css-extract-plugin side (using option)

psdon · 2019-11-18T10:00:43Z

Another way to prevent this:

const IgnoreEmitPlugin = require('ignore-emit-webpack-plugin');
plugins: [
    new IgnoreEmitPlugin(/(?<=main_css\s*).*?(?=\s*js)/gs),
]
``

ararename · 2019-12-04T12:53:29Z

Hello erveryone.
After six days, for one short moment i thought i succeeded in removing 'empty' js files from the html and from the filesystem with 'html-webpack-exclude-assets-plugin' and 'ignore-emit-webpack-plugin' (one suggested by riccardomessineo above, one by psdon).
Everything fine, links gone, empty files gone, the bootstrap js is inside of index.js, index.js is properly linked, no console error and all JavaScript dead.

As soon as i put the line 'excludeAssets: [/app.js/, /custom.js/]' in the webpack config above in comments, everything works (ok, an console error that missing files are linked which, in this case, does indicate that it works) but i have the links to the files in the html. When i uncomment that line, the behaviour is as described above.

Some help before reaching insanity would be highly appreciated. Thank you.

const HtmlWebpackPlugin = require("html-webpack-plugin");
const MiniCssExtractPlugin = require("extract-css-chunks-webpack-plugin");
const HtmlWebpackExcludeAssetsPlugin = require("html-webpack-exclude-assets-plugin");
const IgnoreEmitPlugin = require("ignore-emit-webpack-plugin");

const path = require('path');
const isProd = process.env.NODE_ENV === 'production';
const outputDir = path.join(__dirname, 'build/');

module.exports = {

  entry: {
    index: path.resolve( process.cwd(), 'src', 'index.js')
  },

  mode: isProd ? 'production' : 'development',

  plugins: [
    new HtmlWebpackPlugin({
      filename: 'index-fsc.html',
      template: 'src/index-fsc.html',
      excludeAssets: [/app.js/, /custom.js/]
    }),

    new MiniCssExtractPlugin({
      filename: isProd ? 'assets/css/[name].[hash].css' : 'assets/css/[name].css',
    }),

	new HtmlWebpackExcludeAssetsPlugin(),
	// finally, together with 'html-webpack-exclude-assets-plugin', this is useful 

	new IgnoreEmitPlugin(['app.js', 'custom.js'])
  ],

  optimization: {
     splitChunks: {
      cacheGroups: {
        app: {
          name: 'app',
          test: /app\.s?css$/,
          chunks: 'all',
          enforce: true,
        },
        custom: {
          name: 'custom',
          test: /custom\.s?css$/,
          chunks: 'all',
          enforce: true,
        }
      },
    },
  },
  
  module: {
    rules: [
      {
        test: /\.(sa|sc|c)ss$/,
        use: [
          {
            loader: MiniCssExtractPlugin.loader,
            options: {
              hmr: process.env.NODE_ENV === 'development',
            },
          },
          'css-loader', 'postcss-loader', 'sass-loader',
        ],
      },  
      {
         test: /.(ttf|otf|eot|svg|woff(2)?)(\?[a-z0-9]+)?$/,
         use: [{
           loader: 'file-loader',
           options: {
             emitFile: true,
             name: '[name].[ext]',
             outputPath: 'assets/fonts/',    // where the fonts will go
             publicPath: '../fonts'       // override the default path
           }
         }]
       }
    ]
  },

  output: {
    path: outputDir,
    filename: 'assets/js/[name].js'
  },

  devServer: {
    compress: true,
    contentBase: outputDir,
    port: process.env.PORT || 8000,
    historyApiFallback: true
  }
};

alexander-akait · 2019-12-04T12:55:51Z

It will be solved for webpack@5 (near future), right now please use solutions above

ararename · 2019-12-04T13:12:13Z

Thank you for the answer, i was in hope to not get this 'answer'.

Here we have a thread discussing this very problem since 1 1/2 years, the tip to wait for v5 had already been given a year ago, but the discussion went on.

I did use a solution from above, i tried all of them.
I am looking for a solution for my problem (as described above). Any help is welcome.

ararename · 2019-12-04T22:37:33Z

It turned out that not importing the scss files in my index.js but setting them as entry points in the webpack config did the job.

Everything else was fine. I never changed this throughout my efforts to get this to work. Of course i tried setting the scss files as entry points but not once did i think of removing them from my index.js. Other solutions here might also only work well if crafted like this, i don't know, but check if they do not.

I know some folks say that setting (s)css as an entry point should not work at all, consider it bad practice. At this moment in time i couldn't care less as long as i do not encounter direct drawbacks from that in my project (but i am interested in what these might be).

And, to be honest, i have no real need to get this going this way, i am new to webpack, this is my first 'live' test which began 6 days ago. This is how i start stuff, i try to accomplish something i have in mind. That also is the reason for why there's Foundation and Bootstrap in there, i was curious. Had to get into Foundation for a job and i wanted to transfer some of my Boostrap blocks to be styled by Foundation. To do this in one file in parallel seemed interesting and now it seems to work.
Thanks to all the contributors to this thread, before i was desperate because of this :-)

const HtmlWebpackPlugin = require('html-webpack-plugin');
const MiniCssExtractPlugin = require('extract-css-chunks-webpack-plugin');
const HtmlWebpackExcludeAssetsPlugin = require('html-webpack-exclude-assets-plugin');
const IgnoreEmitPlugin = require('ignore-emit-webpack-plugin');

const path = require('path');
const isProd = process.env.NODE_ENV === 'production';
const outputDir = path.join(__dirname, 'build/');

module.exports = {

  entry: {
    index: path.resolve( process.cwd(), 'src', 'index.js'),
    app: path.resolve( process.cwd(), 'scss', 'app.scss'),
    custom: path.resolve( process.cwd(), 'scss/fsc-custom', 'custom.scss')
  },

  mode: isProd ? 'production' : 'development',

  plugins: [
    new HtmlWebpackPlugin({
      filename: 'index-fsc.html',
      template: 'src/index-fsc.html',
      excludeAssets: [/app.js/, /custom.js/]
    }),

    new MiniCssExtractPlugin({
      filename: isProd ? 'assets/css/[name].[hash].css' : 'assets/css/[name].css',
    }),

    new HtmlWebpackExcludeAssetsPlugin(),
    // finally, together with 'html-webpack-exclude-assets-plugin', this is useful 
    new IgnoreEmitPlugin(['app.js', 'custom.js'])
  ],

  optimization: {
    splitChunks: {
      cacheGroups: {
        app: {
          name: 'app',
          test: /app\.s?css$/,
          chunks: 'all',
          enforce: true,
        },
        custom: {
          name: 'custom',
          test: /custom\.s?css$/,
          chunks: 'all',
          enforce: true,
        }
      },
    },
  },
  
  module: {
    rules: [
      {
        test: /\.(sa|sc|c)ss$/,
        use: [
          {
            loader: MiniCssExtractPlugin.loader,
              options: {
                hmr: process.env.NODE_ENV === 'development',
              },
          },
          'css-loader', 
          'postcss-loader', 
          'sass-loader',
        ],
      },  

      {
        test: /.(ttf|otf|eot|svg|woff(2)?)(\?[a-z0-9]+)?$/,
        use: [{
          loader: 'file-loader',
          options: {
            emitFile: true,
            name: '[name].[ext]',
            outputPath: 'assets/fonts/',
            publicPath: '../fonts'
          }
        }]
      }
    ]
  },

  output: {
    path: outputDir,
    filename: 'assets/js/[name].js'
  },

  devServer: {
    compress: true,
    contentBase: outputDir,
    port: process.env.PORT || 8000,
    historyApiFallback: true
  }
};

I said i tried all of the solutions in this thread. That's true. But the more i look through them now the more i see that i could have found out faster if i hadn't been only rearranging the webpack config over and over again. Some of the solution do suggest using entry points. You know what, this is confusing. It is.

alexander-akait · 2019-12-25T14:17:31Z

Close in favor #85

grahamsutton · 2020-09-02T00:43:49Z

Just another idea, in case you know which directory you want to remove the useless JS file from and your webpack command is aliased as an npm run command then you can just issue a wildcard delete for anything that ends with a .js extension in that directory. Not a perfect solution, but satisfactory.

Example:

In package.json

{
  ...
  "scripts": {
    "build": "node_modules/.bin/webpack && rm -Rf ./dist/css/*.js"
  }
}

then

$ npm run build

Bilge · 2020-12-21T19:51:43Z

v5 is here and it has changed absolutely nothing. Seems it's being tracked at webpack/webpack#11671.

zhuzhuyule · 2021-01-13T13:35:42Z

// webpack.config.js
{
  optimization: {
      splitChunks: {
        cacheGroups: {
          styles: {
            ...
            type: 'css/mini-extract',
            ...
          },
        },
      },
    },
}

I added the type: 'css/mini-extract', config. And then resolved the problem!

koga73 · 2021-02-09T22:42:41Z

// webpack.config.js
{
  optimization: {
      splitChunks: {
        cacheGroups: {
          styles: {
            ...
            type: 'css/mini-extract',
            ...
          },
        },
      },
    },
}

I added the type: 'css/mini-extract', config. And then resolved the problem!

This doesn't work, at least not with WebPack 4. How does it work for you?

alexb-uk · 2021-03-26T12:37:36Z

If it helps anyone I used the plugin remove-files-webpack-plugin, just need to change folder to match your project structure:

new RemovePlugin({
  /**
   * After compilation permanently remove empty JS files created from CSS entries.
   */
  after: {
    test: [
      {
        folder: 'dist/public/css',
        method: (absoluteItemPath) => {
          return new RegExp(/\.js$/, 'm').test(absoluteItemPath);
        },
      }
    ]
  }
}),

Ihor139 · 2024-04-24T07:06:38Z

@danechitoaie thx for the tip!

I've just created a more abstract class to do this:

class Without {
    constructor(patterns) {
        this.patterns = patterns;
    }

    apply(compiler) {
        compiler.hooks.emit.tapAsync("MiniCssExtractPluginCleanup", (compilation, callback) => {
            Object.keys(compilation.assets)
                .filter(asset => {
                    let match = false,
                        i = this.patterns.length
                    ;
                    while (i--) {
                        if (this.patterns[i].test(asset)) {
                            match = true;
                        }
                    }
                    return match;
                }).forEach(asset => {
                    delete compilation.assets[asset];
                });

            callback();
        });
    }
}

module.exports = {
    mode: process.env.NODE_ENV || 'development',
    resolve: {
        extensions: ['.scss', '.css']
    },
    module: {
        rules: [
            {
                test: /\.scss$/,
                use: [
                    MiniCssExtractPlugin.loader,
                    'css-loader',
                    'sass-loader',
                ],
            },
        ],
    },
    plugins: [
        new MiniCssExtractPlugin({
            filename: '[name]',
        }),
        new Without([/\.css\.js(\.map)?$/]), // just give a list with regex patterns that should be excluded
    ],
};

Thank you very much for your help, I have tried several times to compile for separate js and css files and always had problems, but you helped a lot with your code. Good to you!!!!!

o-alexandrov mentioned this issue Jun 24, 2018

docs(README): How to handle duplicate style tags chrisvfritz/prerender-spa-plugin#110

Merged

louisscruz mentioned this issue Jun 27, 2018

main.js has been loaded,but it didn't run webpack/webpack#7535

Closed

Igloczek mentioned this issue Jul 4, 2018

splitChunks can create initial chunks that are empty after CSS extraction webpack/webpack#7300

Closed

michael-ciniawsky closed this as completed Aug 24, 2018

michael-ciniawsky changed the title ~~Feature Request: Don't output JS file~~ Don't output empty JS files Aug 24, 2018

alexander-akait reopened this Aug 24, 2018

thaoms mentioned this issue Nov 25, 2018

Legacy JS doesn't work after build nystudio107/annotated-webpack-config#5

Closed

evanpurkhiser mentioned this issue Feb 12, 2019

build(webpack): Do not generate empty js file for style entries getsentry/sentry#12041

Merged

7iomka mentioned this issue Mar 21, 2019

miniCssExtractPlugin && browsersync - help needed fqborges/webpack-fix-style-only-entries#15

Closed

JesseFarebro mentioned this issue Apr 8, 2019

A "styles.js" file is being loaded (that shouldn't exist) gatsbyjs/gatsby#12018

Closed

alexander-akait closed this as completed Dec 25, 2019

Mamaduka mentioned this issue May 3, 2020

Scripts: Add CSS support to start and build scripts WordPress/gutenberg#21730

Merged

4 tasks

emkayy mentioned this issue Jan 19, 2021

Generation of empty JS file in output folder from CSS only entry point webpack/webpack#11671

Open

Rahmon mentioned this issue Jul 21, 2021

Empty js file output from css entry 10up/10up-toolkit#90

Closed

cirosantilli mentioned this issue Jan 13, 2022

Not able to produced with same names of js and css file in build webpack/webpack#12302

Closed

webdiscus mentioned this issue Oct 2, 2023

simplify webpack config petrushin-ai/webpack5-project-starter#1

Closed

brian-smith-tcril mentioned this issue Jul 29, 2024

feat: add ParagonWebpackPlugin to support design tokens openedx/frontend-build#546

Merged

Don't output empty JS files #151

Don't output empty JS files #151

Comments

TomS- commented May 17, 2018

alexander-akait commented May 17, 2018

TomS- commented May 17, 2018

TomS- commented May 18, 2018

tiendq commented May 21, 2018

TomS- commented May 21, 2018

tiendq commented May 22, 2018

paulmasek commented Jun 7, 2018

GiancarlosIO commented Jun 13, 2018

alexander-akait commented Jun 15, 2018

thewebsitedev commented Jun 16, 2018 • edited Loading

bregenspan commented Jun 18, 2018

paynecodes commented Jun 21, 2018

alexander-akait commented Jun 22, 2018

danechitoaie commented Jun 30, 2018

Igloczek commented Jul 4, 2018

Igloczek commented Jul 4, 2018

danechitoaie commented Jul 4, 2018

riccardomessineo commented Jul 10, 2018

Igloczek commented Jul 10, 2018

riccardomessineo commented Jul 10, 2018

fqborges commented Aug 21, 2018

michael-ciniawsky commented Aug 24, 2018 • edited Loading

alexander-akait commented Aug 24, 2018 • edited Loading

artemkochnev commented Aug 27, 2018

themojilla commented Nov 19, 2018

riccardomessineo commented Nov 19, 2018

tflori commented Dec 25, 2018

Jorenm commented Jan 11, 2019

wzc0x0 commented Jan 14, 2019

leonexcc commented Apr 11, 2019

alexander-akait commented Apr 11, 2019 • edited Loading

psdon commented Nov 18, 2019 • edited Loading

ararename commented Dec 4, 2019 • edited Loading

alexander-akait commented Dec 4, 2019

ararename commented Dec 4, 2019 • edited Loading

ararename commented Dec 4, 2019 • edited Loading

alexander-akait commented Dec 25, 2019

grahamsutton commented Sep 2, 2020

Bilge commented Dec 21, 2020 • edited Loading

zhuzhuyule commented Jan 13, 2021

koga73 commented Feb 9, 2021

alexb-uk commented Mar 26, 2021

Ihor139 commented Apr 24, 2024

thewebsitedev commented Jun 16, 2018 •

edited

Loading

michael-ciniawsky commented Aug 24, 2018 •

edited

Loading

alexander-akait commented Aug 24, 2018 •

edited

Loading

alexander-akait commented Apr 11, 2019 •

edited

Loading

psdon commented Nov 18, 2019 •

edited

Loading

ararename commented Dec 4, 2019 •

edited

Loading

ararename commented Dec 4, 2019 •

edited

Loading

ararename commented Dec 4, 2019 •

edited

Loading

Bilge commented Dec 21, 2020 •

edited

Loading