Is that because ESRI stylesheet contains links to other assets on their site? In that case you could edit the links inside the local copy of that stylesheet to point to their server. If main.css is the culprit then it contains mostly links to images you can copy the images as a stop gap measure if you absolutely need to get you project working.
Does that make sense? Maybe I don’t understand some subtleties of your predicament.
@adongre I can’t create a new reply because of the limit on replies so I’m adding it here. Looks like this is the end of the discussion.
Sometimes from afar we don’t see the simple solution.
So maybe because I’m not understanding the problem domain I’m making this over-complicated.
Looking at your error and not having anything else
to go by, this is what I would try:
It looks like your browser is pulling in iconUtils.js from the ESRI site.
It’s minified js so it’s hard to set a breakpoint where you want.
I don’t know if you’re familiar with tools that redirect http requests?
For this purpose maybe something like ‘Requestly’ from Chrome Web Store.
Using Requestly you could redirect the request for ESRI iconUtils.js to a local dojo source iconUtils.js
that you have on a server you control (like your local development machine)
Start Chrome with --allow-running-insecure-content,
run your app and set the breakpoint at line 80 of that file, then
keep hitting ‘resume execution’ in the chrome debugger and loop until you get to the stylesheet that’s causing the error (or add some debug code - faster).
This way you can find out exactly where the stylesheet is coming from and get a better idea of what to do.
Maybe copy that stylesheet and change the links to files it references.
It sounds like it’s a big job but it might not be. Depends on how mission critical your downtime is.
Are there any ESRI users experiencing this issue? Maybe they can resolve this more effectively.