elevate app.packages to no longer be experimental
Signed-off-by: Fredrik Adelöw <freben@gmail.com>
This commit is contained in:
+17
@@ -20,10 +20,27 @@ export interface Config {
|
||||
/**
|
||||
* @visibility frontend
|
||||
* @deepVisibility frontend
|
||||
* @deprecated This is no longer experimental; use `app.packages` instead.
|
||||
*/
|
||||
packages?: 'all' | { include?: string[]; exclude?: string[] };
|
||||
};
|
||||
|
||||
/**
|
||||
* Controls what packages are loaded by the new frontend system.
|
||||
*
|
||||
* @remarks
|
||||
*
|
||||
* When using the 'all' option, all feature packages that were added as
|
||||
* dependencies to the app will be loaded automatically.
|
||||
*
|
||||
* The `include` and `exclude` options can be used to more finely control
|
||||
* which individual package names to include or exclude.
|
||||
*
|
||||
* @visibility frontend
|
||||
* @deepVisibility frontend
|
||||
*/
|
||||
packages?: 'all' | { include?: string[]; exclude?: string[] };
|
||||
|
||||
routes?: {
|
||||
/**
|
||||
* Maps external route references to regular route references. Both the
|
||||
|
||||
Reference in New Issue
Block a user