@pimepanama This will be due to code having changed, a new hash for the filename being generated and the previous file no longer existing after the new deployment.
The reason you see it as a MIME type of “text/html” error is because the file isn’t found, which would be a 404 and instead the redirect you have of /* /index.html 200 returns the contents of the /index.html file, which has a MIME type of “text/html” (and obviously isn’t valid JavaScript).
It’s mentioned here in the documentation:
https://docs.netlify.com/configure-builds/javascript-spas/#code-splitting-or-hashed-filenames
Here’s the relevant support guide:
https://answers.netlify.com/t/support-guide-handling-code-splitting-issues-on-netlify/113158