# Ajax-loader_c5cd7f53.gif missing, slick

**URL:** https://discourse.roots.io/t/ajax-loader-c5cd7f53-gif-missing-slick/17619
**Category:** sage
**Tags:** webpack
**Created:** 2020-02-11T10:54:37Z
**Posts:** 4

## Post 1 by @Jacek — 2020-02-11T10:54:37Z

I can’t find solution how to fix 404 error for ajax-loader gif…

“…/dist/vendor/ajax-loader\_c5cd7f53.gif 404 (Not Found)”

I have added slick in main.scss  
@import “~slick-carousel/slick/slick.scss”;  
@import “~slick-carousel/slick/slick-theme.scss”;

and variables in common/\_variables.scss

// Slick Carousel font path  
$slick-font-path: “~slick-carousel/slick/fonts/”;

// Slick Carousel ajax-loader.gif path  
$slick-loader-path: “~slick-carousel/slick/”;

Arrows and all the stuff from slick carousel loading properly. But this gif can’t be loaded.  
Do you have similar issue ?

---

## Post 2 by @Jacek — 2020-02-11T11:21:38Z

Solved when I changed the limit in webpack.config.js from 4096 to 24096.

{  
test: /.(ttf|otf|eot|woff2?|png|jpe?g|gif|svg|ico)$/,  
include: config.paths.assets,  
loader: ‘url’,  
options: {  
limit: 24096,  
name: `[path]${assetsFilenames}.[ext]`,  
},  
},  
{  
test: /.(ttf|otf|eot|woff2?|png|jpe?g|gif|svg|ico)$/,  
include: /node\_modules/,  
loader: ‘url’,  
options: {  
limit: 24096,  
outputPath: ‘vendor/’,  
name: `${config.cacheBusting}.[ext]`,  
},  
},  
],

But I am not sure that is good solution and should I change limits in webpack ?

---

## Post 3 by @diomededavid — 2021-01-22T05:47:29Z

> [@Jacek](#):
>
> 24096

Thank you for the solution. I do not know if it is correct either, but it worked.

---

## Post 4 by @mattia — 2021-01-28T09:54:39Z

I had the same problem, and the only fix also for me was to update the limit in webpack.config.js as @Jacek suggested.  
I noticed that the ajax-loader.gif is 4,178 bytes so you can increase the limit in webpack.config.js just a bit, I tried with 4180 and it works.

@mmirus in another post said

> [@Base64 encode on vendors](https://discourse.roots.io/t/base64-encode-on-vendors/13987/2):
>
> The `limit` options mean that files under 4,096 bytes will be encoded and inlined.

so I don’t think that increasing the limit just a little bit is a bad solution, but I would be good to have an expert opinion on this. (because it seems strange that a 4,178 bytes gif cause this problem)