terser-webpack-plugin doesn't support IE11 - internet-explorer-11

I've to update uglify-webpack-plugin due to server restrictions, so I found terser-webpack-plugin is in the suggestion, however it doesn't support IE11 by default.
It just shows a syntax error in the vendor.js file, while loading the app.
Anyone faced this issue before, please guide me. Thanks.

Related

Pptxgenjs appears to not work in IE11 even with jszip#3.1.5

Having read the previous versions of this question from 2020 this issue appears to have reared it's head again. I have tried these demos with my current jszip#3.7.0 and with jszip 3.1.5 using it as my application jszip and overwriting the jszip within pptxgenjs.
When using pptxgenjs in IE11 (Windows 10) it appears to work in that no errors are reported, what does happen is the browser alerts the user that: "You'll need a new app to open this blob link". The only option that is available at this point is then to go to "Look for an app in the Microsoft Store" of which no apps are available.
What this says to me is that pptxgenjs has done its job and has passed the blob link to the browser and the browser has said I have no clue you'll need to find something to open this.
I've attempted to run the demos in the same Windows 10/IE11 setup and they seem to do worse. the live demo doesn't error or offer the ability to download an app to support opening the blob link. The react demo errors to the console: SCRIPT438: Object doesn't support property or method 'endsWith'. The Basic Demo in the complete library of demos fails like the live demo not returning an error or acknowledging anything.
Is this a known issue? Is there another step to help IE11 with the blob link? Can anyone else get the demos to work and I should be looking at something else? Any thoughts would be appreciated.
Edit:
Apologies if this wasn't clear, but the demos I was referring to were the pptxgenjs demos found here: https://gitbrent.github.io/PptxGenJS/demos/ so focusing on the initial demo named 'Live Demo' the code that is being run is here: https://gist.github.com/gitbrent/84acbcaab54be0eba83f5206ef6ddd95#file-pptxgenjs_demo-js
Running this with all other key browsers such as edge, firefox and chrome all 'download' the generated file whereas running the same demo in IE11 fails silently.

GatsbyJS - Can't resolve 'babel-runtime/helpers/possibleConstructorReturn'

I have a website that has been running fine for the last 4 months. Randomly the site stopped deploying on Netlify and I keep getting this error:
Generating development JavaScript bundle failed
Can't resolve 'babel-runtime/helpers/possibleConstructorReturn' in
'D:\Websites\nemesis-cheer\node_modules\react-script-tag\lib'
I have tried reinstalling babel, tried downgrading to different versions of babel/runtime, tried clearing cache and redeploying, Even tried reverting to old versions of the repo that I know for a fact deploy successfully and they still failed.
Here is my deploy log:
https://pastebin.com/raw/dH45EtP5
The repo is:
https://github.com/mont266/nemesis-cheerleading
Im really stomped here if anyone could help me out I would really appreciate it.
Try upgrading your babel/core dependency.
Now you have it locked to 7.13.8 (according to your package-lock.json), and it seems that the missing helpers are fixed in the 7.5.5, according to this stack trace.
I fixed the issue by reinstalling yarn and doing 'yarn add babel-runtime'. Must've gotten rid of the entire plugin at somepoint by accident.
I suggest you to try adding "babel-runtime": "6.26.0" to your package.json
Maybe it would fix an error for you

MultipleDefine xspClientDojo.js and dojo.js error

I having a problem with MultipleDefine xspClientDojo and dojo.
I have implemented select2 version 4.0.3 in a xPage theme.
But I get an error in the browser console, when loading the page.
The select2 fields are working, but some other dojo things are not.
Does anyone have a clue why this happens and how to resolve it?
Not familiar with "select2 version 4.0.3 theme", but multi-define error is usually the result of conflict of having more than one widget with the same id.
I found a simular problem here Xpages Getting Select 2 to work with current Extension Library
And the solution was to outcomment the AMD part in the start of the select2.js file.

Errors when installing fbctf

I'm trying to install Facebook Capture the flag. I get the errors show in screenshot.
The Server is the recommended Ubuntu 14.4. Server 64bit.
Does anyone know how to fix them? Thanks!
It seems like some kind of locale issue. Maybe you can check here:
"Do you have your locale settings configured correctly? The vendor folder won't get created properly if you don't. I recommend following the instructions on this thread: https://askubuntu.com/questions/162391/how-do-i-fix-my-locale-issue"
The install instructions have been updated and is working as expected now.

IE10 WebResource.axd does not download. Causes Error "'WebForm_DoPostBackWithOptions' is undefined"

It seems that in our case link buttons get this error in IE 10 only. In the couple hours of research I've done this appears to be a IE 10 bug.
Bug and Fix: ASP.NET fails to detect IE10 causing _doPostBack is undefined JavaScript error or maintain FF5 scrollbar position
I tried to download the KB hot fix and cannot, I get a page not found message. I also tried downloading the browser files in the blog post, the fix did not work.
This issue only occurs on our win server 2008 IIS 7 servers
iis 6 win server 2003 work fine.
Anyone else run into this and have a fix for it?
So you've walked through the steps Hanselman outlined here?
http://www.hanselman.com/blog/BugAndFixASPNETFailsToDetectIE10CausingDoPostBackIsUndefinedJavaScriptErrorOrMaintainFF5ScrollbarPosition.aspx
We had this same problem, got the hotfix files, applied them to the server and all is well for us.
The hot fix in Hanselman's blog fixed my issue.
http://www.hanselman.com/blog/BugAndFixASPNETFailsToDetectIE10CausingDoPostBackIsUndefinedJavaScriptErrorOrMaintainFF5ScrollbarPosition.aspx
I tried every patch that I've seen listed on the internet, including the ones listed in the referenced blog. The only thing that actually seemed to work was installing the .NET 4.5 Framework on the server.
Get it here: http://www.microsoft.com/en-us/download/details.aspx?id=30653
Hope this saves someone a few of the hours I've lost on this one.