You are never going to be able to reliably determine if a resource exists before doing something with it.
Note that this holds true even on a program that runs directly on a user's machine or a server. I don't normally mention other people's answers in my own, but the one advocating that you do that check (which per the link is problematic even in the best of circumstances) but across a client-server gap is sheer folly. Think about all the things that can go wrong:
- The server could have moved the resource between the time you check and the time you set it.
- Another thread or even entire other program could have acquired a lock on the resource causing your request to either take a lot of extra time or fail outright.
- The user could be on a mobile connection and lost signal between the time of the check and the time of the resource request.
- If you're passing an authentication token the user's session could expire between the time of the check and the time of the actual request.
- The server could crash between the first request and the second.
- The second request could be load-balanced to a different server than the first request.
- The entire network for a major service could go down between the requests. Yes, really.
And so on.
Not to mention that for the happy path it involves a completely unnecessary extra round trip to the server before you start showing them the thing you wanted to show them in the first place!
The correct way to do this is to attempt to load the resource and then just handle the error if it fails:
function loadFiles(num) {
let s = 'assets/content/Compiladores/Slides/' + num + '.jpg';
let t = 'assets/content/Compiladores/Texts/' + num + '.txt';
document.slider.onerror = function () {
// deal with the resource not loading here
}
document.slider.src = s;
const desc = $("#description");
desc.on("error" function () {
// deal with the resource not loading here
});
desc.load(t);
$("#num").text(num);
}
onerrorevent.