We Keep Coding

Unexpected Token in Angulars runtime.js

I've a strange issue with an Angular frontend that has been running fine for the last months and all of a sudden the page doesn't load anymore (just white).
In the browser console I see the message
Uncaught SyntaxError: Unexpected token '<' (at runtime.ec2944dd8b20ec099bf3.js:1:1)
Unfortunately I'm not really a web dev and just have limited experience with Angular (rather using React if any). From what I read, this runtime.js is a utility file built by webpack. The whole page runs in a docker container on the server, I tried rebuilding it but issue remains. I see it on every computer in the network and with every browser, so it doesn't seem to be a caching problem.
When I run the Angular project on my local machine with ng serve everything works fine, so the application code itself seems to be okay as well.
Is anyone aware of something that has changed recently that could cause such an issue (altough it would have to be the browser...) or could give me a hint in what direction I should dig?

Presumably the frontend is trying to fetch data from an endpoint where a json-response is expected. If the endpoint is not accessible for some reason the server then returns a normal html-formatted response, which starts with a ' tag. This '<'-character is not valid json or js and it causes the unexpected token exception.
Maybe on localhost it works fine, because locally you have the necessary permissions to access the endpoint, while on production environment these permissions are lacking?

JSP page not loading issue after login

JSP page is not loading after login. same set up is working on Quality system but trying to clone on another system its not working.. guessing the images files path are not reachable in custom project. getting 404 error.. using web sphere server & jdk 1.8

From just your original description it is hard to say what might cause the error, but then if you have reason to believe an image path isn't reachable can you test that theory by logging into the system and seeing if you can access the directory in question. Generally, whether an error in JSP is caused by a compile error or a runtime error, there should be a message or exception in the server log showing more information what went wrong.

How can I Found what is causing crashing page in Mobile?

I have a problem:
Cart and checkout page in the mobile version: on scrolls page refreshed and suddenly crashed and in safari, I get this error: a problem repeatedly occurred.
I checked the following ways but I couldn't find what caused this problem:
I enable WP_DEBUG and fix all errors.
I check each single js file structure in online tools that check the
structure of JS files.
I create wp-content/mu-plugins and disable unnecessary plugins on these pages.
I removed .css and .js files of the theme to see if this file caused
this error.
I checked the console in inspect mode. and there is no error there.
Would you please share your experience what else I should check to see the reason of the

why doesn't my live server work in visual studio code?

My live server on visual studio keeps opening an old html file when i try to open my current one. Ive tried reinstalling the extension but its the same problem. Can anyone help please

i cannot have two project folders with an html file running through the live server. Only one html file can be streamed at one time other wise when trying to stream the second, it will stream the first (Like the issue i was having)

I was having the same problem but later on I find out that, I renamed my project folder while my server was still loading the same project but with the previous folder name so I changed the link to my new folder folder name and it worked for me.

I have live server will simply not work if there was an error in JavaScript file.
Even if you do an alert in the beginning of JavaScript file (for test purposes) but at the end of the file re-define a variable which was already defined before, this error will render liver server not working.
The html page will not respond as well.
Solution is to go to developer tools (F12), see the errors on console, fix them and save and the live server would be back in action! At least that was the case with me.

I had the same issue, sometimes it was an error on the console, or keep showing an old HTML, tried everything, deleting cookies, reinstalling everything and nothing worked,
Eventually, it worked with a hard refresh, what it really worked was to
Go to ---> vs code settings ----> extensions ---> live server config set as chrome private. So far no more errors!

The liveserver extension serves static pages like html files and it does not load javascript or typescript files. You need to setup a server yourself for example in react you use webpack to configure your local server and your app runs on a localhost:port. In a nutshell, you need to write a script for node to run your js files. And you won't need liveserver after that.

Ace Code Editor theme 403

I have installed the code editor Ace onto my site (not locally). Now I am trying to load the theme 'ambiance' as shown in the available themes here.
editor.setTheme("ace/theme/ambiance");
However its failing to load returning a 403 response. I can see it being used with no issue on the ace kitchen sink page here.
The other themes I have tried have loaded with no problem, so why am I getting 403 forbidden for ambiance since its clearly listed in the themes repo?

Which installation instructions did you follow (link please)?
I did
git clone https://github.com/ajaxorg/ace-builds.git
and the contents of ace-builds/src show no obvious problem with theme-ambiance.js.
All I can suggest is to debug the problem in a browser with great devtools, like Google Chrome.