You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Set output.publicPath
to the public URL (relative or absolute) of the output directory, i.e. where
all the feature app chunks are hosted.
Since this is not always known at compile time, it can be left blank and set
dynamically at runtime in the feature app's entry file using the global
variable __webpack_public_path__. To help with that, createInstance is
called with an env object that includes the publicPath of the feature
app:
Closes#119, #167, #189, #151, #138, #145, #146
This commit replaces the large README and scattered package READMEs. In the future, the WebSite will be the gateway to documentation. GitHub will then only be used for development/collaboration.
Out of date
Dynamic Code Splitting With Webpack
Feature apps can use
webpack's dynamic code splitting feature
using the
import()
syntax.To make this work for multiple feature apps living together on the Feature Hub
two configurations need to be made:
Set a unique value for
output.jsonpFunction
,e.g.
"webpackJsonpMyFeatureApp"
.Set
output.publicPath
to the public URL (relative or absolute) of the output directory, i.e. where
all the feature app chunks are hosted.
Since this is not always known at compile time, it can be left blank and set
dynamically at runtime in the feature app's entry file using the global
variable
__webpack_public_path__
. To help with that,createInstance
iscalled with an
env
object that includes thepublicPath
of the featureapp:
The text was updated successfully, but these errors were encountered: