dojoConfig (loader) replacement strategy for large JavaScript app with many files?

[Andy_Morgan]

I have a large web application used by most of our department that I've been maintaining since the early versions of the ArcGIS API / Maps SDK for JavaScript. Along with looking into the Widget to Component transition, there is one really important concept for which I need clarification and guidance. Will my dojoConfig.js file (entire code pasted below) continue to work after 4.x? (I'm currently on 4.27...you guys move too fast for some of us!)

I realize Dojo framework itself has long been removed, but this piece continues to work and appears to be supported through the last 4.x version (4.34). As I understand, it’s basically a Require.js remnant that I still need to use for defining custom paths in the AMD structure in order to break up large amounts of code and for having separate classes and HTML templates. Either it will become unsupported altogether in 5.x (immediately or within a few versions) or maybe there no good way to weave this into Web Components…in either case it would leave me scrambling to find a way to reference all my files in the Visual Studio (.NET Framework) project. I asked the Community about this a couple of years ago but never got a good answer. This will take a substantial amount of time for me to re-write, when converting to Components alone, so I don't want to waste any time with my approach over the next 6 months.

Do I need to re-arrange my code altogether, and if so how best to accomplish in today's modern JS design (preferably without relying on React/Angular/Vue frameworks)? I don't have much time to research these things, having just finished overseeing a double UN deployment and loaded with many other projects. I'm only knowledgeable in so many directions.

dojoConfig.js

let locationPath = location.pathname.replace(/\/[^/]+$/, '');
window.dojoConfig = {
    async: true, parseOnLoad: false, packages: [
        { name: "appJavascript", location: locationPath + "/js" },
        { name: "appJavascriptClasses", location: locationPath + "/js/classes" },
        { name: "appJavascriptChartJS", location: locationPath + "/js/chart_js" },
        { name: "appHtml", location: locationPath + "/html" }
    ],
    has: {
        "esri-native-promise": true
    }
}

This is used to call Javascript files from the "appJavascript/..." path 

define(["esri/config", "esri/geometry/SpatialReference", "esri/geometry/Extent", "esri/Map", "esri/views/MapView",
    "appJavascript/buttonHandlers", "appJavascript/layersLegend", "appJavascript/measure", "appJavascript/redline", 
], function (esriConfig, SpatialReference, Extent, Map, MapView, 
    appButtonHandlers, appLayersLegend, appMeasure, appRedline
) {

Here's a portion of my file structure to get an idea of the size:

Here's what else I know:

• 4.25 release notes saying that Dojo Loader is still included in the CDN
• AMD npm package and esri-loader are deprecated at 4.29

It seems like only a short matter of time before Dojo Loader is obsolete.