Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Dynamically lightup of injected packages as part of application closure #1597
Today, an application's closure is defined by its corresponding .deps.json file, which is statically computed and known at publish time. However, there are scenarios where certain packages may needed to be injected at runtime for them to become part of the application closure.
To support this, the entity wishing to inject packages would produce a lightup.deps.json and place it in a folder that mimic's the SharedFX layout. That is, the file will live in \Shared<SharedFXPackageName><SharedFrameworkVersion>\lightup.deps.json. The host will then be pointed to BaseFolder during application activation (either via an environment variable or command line argument) and will lookup lightup.deps.json using the SharedFX package name/version from the application's deps.json.
The contents of this file will then be part of the deps.json merge step in the host, where the app's deps.json will still override it incase of conflicting packages (like it does today for fx.deps.json).
@eerhardt When you deploy your application to Azure App Service it will automatically log to the right place, taking into account Azure specific configuration, without you needing to remember to explicitly turn it on or configure it before a problem occurs. That's one end goal that we would enable using this.
referenced this issue
Mar 4, 2017
Thus, they will not be able to use lightup components under a basedir - they will need to have an explicit path specified to the deps.json.
Thus, the question for you is - do you expect to have standalone apps participate in lightup? It looks like a scenario that will likely not work for them .