cli-node: add backstage.inline
Signed-off-by: Patrik Oldsberg <poldsberg@gmail.com>
This commit is contained in:
@@ -0,0 +1,5 @@
|
||||
---
|
||||
'@backstage/cli-node': patch
|
||||
---
|
||||
|
||||
Add definition for the new `backstage.inline` field in `package.json`.
|
||||
@@ -18,6 +18,7 @@ export interface BackstagePackageJson {
|
||||
backstage?: {
|
||||
role?: PackageRole;
|
||||
moved?: string;
|
||||
inline?: boolean;
|
||||
pluginId?: string | null;
|
||||
pluginPackage?: string;
|
||||
pluginPackages?: string[];
|
||||
|
||||
@@ -47,6 +47,15 @@ export interface BackstagePackageJson {
|
||||
role?: PackageRole;
|
||||
moved?: string;
|
||||
|
||||
/**
|
||||
* If set to `true`, the package will be treated as an internal package
|
||||
* where any imports will be inlined into the consuming package.
|
||||
*
|
||||
* When set to `true`, the top-level `private` field must be set to `true`
|
||||
* as well.
|
||||
*/
|
||||
inline?: boolean;
|
||||
|
||||
/**
|
||||
* The ID of the plugin if this is a plugin package. Must always be set for plugin and module packages, and may be set for library packages. A `null` value means that the package is explicitly not a plugin package.
|
||||
*/
|
||||
|
||||
Reference in New Issue
Block a user