common-types
Advanced tools
Comparing version 1.29.1 to 1.30.0
@@ -14,2 +14,7 @@ import { url } from "./aliases"; | ||
name: string; | ||
/** | ||
* If true, the package is considered private and pkg mgr will refuse to publish it regardless of the circumstances. | ||
* Setting this flag also unlocks some features that wouldn't make sense in published packages, such as workspaces. | ||
*/ | ||
private?: boolean; | ||
version: string; | ||
@@ -79,2 +84,28 @@ description?: string; | ||
}; | ||
/** | ||
* This field lists some extra information related to the dependencies listed in the dependencies and devDependencies fields. | ||
* In the context of a workspaced project most of these settings will affect all workspaces and as such must be specified at | ||
* the root of the project (except if noted otherwise, the dependenciesMeta field will be ignored if found within a workspace). | ||
*/ | ||
dependenciesMeta?: { | ||
fsevents: { | ||
/** | ||
* If false, the package will never be built (deny-list). This behavior is reversed when the enableScripts yarnrc setting is toggled off | ||
* - when that happens, only packages with built explicitly set to true will be executed (allow-list), and those with built explicitly | ||
* set to false will simply see their build script warnings downgraded into simple notices. | ||
*/ | ||
built: boolean; | ||
/** | ||
* If true, the build isn't required to succeed for the install to be considered a success, and the dependency may be skipped if its os | ||
* and cpu fields don't match the current system architecture. It's what the optionalDependencies field compiles down to. | ||
*/ | ||
optional: boolean; | ||
/** | ||
* If true, the specified package will be automatically unplugged at install time. This should only be needed for packages that contain | ||
* scripts in other languages than Javascript (for example nan contains C++ headers). | ||
*/ | ||
unplugged: boolean; | ||
}; | ||
[key: string]: unknown; | ||
}; | ||
dependencies?: IDictionary<string>; | ||
@@ -85,2 +116,10 @@ /** If someone is planning on downloading and using your module in their program, then they probably don't want or need to download and build the external test or documentation framework that you use. */ | ||
peerDependencies?: IDictionary<string>; | ||
/** This field lists some extra information related to the dependencies listed in the peerDependencies field. */ | ||
peerDepedenciesMeta?: { | ||
"react-dom": { | ||
/** If true, the selected peer dependency will be marked as optional by the package manager and the consumer omitting it won't be reported as an error. */ | ||
optional: boolean; | ||
}; | ||
[key: string]: unknown; | ||
}; | ||
/** This defines an array of package names that will be bundled when publishing the package. */ | ||
@@ -87,0 +126,0 @@ bundledDependencies?: string[]; |
import { minutes, scalar } from "../aliases"; | ||
import { arn } from "../aws"; | ||
import { IApiGatewayAliasConfig } from "../serverless-plugins/serverless-alias-plugin"; | ||
import { AWSRuntime, ServerlessFunctionMemorySize } from "./serverless"; | ||
@@ -48,3 +47,3 @@ import { IServerlessApiGatewayConfig } from "./serverless-api-gateway"; | ||
}; | ||
httpApi: { | ||
httpApi?: { | ||
id?: string; | ||
@@ -86,3 +85,3 @@ name?: string; | ||
stackParameters?: Record<string, string>; | ||
rollbackConfiguraiton?: { | ||
rollbackConfiguration?: { | ||
MonitoringTimeInMinutes: minutes; | ||
@@ -102,9 +101,2 @@ RollbackTriggers: Array<{ | ||
iamRoleStatements?: any[]; | ||
/** | ||
* **aliasStage** | ||
* | ||
* If using the the [serverless-aws-alias](https://github.com/HyperBrain/serverless-aws-alias) | ||
* plugin then you can configure settings here. | ||
*/ | ||
aliasStage?: IApiGatewayAliasConfig; | ||
logs?: { | ||
@@ -111,0 +103,0 @@ restApi?: IRestApiLogging; |
@@ -14,2 +14,7 @@ import { url } from "./aliases"; | ||
name: string; | ||
/** | ||
* If true, the package is considered private and pkg mgr will refuse to publish it regardless of the circumstances. | ||
* Setting this flag also unlocks some features that wouldn't make sense in published packages, such as workspaces. | ||
*/ | ||
private?: boolean; | ||
version: string; | ||
@@ -79,2 +84,28 @@ description?: string; | ||
}; | ||
/** | ||
* This field lists some extra information related to the dependencies listed in the dependencies and devDependencies fields. | ||
* In the context of a workspaced project most of these settings will affect all workspaces and as such must be specified at | ||
* the root of the project (except if noted otherwise, the dependenciesMeta field will be ignored if found within a workspace). | ||
*/ | ||
dependenciesMeta?: { | ||
fsevents: { | ||
/** | ||
* If false, the package will never be built (deny-list). This behavior is reversed when the enableScripts yarnrc setting is toggled off | ||
* - when that happens, only packages with built explicitly set to true will be executed (allow-list), and those with built explicitly | ||
* set to false will simply see their build script warnings downgraded into simple notices. | ||
*/ | ||
built: boolean; | ||
/** | ||
* If true, the build isn't required to succeed for the install to be considered a success, and the dependency may be skipped if its os | ||
* and cpu fields don't match the current system architecture. It's what the optionalDependencies field compiles down to. | ||
*/ | ||
optional: boolean; | ||
/** | ||
* If true, the specified package will be automatically unplugged at install time. This should only be needed for packages that contain | ||
* scripts in other languages than Javascript (for example nan contains C++ headers). | ||
*/ | ||
unplugged: boolean; | ||
}; | ||
[key: string]: unknown; | ||
}; | ||
dependencies?: IDictionary<string>; | ||
@@ -85,2 +116,10 @@ /** If someone is planning on downloading and using your module in their program, then they probably don't want or need to download and build the external test or documentation framework that you use. */ | ||
peerDependencies?: IDictionary<string>; | ||
/** This field lists some extra information related to the dependencies listed in the peerDependencies field. */ | ||
peerDepedenciesMeta?: { | ||
"react-dom": { | ||
/** If true, the selected peer dependency will be marked as optional by the package manager and the consumer omitting it won't be reported as an error. */ | ||
optional: boolean; | ||
}; | ||
[key: string]: unknown; | ||
}; | ||
/** This defines an array of package names that will be bundled when publishing the package. */ | ||
@@ -87,0 +126,0 @@ bundledDependencies?: string[]; |
import { minutes, scalar } from "../aliases"; | ||
import { arn } from "../aws"; | ||
import { IApiGatewayAliasConfig } from "../serverless-plugins/serverless-alias-plugin"; | ||
import { AWSRuntime, ServerlessFunctionMemorySize } from "./serverless"; | ||
@@ -48,3 +47,3 @@ import { IServerlessApiGatewayConfig } from "./serverless-api-gateway"; | ||
}; | ||
httpApi: { | ||
httpApi?: { | ||
id?: string; | ||
@@ -86,3 +85,3 @@ name?: string; | ||
stackParameters?: Record<string, string>; | ||
rollbackConfiguraiton?: { | ||
rollbackConfiguration?: { | ||
MonitoringTimeInMinutes: minutes; | ||
@@ -102,9 +101,2 @@ RollbackTriggers: Array<{ | ||
iamRoleStatements?: any[]; | ||
/** | ||
* **aliasStage** | ||
* | ||
* If using the the [serverless-aws-alias](https://github.com/HyperBrain/serverless-aws-alias) | ||
* plugin then you can configure settings here. | ||
*/ | ||
aliasStage?: IApiGatewayAliasConfig; | ||
logs?: { | ||
@@ -111,0 +103,0 @@ restApi?: IRestApiLogging; |
{ | ||
"name": "common-types", | ||
"version": "1.29.1", | ||
"version": "1.30.0", | ||
"description": "Common Types for Typescript", | ||
@@ -5,0 +5,0 @@ "repository": "https://github.com/lifegadget/common-types", |
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
456949
10853