Add a Link with "likely causes" to "The API version X does not match the worker version Y"

[ralfhauser]

For me, the solution mentioned in
#10997 (comment)
worked.

Suggestion:

1. As this is a frequent error, add a link to this error message where on your site, you can list possible counter-measures.
   a) flushing the cache probably being the most likely

More incidents of the same error message:

• The API version does not match the worker version #9997
• Error: The API version "2.6.33" does not match the Worker version "2.6.36" #11994
• ...

[Snuffleupagus]

add a link to this error message where on your site,

Adding a link in the code could be problematic[1], however adding a section about this in the Wiki would probably be a good idea.

flushing the cache probably being the most likely

Another situation, and possible more common cause, is for users that load the pdf.worker.js file from a CDN (see https://mozilla.github.io/pdf.js/getting_started/#including-via-a-cdn), and thus run into these issues when updating to a new PDF.js release.

---

[1] For example, it would do nothing for the already existing releases (and it would also take quite some time before that even hits official releases). Moreover, there's also the risk that a link in the code itself breaks inadvertently, if any future changes are make to e.g. the Wiki (or wherever the link points to), and having a broken link seems worse than no link at all.

[Snuffleupagus]

An entry has been added to the Wiki, please see https://github.com/mozilla/pdf.js/wiki/Frequently-Asked-Questions#version-mismatch
We can obviously always improve/expand upon that later on; however closing this issue as fixed for now.