To prevent additional build sizes of applications, @osjs/gui could be provded by the service provider this package provides via window.osjsGui just as the UMD module does.
As far as I know there's no way to use a webpack generated module as both a global and included module. So if I were to do window.osjsGui = osjsGui where import * as osjsGui from 'index.js' would not create a ES5 compatible object since they all will be of the type Module.
Would be nice to sort this out without loading an additional @osjs/gui bundle file.
This way apps can just use this in the webpack config instead of having it as a dependency:
To prevent additional build sizes of applications,
@osjs/gui
could be provded by the service provider this package provides viawindow.osjsGui
just as the UMD module does.As far as I know there's no way to use a webpack generated module as both a global and included module. So if I were to do
window.osjsGui = osjsGui
whereimport * as osjsGui from 'index.js'
would not create a ES5 compatible object since they all will be of the typeModule
.Would be nice to sort this out without loading an additional
@osjs/gui
bundle file.This way apps can just use this in the webpack config instead of having it as a dependency:
No changes required in the actual implementations: