I the last release css file for find admin is located at https://dl.episerver.net/current/epi-find/epi.css but it does not exist there.
The strange part here is why there is a request to http://dl.episerver.net/ rather than the expected https://dl.episerver.net/.
You haven't reconfigured anything in regarding the base path, have you?
Regarding "current" that is used as a fallback only. We're looking into the error regarding that but if you get an url referring to that path there is already some problem occuring.
As far as combining scripts go, it's a conscious desicion that we will distribute the resources from the cloud to be able to load them in separate packages (layers) when desired and also be able to change UI version without end customer or partner interaction and in the future also update sources in background while UI is running.
The issue with any extra requests should be virtually non existent once files are cached.
Joakim: I see the point. Be careful to not end upp like in many wordpress installations with a lot of extra request for all plugins. Can be 100 of them. As you say the files are cached but I think it's very important to have a fast load of the start page, when the files aren't cached.
For now it's not a big problem with just one "plug-in".
We have had some problems with the public scripts and css at dl.episerver.net. E.g. http://dl.episerver.net/8.2.12/epi-find/epi.css
Today we do get "504 - Gateway Timeout". This is a problem even for public users on our web page because of the find.js script that is loaded on all pages. This error will cause javascript runtime errors on the page.
Wouldn't it be a better solution to include theses css and js files in the nuget-package. Then we will also be able to minify and combine all scripts and stylesheets with the other ones. Otherwise all users will have to do some extra requests to the server.