npm - cloudstructs - Versions diffs - 0.9.42 → 0.9.43 - Mend

cloudstructs 0.9.42 → 0.9.43

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (349) hide show

package/.jsii CHANGED Viewed

@@ -7,9 +7,9 @@
     ]
   },
   "bundled": {
-    "@slack/web-api": "^7.11.0",
+    "@slack/web-api": "^7.12.0",
     "got": "^11.8.6",
-    "mjml": "^4.16.1"
+    "mjml": "^4.17.0"
   },
   "dependencies": {
     "aws-cdk-lib": "^2.133.0",
@@ -3654,7 +3654,7 @@
     "stability": "stable"
   },
   "homepage": "https://github.com/jogold/cloudstructs.git",
-  "jsiiVersion": "5.9.9 (build 2b878e9)",
+  "jsiiVersion": "5.9.14 (build 9fc28bd)",
   "keywords": [
     "cdk"
   ],
@@ -7820,6 +7820,6 @@
       "symbolId": "src/url-shortener/index:UrlShortenerProps"
     }
   },
-  "version": "0.9.42",
-  "fingerprint": "hD82Jv32xooFFPd5sy/jkZ7y+F5V8SF8m330m0ul6P8="
+  "version": "0.9.43",
+  "fingerprint": "rVD1atFY3TK6dgg5kKO2o+Co2nmifAL4eLNMrRLGbrI="
 }

package/API.md CHANGED Viewed

@@ -64,7 +64,7 @@ Returns a string representation of this construct.
 ---
-##### ~~`isConstruct`~~ <a name="isConstruct" id="cloudstructs.CodeCommitMirror.isConstruct"></a>
+##### `isConstruct` <a name="isConstruct" id="cloudstructs.CodeCommitMirror.isConstruct"></a>
 ```typescript
 import { CodeCommitMirror } from 'cloudstructs'
@@ -74,6 +74,20 @@ CodeCommitMirror.isConstruct(x: any)
 Checks if `x` is a construct.
+Use this method instead of `instanceof` to properly detect `Construct`
+instances, even when the construct library is symlinked.
+Explanation: in JavaScript, multiple copies of the `constructs` library on
+disk are seen as independent, completely different libraries. As a
+consequence, the class `Construct` in each copy of the `constructs` library
+is seen as a different class, and an instance of one class will not test as
+`instanceof` the other class. `npm install` will not create installations
+like this, but users may manually symlink construct libraries together or
+use a monorepo tool: in those cases, multiple copies of the `constructs`
+library can be accidentally installed, and `instanceof` will behave
+unpredictably. It is safest to avoid using `instanceof`, and using
+this type-testing method instead.
 ###### `x`<sup>Required</sup> <a name="x" id="cloudstructs.CodeCommitMirror.isConstruct.parameter.x"></a>
 - *Type:* any
@@ -165,7 +179,7 @@ Returns a string representation of this construct.
 ---
-##### ~~`isConstruct`~~ <a name="isConstruct" id="cloudstructs.DmarcReporter.isConstruct"></a>
+##### `isConstruct` <a name="isConstruct" id="cloudstructs.DmarcReporter.isConstruct"></a>
 ```typescript
 import { DmarcReporter } from 'cloudstructs'
@@ -175,6 +189,20 @@ DmarcReporter.isConstruct(x: any)
 Checks if `x` is a construct.
+Use this method instead of `instanceof` to properly detect `Construct`
+instances, even when the construct library is symlinked.
+Explanation: in JavaScript, multiple copies of the `constructs` library on
+disk are seen as independent, completely different libraries. As a
+consequence, the class `Construct` in each copy of the `constructs` library
+is seen as a different class, and an instance of one class will not test as
+`instanceof` the other class. `npm install` will not create installations
+like this, but users may manually symlink construct libraries together or
+use a monorepo tool: in those cases, multiple copies of the `constructs`
+library can be accidentally installed, and `instanceof` will behave
+unpredictably. It is safest to avoid using `instanceof`, and using
+this type-testing method instead.
 ###### `x`<sup>Required</sup> <a name="x" id="cloudstructs.DmarcReporter.isConstruct.parameter.x"></a>
 - *Type:* any
@@ -266,7 +294,7 @@ Returns a string representation of this construct.
 ---
-##### ~~`isConstruct`~~ <a name="isConstruct" id="cloudstructs.EcsServiceRoller.isConstruct"></a>
+##### `isConstruct` <a name="isConstruct" id="cloudstructs.EcsServiceRoller.isConstruct"></a>
 ```typescript
 import { EcsServiceRoller } from 'cloudstructs'
@@ -276,6 +304,20 @@ EcsServiceRoller.isConstruct(x: any)
 Checks if `x` is a construct.
+Use this method instead of `instanceof` to properly detect `Construct`
+instances, even when the construct library is symlinked.
+Explanation: in JavaScript, multiple copies of the `constructs` library on
+disk are seen as independent, completely different libraries. As a
+consequence, the class `Construct` in each copy of the `constructs` library
+is seen as a different class, and an instance of one class will not test as
+`instanceof` the other class. `npm install` will not create installations
+like this, but users may manually symlink construct libraries together or
+use a monorepo tool: in those cases, multiple copies of the `constructs`
+library can be accidentally installed, and `instanceof` will behave
+unpredictably. It is safest to avoid using `instanceof`, and using
+this type-testing method instead.
 ###### `x`<sup>Required</sup> <a name="x" id="cloudstructs.EcsServiceRoller.isConstruct.parameter.x"></a>
 - *Type:* any
@@ -367,7 +409,7 @@ Returns a string representation of this construct.
 ---
-##### ~~`isConstruct`~~ <a name="isConstruct" id="cloudstructs.EmailReceiver.isConstruct"></a>
+##### `isConstruct` <a name="isConstruct" id="cloudstructs.EmailReceiver.isConstruct"></a>
 ```typescript
 import { EmailReceiver } from 'cloudstructs'
@@ -377,6 +419,20 @@ EmailReceiver.isConstruct(x: any)
 Checks if `x` is a construct.
+Use this method instead of `instanceof` to properly detect `Construct`
+instances, even when the construct library is symlinked.
+Explanation: in JavaScript, multiple copies of the `constructs` library on
+disk are seen as independent, completely different libraries. As a
+consequence, the class `Construct` in each copy of the `constructs` library
+is seen as a different class, and an instance of one class will not test as
+`instanceof` the other class. `npm install` will not create installations
+like this, but users may manually symlink construct libraries together or
+use a monorepo tool: in those cases, multiple copies of the `constructs`
+library can be accidentally installed, and `instanceof` will behave
+unpredictably. It is safest to avoid using `instanceof`, and using
+this type-testing method instead.
 ###### `x`<sup>Required</sup> <a name="x" id="cloudstructs.EmailReceiver.isConstruct.parameter.x"></a>
 - *Type:* any
@@ -494,7 +550,7 @@ Returns a string representation of this construct.
 ---
-##### ~~`isConstruct`~~ <a name="isConstruct" id="cloudstructs.MjmlTemplate.isConstruct"></a>
+##### `isConstruct` <a name="isConstruct" id="cloudstructs.MjmlTemplate.isConstruct"></a>
 ```typescript
 import { MjmlTemplate } from 'cloudstructs'
@@ -504,6 +560,20 @@ MjmlTemplate.isConstruct(x: any)
 Checks if `x` is a construct.
+Use this method instead of `instanceof` to properly detect `Construct`
+instances, even when the construct library is symlinked.
+Explanation: in JavaScript, multiple copies of the `constructs` library on
+disk are seen as independent, completely different libraries. As a
+consequence, the class `Construct` in each copy of the `constructs` library
+is seen as a different class, and an instance of one class will not test as
+`instanceof` the other class. `npm install` will not create installations
+like this, but users may manually symlink construct libraries together or
+use a monorepo tool: in those cases, multiple copies of the `constructs`
+library can be accidentally installed, and `instanceof` will behave
+unpredictably. It is safest to avoid using `instanceof`, and using
+this type-testing method instead.
 ###### `x`<sup>Required</sup> <a name="x" id="cloudstructs.MjmlTemplate.isConstruct.parameter.x"></a>
 - *Type:* any
@@ -618,6 +688,20 @@ SamlIdentityProvider.isConstruct(x: any)
 Checks if `x` is a construct.
+Use this method instead of `instanceof` to properly detect `Construct`
+instances, even when the construct library is symlinked.
+Explanation: in JavaScript, multiple copies of the `constructs` library on
+disk are seen as independent, completely different libraries. As a
+consequence, the class `Construct` in each copy of the `constructs` library
+is seen as a different class, and an instance of one class will not test as
+`instanceof` the other class. `npm install` will not create installations
+like this, but users may manually symlink construct libraries together or
+use a monorepo tool: in those cases, multiple copies of the `constructs`
+library can be accidentally installed, and `instanceof` will behave
+unpredictably. It is safest to avoid using `instanceof`, and using
+this type-testing method instead.
 ###### `x`<sup>Required</sup> <a name="x" id="cloudstructs.SamlIdentityProvider.isConstruct.parameter.x"></a>
 - *Type:* any
@@ -728,7 +812,7 @@ Returns a string representation of this construct.
 ---
-##### ~~`isConstruct`~~ <a name="isConstruct" id="cloudstructs.SlackApp.isConstruct"></a>
+##### `isConstruct` <a name="isConstruct" id="cloudstructs.SlackApp.isConstruct"></a>
 ```typescript
 import { SlackApp } from 'cloudstructs'
@@ -738,6 +822,20 @@ SlackApp.isConstruct(x: any)
 Checks if `x` is a construct.
+Use this method instead of `instanceof` to properly detect `Construct`
+instances, even when the construct library is symlinked.
+Explanation: in JavaScript, multiple copies of the `constructs` library on
+disk are seen as independent, completely different libraries. As a
+consequence, the class `Construct` in each copy of the `constructs` library
+is seen as a different class, and an instance of one class will not test as
+`instanceof` the other class. `npm install` will not create installations
+like this, but users may manually symlink construct libraries together or
+use a monorepo tool: in those cases, multiple copies of the `constructs`
+library can be accidentally installed, and `instanceof` will behave
+unpredictably. It is safest to avoid using `instanceof`, and using
+this type-testing method instead.
 ###### `x`<sup>Required</sup> <a name="x" id="cloudstructs.SlackApp.isConstruct.parameter.x"></a>
 - *Type:* any
@@ -917,7 +1015,7 @@ Returns a string representation of this construct.
 ---
-##### ~~`isConstruct`~~ <a name="isConstruct" id="cloudstructs.SlackEvents.isConstruct"></a>
+##### `isConstruct` <a name="isConstruct" id="cloudstructs.SlackEvents.isConstruct"></a>
 ```typescript
 import { SlackEvents } from 'cloudstructs'
@@ -927,6 +1025,20 @@ SlackEvents.isConstruct(x: any)
 Checks if `x` is a construct.
+Use this method instead of `instanceof` to properly detect `Construct`
+instances, even when the construct library is symlinked.
+Explanation: in JavaScript, multiple copies of the `constructs` library on
+disk are seen as independent, completely different libraries. As a
+consequence, the class `Construct` in each copy of the `constructs` library
+is seen as a different class, and an instance of one class will not test as
+`instanceof` the other class. `npm install` will not create installations
+like this, but users may manually symlink construct libraries together or
+use a monorepo tool: in those cases, multiple copies of the `constructs`
+library can be accidentally installed, and `instanceof` will behave
+unpredictably. It is safest to avoid using `instanceof`, and using
+this type-testing method instead.
 ###### `x`<sup>Required</sup> <a name="x" id="cloudstructs.SlackEvents.isConstruct.parameter.x"></a>
 - *Type:* any
@@ -1031,7 +1143,7 @@ Returns a string representation of this construct.
 ---
-##### ~~`isConstruct`~~ <a name="isConstruct" id="cloudstructs.SlackTextract.isConstruct"></a>
+##### `isConstruct` <a name="isConstruct" id="cloudstructs.SlackTextract.isConstruct"></a>
 ```typescript
 import { SlackTextract } from 'cloudstructs'
@@ -1041,6 +1153,20 @@ SlackTextract.isConstruct(x: any)
 Checks if `x` is a construct.
+Use this method instead of `instanceof` to properly detect `Construct`
+instances, even when the construct library is symlinked.
+Explanation: in JavaScript, multiple copies of the `constructs` library on
+disk are seen as independent, completely different libraries. As a
+consequence, the class `Construct` in each copy of the `constructs` library
+is seen as a different class, and an instance of one class will not test as
+`instanceof` the other class. `npm install` will not create installations
+like this, but users may manually symlink construct libraries together or
+use a monorepo tool: in those cases, multiple copies of the `constructs`
+library can be accidentally installed, and `instanceof` will behave
+unpredictably. It is safest to avoid using `instanceof`, and using
+this type-testing method instead.
 ###### `x`<sup>Required</sup> <a name="x" id="cloudstructs.SlackTextract.isConstruct.parameter.x"></a>
 - *Type:* any
@@ -1132,7 +1258,7 @@ Returns a string representation of this construct.
 ---
-##### ~~`isConstruct`~~ <a name="isConstruct" id="cloudstructs.SslServerTest.isConstruct"></a>
+##### `isConstruct` <a name="isConstruct" id="cloudstructs.SslServerTest.isConstruct"></a>
 ```typescript
 import { SslServerTest } from 'cloudstructs'
@@ -1142,6 +1268,20 @@ SslServerTest.isConstruct(x: any)
 Checks if `x` is a construct.
+Use this method instead of `instanceof` to properly detect `Construct`
+instances, even when the construct library is symlinked.
+Explanation: in JavaScript, multiple copies of the `constructs` library on
+disk are seen as independent, completely different libraries. As a
+consequence, the class `Construct` in each copy of the `constructs` library
+is seen as a different class, and an instance of one class will not test as
+`instanceof` the other class. `npm install` will not create installations
+like this, but users may manually symlink construct libraries together or
+use a monorepo tool: in those cases, multiple copies of the `constructs`
+library can be accidentally installed, and `instanceof` will behave
+unpredictably. It is safest to avoid using `instanceof`, and using
+this type-testing method instead.
 ###### `x`<sup>Required</sup> <a name="x" id="cloudstructs.SslServerTest.isConstruct.parameter.x"></a>
 - *Type:* any
@@ -1246,7 +1386,7 @@ Returns a string representation of this construct.
 ---
-##### ~~`isConstruct`~~ <a name="isConstruct" id="cloudstructs.StateMachineCustomResourceProvider.isConstruct"></a>
+##### `isConstruct` <a name="isConstruct" id="cloudstructs.StateMachineCustomResourceProvider.isConstruct"></a>
 ```typescript
 import { StateMachineCustomResourceProvider } from 'cloudstructs'
@@ -1256,6 +1396,20 @@ StateMachineCustomResourceProvider.isConstruct(x: any)
 Checks if `x` is a construct.
+Use this method instead of `instanceof` to properly detect `Construct`
+instances, even when the construct library is symlinked.
+Explanation: in JavaScript, multiple copies of the `constructs` library on
+disk are seen as independent, completely different libraries. As a
+consequence, the class `Construct` in each copy of the `constructs` library
+is seen as a different class, and an instance of one class will not test as
+`instanceof` the other class. `npm install` will not create installations
+like this, but users may manually symlink construct libraries together or
+use a monorepo tool: in those cases, multiple copies of the `constructs`
+library can be accidentally installed, and `instanceof` will behave
+unpredictably. It is safest to avoid using `instanceof`, and using
+this type-testing method instead.
 ###### `x`<sup>Required</sup> <a name="x" id="cloudstructs.StateMachineCustomResourceProvider.isConstruct.parameter.x"></a>
 - *Type:* any
@@ -1360,7 +1514,7 @@ Returns a string representation of this construct.
 ---
-##### ~~`isConstruct`~~ <a name="isConstruct" id="cloudstructs.StaticWebsite.isConstruct"></a>
+##### `isConstruct` <a name="isConstruct" id="cloudstructs.StaticWebsite.isConstruct"></a>
 ```typescript
 import { StaticWebsite } from 'cloudstructs'
@@ -1370,6 +1524,20 @@ StaticWebsite.isConstruct(x: any)
 Checks if `x` is a construct.
+Use this method instead of `instanceof` to properly detect `Construct`
+instances, even when the construct library is symlinked.
+Explanation: in JavaScript, multiple copies of the `constructs` library on
+disk are seen as independent, completely different libraries. As a
+consequence, the class `Construct` in each copy of the `constructs` library
+is seen as a different class, and an instance of one class will not test as
+`instanceof` the other class. `npm install` will not create installations
+like this, but users may manually symlink construct libraries together or
+use a monorepo tool: in those cases, multiple copies of the `constructs`
+library can be accidentally installed, and `instanceof` will behave
+unpredictably. It is safest to avoid using `instanceof`, and using
+this type-testing method instead.
 ###### `x`<sup>Required</sup> <a name="x" id="cloudstructs.StaticWebsite.isConstruct.parameter.x"></a>
 - *Type:* any
@@ -1500,7 +1668,7 @@ Returns a string representation of this construct.
 ---
-##### ~~`isConstruct`~~ <a name="isConstruct" id="cloudstructs.ToolkitCleaner.isConstruct"></a>
+##### `isConstruct` <a name="isConstruct" id="cloudstructs.ToolkitCleaner.isConstruct"></a>
 ```typescript
 import { ToolkitCleaner } from 'cloudstructs'
@@ -1510,6 +1678,20 @@ ToolkitCleaner.isConstruct(x: any)
 Checks if `x` is a construct.
+Use this method instead of `instanceof` to properly detect `Construct`
+instances, even when the construct library is symlinked.
+Explanation: in JavaScript, multiple copies of the `constructs` library on
+disk are seen as independent, completely different libraries. As a
+consequence, the class `Construct` in each copy of the `constructs` library
+is seen as a different class, and an instance of one class will not test as
+`instanceof` the other class. `npm install` will not create installations
+like this, but users may manually symlink construct libraries together or
+use a monorepo tool: in those cases, multiple copies of the `constructs`
+library can be accidentally installed, and `instanceof` will behave
+unpredictably. It is safest to avoid using `instanceof`, and using
+this type-testing method instead.
 ###### `x`<sup>Required</sup> <a name="x" id="cloudstructs.ToolkitCleaner.isConstruct.parameter.x"></a>
 - *Type:* any
@@ -1616,7 +1798,7 @@ Grant access to invoke the URL shortener if protected by IAM authorization.
 ---
-##### ~~`isConstruct`~~ <a name="isConstruct" id="cloudstructs.UrlShortener.isConstruct"></a>
+##### `isConstruct` <a name="isConstruct" id="cloudstructs.UrlShortener.isConstruct"></a>
 ```typescript
 import { UrlShortener } from 'cloudstructs'
@@ -1626,6 +1808,20 @@ UrlShortener.isConstruct(x: any)
 Checks if `x` is a construct.
+Use this method instead of `instanceof` to properly detect `Construct`
+instances, even when the construct library is symlinked.
+Explanation: in JavaScript, multiple copies of the `constructs` library on
+disk are seen as independent, completely different libraries. As a
+consequence, the class `Construct` in each copy of the `constructs` library
+is seen as a different class, and an instance of one class will not test as
+`instanceof` the other class. `npm install` will not create installations
+like this, but users may manually symlink construct libraries together or
+use a monorepo tool: in those cases, multiple copies of the `constructs`
+library can be accidentally installed, and `instanceof` will behave
+unpredictably. It is safest to avoid using `instanceof`, and using
+this type-testing method instead.
 ###### `x`<sup>Required</sup> <a name="x" id="cloudstructs.UrlShortener.isConstruct.parameter.x"></a>
 - *Type:* any