Hi all,
We are an Oracle Health client, and OH have recently advised that the frameworks Cerner used to maintain are in maintenance mode only and not recommended for new development. Oracle Jet was suggested as a go-forward option for new web development. I'm investigating the use of Jet v19 as a framework to plug into the existing Oracle Health Foundation EHR - previously Cerner Millennium - to meet some specific data visualisation needs.
The application runs in Microsoft Edge WebView2, and is served over an IBM Websphere server (which I've heard is probably going to get migrated to Weblogic). The problem with delpoying a custom website to this server is the technique that is necessary:
- Copy all files for the site over Citrix session into a remote folder,
- Trigger a refresh, which copies the folder to the several Websphere hosts.
Unfortunately, a large number of files makes deployment very slow or even impossible, for both steps.
The basic starter navbar template seems to generate 82mb of content over 7k files in release mode, which is not compatible with this deployment technique. We also can't switch to deploying a WAR file as we don't control the Websphere server ourselves.
I tried switching my project from requirejs to webpack, and it does result in a much smaller number and size of files. I had to spend some time optimising the filenames (removing content hashes & other issues), but later got stuck because the core pack objects weren't seeing their redwood style applying correctly - they appeared to be basically unstyled. This issue went away when moving back to requirejs.
Then I tried optimising the requirejs build using ojet build -r --optimize and editing src/js/main.js, and it appears that even “generateSourceMaps: false, preserveLicenseComments: false, ” are being completely ignored when added to main.js.
Given the difficulties I had trying to use webpack, does anyone have a suggestion for the best path to producing a release with the fewest number of required files, ideally less than 100? if it's only possible with webpack, is there a recommended configuration that produces a correct build and filenames that stay consistent with each build?
Thanks, Hamish.