@mrgrain/cdk-esbuild 3.3.0 → 3.4.0

package/.gitattributes

@@ -6,7 +6,6 @@
 /.github/pull_request_template.md linguist-generated
 /.github/workflows/build.yml linguist-generated
 /.github/workflows/pull-request-lint.yml linguist-generated
-/.github/workflows/stale.yml linguist-generated
 /.gitignore linguist-generated
 /.mergify.yml linguist-generated
 /.npmignore linguist-generated

package/.jsii

@@ -2777,7 +2777,7 @@
     "stability": "stable"
   },
   "homepage": "https://github.com/mrgrain/cdk-esbuild",
-  "jsiiVersion": "1.54.0 (build b1b977a)",
+  "jsiiVersion": "1.57.0 (build f614666)",
   "keywords": [
     "aws-cdk",
     "bundler",
@@ -2800,7 +2800,7 @@
   },
   "name": "@mrgrain/cdk-esbuild",
   "readme": {
-    "markdown": "# cdk-esbuild\n\n_CDK constructs for [esbuild](https://github.com/evanw/esbuild), an extremely fast JavaScript bundler_\n\n> ⚠️ This version is compatible with AWS CDK v2. For the previous, AWS CDK v1 compatible release, see [cdk-esbuild@v2](https://github.com/mrgrain/cdk-esbuild/tree/v2)\n\n[Getting started](#getting-started) | [Migrating to v3](#migrating-to-v3) |\n[Documentation](#documentation) | [API Reference](#api-reference) | [Versioning](#versioning)\n\n## Why?\n\n_esbuild_ is an extremely fast bundler and minifier for Typescript and JavaScript.\nThis package makes _esbuild_ available to deploy lambda functions, static websites or to publish build artefacts (assets) for further use.\n\nAWS CDK [supports _esbuild_ with Lambda Functions](https://docs.aws.amazon.com/cdk/api/latest/docs/aws-lambda-nodejs-readme.html). However the implementation cannot be used with any other Constructs and doesn't expose all of _esbuild_'s build interface.\n\nThis package is running _esbuild_ directly in Node.js and bypasses Docker which the AWS CDK implementation uses. The approach is quicker and easier to use for Node.js users, but incompatible with other languages.\n\n**Production readiness**\n\nThis package is generally stable and ready to be used in production, as many do. However _esbuild_ not yet released a version 1.0.0 yet and its API is still in active development. Please check their guide on [production readiness](https://esbuild.github.io/faq/#production-readiness).\n\nNotably upgrades of the _esbuild_ minimum version requirement will be introduced in **minor versions** of this package and will inherit breaking changes from _esbuild_.\n\n## Getting started\n\nInstall `cdk-esbuild`:\n\n```\nnpm install @mrgrain/cdk-esbuild@3\n```\n\nIf _peer_ and _optional dependencies_ are not installed automatically (e.g. when using npm v4-6), please use this command to install all of them:\n\n```\nnpm install @mrgrain/cdk-esbuild@3 esbuild\n```\n\n### AWS Lambda: Serverless function\n\n> 💡 See [Lambda Function](examples/lambda) for a complete working example of a how to deploy a lambda function.\n\nUse `TypeScriptCode` as the `code` of a [lambda function](https://docs.aws.amazon.com/cdk/api/v2/docs/aws-cdk-lib.aws_lambda.Function.html#code):\n\n```ts\nimport * as lambda from \"aws-cdk-lib/aws-lambda\";\nimport { TypeScriptCode } from \"@mrgrain/cdk-esbuild\";\n\nconst bundledCode = new TypeScriptCode(\"src/index.ts\");\n\nconst fn = new lambda.Function(stack, \"MyFunction\", {\n  runtime: lambda.Runtime.NODEJS_14_X,\n  handler: \"index.handler\",\n  code: bundledCode,\n});\n```\n\n### AWS S3: Static Website\n\n> 💡 See [Static Website with React](examples/website) for a complete working example of a how to deploy a React app to S3.\n\nUse `TypeScriptSource` as one of the `sources` of a [static website deployment](https://docs.aws.amazon.com/cdk/api/latest/docs/aws-s3-deployment-readme.html#roadmap):\n\n```ts\nimport * as s3 from \"aws-cdk-lib/aws-s3\";\nimport * as s3deploy from \"aws-cdk-lib/aws-s3-deployment\";\nimport { TypeScriptSource } from \"@mrgrain/cdk-esbuild\";\n\nconst websiteBundle = new TypeScriptSource(\"src/index.tsx\");\n\nconst websiteBucket = new s3.Bucket(stack, \"WebsiteBucket\", {\n  autoDeleteObjects: true,\n  publicReadAccess: true,\n  removalPolicy: RemovalPolicy.DESTROY,\n  websiteIndexDocument: \"index.html\",\n});\n\nnew s3deploy.BucketDeployment(stack, \"DeployWebsite\", {\n  destinationBucket: websiteBucket,\n  sources: [websiteBundle],\n});\n```\n\n### Amazon CloudWatch Synthetics: Canary monitoring\n\n> 💡 See [Monitored Website](examples/website) for a complete working example of a deployed and monitored website.\n\nSynthetics runs a canary to produce traffic to an application for monitoring purposes. Use `TypeScriptCode` as the `code` of a Canary test:\n\n> ℹ️ This feature depends on the `@aws-cdk/aws-synthetics-alpha` package which is a developer preview. You may need to update your source code when upgrading to a newer version of this package.\n>\n> ```\n> npm i @aws-cdk/aws-synthetics-alpha\n> ```\n\n```ts\nimport * as synthetics from \"@aws-cdk/aws-synthetics-alpha\";\nimport { TypeScriptCode } from \"@mrgrain/cdk-esbuild\";\n\nconst bundledCode = new TypeScriptCode(\"src/index.ts\", {\n  buildOptions: {\n    outdir: \"nodejs/node_modules\", // This is required by Synthetics\n  },\n});\n\nconst canary = new synthetics.Canary(stack, \"MyCanary\", {\n  runtime: synthetics.Runtime.SYNTHETICS_NODEJS_PUPPETEER_3_2,\n  test: synthetics.Test.custom({\n    code: bundledCode,\n    handler: \"index.handler\",\n  });\n});\n```\n\n# Documentation\n\nThe package exports various different constructs for use with existing CDK features. A major guiding design principal for this package is to _extend, don't replace_. Expect constructs that you can provide as props, not complete replacements.\n\nFor use in **Lambda Functions** and **Synthetic Canaries**, the following classes implement `lambda.Code` ([reference](https://docs.aws.amazon.com/cdk/api/v2/docs/aws-cdk-lib.aws_lambda.Code.html)) and `synthetics.Code` ([reference](https://docs.aws.amazon.com/cdk/api/v2/docs/@aws-cdk_aws-synthetics-alpha.Code.html)):\n\n- `TypeScriptCode` & `JavaScriptCode`\n\nInline code is only supported by **Lambda**:\n\n- `InlineTypeScriptCode` & `InlineJavaScriptCode`\n- `InlineTsxCode` & `InlineJsxCode`\n\nFor use with **S3 bucket deployments**, classes implementing `s3deploy.ISource` ([reference](https://docs.aws.amazon.com/cdk/api/latest/docs/aws-s3-deployment-readme.html)):\n\n- `TypeScriptSource` & `JavaScriptSource`\n\n> _Code and Source constructs seamlessly plugin to high-level CDK features. They share the same set of parameters, props and build options._\n\nUnderlying classes power the other features. You normally won't have to use them, but they are there if you need them:\n\n- `TypeScriptAsset` & `JavaScriptAsset` implements `s3.Asset` ([reference](https://docs.aws.amazon.com/cdk/api/v2/docs/aws-cdk-lib.aws_s3_assets.Asset.html)) \\\n  creates an asset uploaded to S3 which can be referenced by other constructs\n\n- `EsbuildBundler` implements `core.BundlingOptions` ([reference](https://docs.aws.amazon.com/cdk/api/v2/docs/aws-cdk-lib.BundlingOptions.html)) \\\n  provides an interface for a _esbuild_ bundler wherever needed\n\n## [API Reference](API.md)\n\nAuto-generated reference for classes and structs. This information is also available within the code completion of your IDE.\n\n## Escape hatches\n\nIt's possible that you want to use a implementation of esbuild that's different to the default one. Common reasons are:\n\n- The current version constraints for esbuild are not suitable\n- To use version of esbuild that is installed by any other means than `npm`, including Docker\n- Plugin support is needed for the building\n\nFor these situations, this package offers an escape hatch to bypass regular the implementation and provide a custom build and transform function.\n\n### Custom build function\n\n> 💡 See [Using esbuild with plugins](examples/esbuild-with-plugins) for a complete working example of a custom build function using this escape hatch.\n\nConstructs that result in starting a build, take a `buildFn` as optional prop. While the defined type for this function is `any`, it must implement the same signature as esbuild's `buildSync` function.\n\n```ts\nnew TypeScriptCode(\"fixtures/handlers/ts-handler.ts\", {\n  buildFn: (options: BuildOptions): BuildResult => {\n    try {\n      // custom implementation returning BuildResult\n    } catch (error) {\n      // throw BuildFailure exception here\n    }\n  },\n});\n```\n\nInstead of esbuild, the provided function will be invoked with the calculated build options. The custom build function can amend, change or discard any of these. However integration with CDK relies heavily on the values `outdir`/`outfile` are set to and it's usually required to use them unchanged.\n\nFailures have to cause a `BuildFailure` exception in order to be fully handled.\n\n### Custom transform function\n\nConstructs that result in starting a transformation, take a `transformFn` as optional prop. While the defined type for this function is `any`, it must implement the same signature as esbuild's `transformSync` function.\n\n```ts\nnew InlineTypeScriptCode(\"let x: number = 1\", {\n  transformFn: (options: TransformOptions): TransformResult => {\n    try {\n      // custom implementation returning TransformResult\n    } catch (error) {\n      // throw TransformFailure exception here\n    }\n  },,\n});\n```\n\nInstead of esbuild, the provided function will be invoked with the calculated transform options. The custom transform function can amend, change or discard any of these.\n\nFailures have to cause a `TransformFailure` exception in order to be fully handled.\n\n## Migrating to v3\n\nThe release of cdk-esbuild v3 brings compatibility with AWS CDK v2. Furthermore all deprecated properties and classes have been removed. In particular `InlineCode` classes now take `TransformerProps` as second parameter instead of transform options.\n\n### Upgrading\n\n- This version requires AWS CDK v2. Follow the [official migration guide](https://docs.aws.amazon.com/cdk/latest/guide/work-with-cdk-v2.html) to upgrade.\n- Update the package dependency to v3: `npm install --save @mrgrain/cdk-esbuild@^3.0.0`\n- `esbuild` is installed as an optional dependency. If your setup does not automatically install optional dependencies, make sure to add it as an explicit dependency.\n- Any use of `InlineCode` variations has to be updated. Previously the second parameter was either of type `TransformerProps` or `TransformOptions`. Now it must be `TransformerProps`.\\\n  If the passed value is of type `TransformOptions`, turn it into the correct type like this:\n\n  ```ts\n  const oldOptions: TransformOptions = {...}\n\n  new InlineTypeScriptCode('// inline code', {\n    transformOptions: oldOptions\n  });\n  ```\n\n## Versioning\n\nThis package _mostly_ follows [Semantic Versioning](https://semver.org/), with the exception of upgrades to `esbuild`. These will be released as **minor versions** and often include breaking changes from `esbuild`.\n\n### Npm Tags\n\nSome users prefer to use tags over version ranges. The following stable tags are available for use:\n\n- `cdk-v1`, `cdk-v2` are provided for the latest release compatible with each version of the AWS CDK.\n\n- `latest` is the most recent stable release.\n\nThese tags also exist, but usage is strongly not recommended:\n\n- `unstable`, `next` are used for pre-release of the current and next major version respectively.\n\n- ~~`cdk-1.x.x`~~ tags have been deprecated in favour of `cdk-v1`. Use that one instead.\n\n## Future releases\n\n### Stable esbuild\n\nOnce `esbuild` has reached a stable version 1.0, a new major version will be released for _all_ breaking changes, including updates to minimum (peer) dependencies.\n\n## Library authors\n\nWhen developing a library consumed by other packages, you'll most likely have to set `buildOptions.absWorkingDir`. The easiest way to do this, is to resolve based on the directory name of the file, and traverse the tree upwards to the root of your library package (that's where `package.json` and `tsconfig.json` are):\n\n```ts\n// file: project/src/index.ts\nconst props = {\n  buildOptions: {\n    absWorkingDir: path.resolve(__dirname, \"..\"), // now: /user/project\n  },\n};\n```\n\nThis will dynamically resolve to the correct path, wherever the package is installed.\n"
+    "markdown": "# cdk-esbuild\n\n_CDK constructs for [esbuild](https://github.com/evanw/esbuild), an extremely fast JavaScript bundler_\n\n[Getting started](#getting-started) | [Migrating to v3](#migrating-to-v3) |\n[Documentation](#documentation) | [API Reference](#api-reference) | [Versioning](#versioning)\n\n> This version is compatible with AWS CDK v2. For the previous, AWS CDK v1 compatible release, see [cdk-esbuild@v2](https://github.com/mrgrain/cdk-esbuild/tree/v2).\n\n## Why?\n\n_esbuild_ is an extremely fast bundler and minifier for Typescript and JavaScript.\nThis package makes _esbuild_ available to deploy lambda functions, static websites or to publish build artefacts (assets) for further use.\n\nAWS CDK [supports _esbuild_ with Lambda Functions](https://docs.aws.amazon.com/cdk/api/latest/docs/aws-lambda-nodejs-readme.html). However the implementation cannot be used with any other Constructs and doesn't expose all of _esbuild_'s build interface.\n\nThis package is running _esbuild_ directly in Node.js and bypasses Docker which the AWS CDK implementation uses. The approach is quicker and easier to use for Node.js users, but incompatible with other languages.\n\n**Production readiness**\n\nThis package is stable and ready to be used in production, as many do. However _esbuild_ has not yet released a version 1.0.0 and its API is still in active development. Please read the guide on [esbuild's production readiness](https://esbuild.github.io/faq/#production-readiness).\n\nNotably upgrades of the _esbuild_ minimum version requirement will be introduced in **minor versions** of this package and will inherit breaking changes from _esbuild_.\n\n## Getting started\n\nInstall `cdk-esbuild`:\n\n```\nnpm install @mrgrain/cdk-esbuild@3\n```\n\nIf _peer_ or _optional dependencies_ are not installed automatically (e.g. when using npm v4-6), please use this command to install all of them:\n\n```\nnpm install @mrgrain/cdk-esbuild@3 esbuild\n```\n\n### AWS Lambda: Serverless function\n\n> 💡 See [Lambda Function](examples/lambda) for a complete working example of a how to deploy a lambda function.\n\nUse `TypeScriptCode` as the `code` of a [lambda function](https://docs.aws.amazon.com/cdk/api/v2/docs/aws-cdk-lib.aws_lambda.Function.html#code):\n\n```ts\nimport * as lambda from \"aws-cdk-lib/aws-lambda\";\nimport { TypeScriptCode } from \"@mrgrain/cdk-esbuild\";\n\nconst bundledCode = new TypeScriptCode(\"src/index.ts\");\n\nconst fn = new lambda.Function(stack, \"MyFunction\", {\n  runtime: lambda.Runtime.NODEJS_16_X,\n  handler: \"index.handler\",\n  code: bundledCode,\n});\n```\n\n### AWS S3: Static Website\n\n> 💡 See [Static Website with React](examples/website) for a complete working example of a how to deploy a React app to S3.\n\nUse `TypeScriptSource` as one of the `sources` of a [static website deployment](https://docs.aws.amazon.com/cdk/api/latest/docs/aws-s3-deployment-readme.html#roadmap):\n\n```ts\nimport * as s3 from \"aws-cdk-lib/aws-s3\";\nimport * as s3deploy from \"aws-cdk-lib/aws-s3-deployment\";\nimport { TypeScriptSource } from \"@mrgrain/cdk-esbuild\";\n\nconst websiteBundle = new TypeScriptSource(\"src/index.tsx\");\n\nconst websiteBucket = new s3.Bucket(stack, \"WebsiteBucket\", {\n  autoDeleteObjects: true,\n  publicReadAccess: true,\n  removalPolicy: RemovalPolicy.DESTROY,\n  websiteIndexDocument: \"index.html\",\n});\n\nnew s3deploy.BucketDeployment(stack, \"DeployWebsite\", {\n  destinationBucket: websiteBucket,\n  sources: [websiteBundle],\n});\n```\n\n### Amazon CloudWatch Synthetics: Canary monitoring\n\n> 💡 See [Monitored Website](examples/website) for a complete working example of a deployed and monitored website.\n\nSynthetics runs a canary to produce traffic to an application for monitoring purposes. Use `TypeScriptCode` as the `code` of a Canary test:\n\n> ℹ️ This feature depends on the `@aws-cdk/aws-synthetics-alpha` package which is a developer preview. You may need to update your source code when upgrading to a newer version of this package.\n>\n> ```\n> npm i @aws-cdk/aws-synthetics-alpha\n> ```\n\n```ts\nimport * as synthetics from \"@aws-cdk/aws-synthetics-alpha\";\nimport { TypeScriptCode } from \"@mrgrain/cdk-esbuild\";\n\nconst bundledCode = new TypeScriptCode(\"src/index.ts\", {\n  buildOptions: {\n    outdir: \"nodejs/node_modules\", // This is required by Synthetics\n  },\n});\n\nconst canary = new synthetics.Canary(stack, \"MyCanary\", {\n  runtime: synthetics.Runtime.SYNTHETICS_NODEJS_PUPPETEER_3_2,\n  test: synthetics.Test.custom({\n    code: bundledCode,\n    handler: \"index.handler\",\n  });\n});\n```\n\n## Documentation\n\nThe package exports various different constructs for use with existing CDK features. A major guiding design principal for this package is to _extend, don't replace_. Expect constructs that you can provide as props, not complete replacements.\n\nFor use in **Lambda Functions** and **Synthetic Canaries**, the following classes implement `lambda.Code` ([reference](https://docs.aws.amazon.com/cdk/api/v2/docs/aws-cdk-lib.aws_lambda.Code.html)) and `synthetics.Code` ([reference](https://docs.aws.amazon.com/cdk/api/v2/docs/@aws-cdk_aws-synthetics-alpha.Code.html)):\n\n- `TypeScriptCode` & `JavaScriptCode`\n\nInline code is only supported by **Lambda**:\n\n- `InlineTypeScriptCode` & `InlineJavaScriptCode`\n- `InlineTsxCode` & `InlineJsxCode`\n\nFor use with **S3 bucket deployments**, classes implementing `s3deploy.ISource` ([reference](https://docs.aws.amazon.com/cdk/api/latest/docs/aws-s3-deployment-readme.html)):\n\n- `TypeScriptSource` & `JavaScriptSource`\n\n> _Code and Source constructs seamlessly plug-in to other high-level CDK constructs. They share the same set of parameters, props and build options._\n\nThe following classes power the other features. You normally won't have to use them, but they are there if you need them:\n\n- `TypeScriptAsset` & `JavaScriptAsset` implements `s3.Asset` ([reference](https://docs.aws.amazon.com/cdk/api/v2/docs/aws-cdk-lib.aws_s3_assets.Asset.html)) \\\n  creates an asset uploaded to S3 which can be referenced by other constructs\n\n- `EsbuildBundler` implements `core.BundlingOptions` ([reference](https://docs.aws.amazon.com/cdk/api/v2/docs/aws-cdk-lib.BundlingOptions.html)) \\\n  provides an interface for a _esbuild_ bundler wherever needed\n\n### [API Reference](API.md)\n\nAuto-generated reference for classes and structs. This information is also available as part of your IDE's code completion.\n\n### Escape hatches\n\nIt's possible that you want to use an implementation of esbuild that's different to the default one. Common reasons are:\n\n- The current version constraints for esbuild are not suitable\n- To use a version of esbuild that is installed by any other means than `npm`, including Docker\n- Plugin support is needed for building\n\nFor these situations, this package offers an escape hatch to bypass regular the implementation and provide a custom build and transform function.\n\n#### Custom build function\n\n> 💡 See [Using esbuild with plugins](examples/esbuild-with-plugins) for a complete working example of a custom build function using this escape hatch.\n\nConstructs that result in starting a build, take a `buildFn` as optional prop. While the defined type for this function is `any`, it must implement the same signature as esbuild's `buildSync` function.\n\n```ts\nnew TypeScriptCode(\"fixtures/handlers/ts-handler.ts\", {\n  buildFn: (options: BuildOptions): BuildResult => {\n    try {\n      // custom implementation returning BuildResult\n    } catch (error) {\n      // throw BuildFailure exception here\n    }\n  },\n});\n```\n\nInstead of esbuild, the provided function will be invoked with the calculated build options. The custom build function can amend, change or discard any of these. However integration with CDK relies heavily on the values `outdir`/`outfile` are set to and it's usually required to use them unchanged.\n\nFailures have to cause a `BuildFailure` exception in order to be fully handled.\n\n#### Custom transform function\n\nConstructs that result in starting a transformation, take a `transformFn` as optional prop. While the defined type for this function is `any`, it must implement the same signature as esbuild's `transformSync` function.\n\n```ts\nnew InlineTypeScriptCode(\"let x: number = 1\", {\n  transformFn: (options: TransformOptions): TransformResult => {\n    try {\n      // custom implementation returning TransformResult\n    } catch (error) {\n      // throw TransformFailure exception here\n    }\n  },,\n});\n```\n\nInstead of esbuild, the provided function will be invoked with the calculated transform options. The custom transform function can amend, change or discard any of these.\n\nFailures have to cause a `TransformFailure` exception in order to be fully handled.\n\n### Migrating to v3\n\nThe release of cdk-esbuild v3 brings compatibility with AWS CDK v2. Furthermore all deprecated properties and classes have been removed. In particular `InlineCode` classes now take `TransformerProps` as second parameter instead of transform options.\n\n#### Upgrading\n\n- This version requires AWS CDK v2. Follow the [official migration guide](https://docs.aws.amazon.com/cdk/latest/guide/work-with-cdk-v2.html) to upgrade.\n- Update the package dependency to v3: `npm install --save @mrgrain/cdk-esbuild@^3.0.0`\n- `esbuild` is installed as an optional dependency. If your setup does not automatically install optional dependencies, make sure to add it as an explicit dependency.\n- Any use of `InlineCode` variations has to be updated. Previously the second parameter was either of type `TransformerProps` or `TransformOptions`. Now it must be `TransformerProps`.\\\n  If the passed value is of type `TransformOptions`, turn it into the correct type like this:\n\n  ```ts\n  const oldOptions: TransformOptions = {...}\n\n  new InlineTypeScriptCode('// inline code', {\n    transformOptions: oldOptions\n  });\n  ```\n\n## Versioning\n\nThis package follows [Semantic Versioning](https://semver.org/), with the exception of upgrades to `esbuild`. These will be released as **minor versions** and often include breaking changes from `esbuild`.\n\n### Npm Tags\n\nSome users prefer to use tags over version ranges. The following stable tags are available for use:\n\n- `cdk-v1`, `cdk-v2` are provided for the latest release compatible with each version of the AWS CDK.\n\n- `latest` is the most recent stable release.\n\nThese tags also exist, but usage is strongly not recommended:\n\n- `unstable`, `next` are used for pre-release of the current and next major version respectively.\n\n- ~~`cdk-1.x.x`~~ tags have been deprecated in favour of `cdk-v1`. Use that one instead.\n\n## Roadmap & Contributions\n\n[The project's roadmap is available on GitHub.](https://github.com/mrgrain/cdk-esbuild/projects/1) Please submit any feature requests as issues to the repository.\n\nAll contributions are welcome, no matter if they are for already planned or completely new features.\n\n## Library authors\n\nBuilding a library consumed by other packages that relies on `cdk-esbuild` might require you to set `buildOptions.absWorkingDir`. The easiest way to do this, is to resolve based on the directory name of the calling file, and traverse the tree upwards to the root of your library package (that's where `package.json` and `tsconfig.json` are):\n\n```ts\n// file: project/src/index.ts\nconst props = {\n  buildOptions: {\n    absWorkingDir: path.resolve(__dirname, \"..\"), // now: /user/project\n  },\n};\n```\n\nThis will dynamically resolve to the correct path, wherever the package is installed.\n\nPlease open an issue if you encounter any difficulties.\n"
   },
   "repository": {
     "type": "git",
@@ -3954,7 +3954,7 @@
       "kind": "interface",
       "locationInModule": {
         "filename": "src/bundler.ts",
-        "line": 22
+        "line": 23
       },
       "name": "BundlerProps",
       "properties": [
@@ -3974,7 +3974,7 @@
           "immutable": true,
           "locationInModule": {
             "filename": "src/bundler.ts",
-            "line": 63
+            "line": 79
           },
           "name": "buildFn",
           "optional": true,
@@ -3985,7 +3985,7 @@
         {
           "abstract": true,
           "docs": {
-            "remarks": "- `buildOptions.outdir: string`\nThe actual path for the output directory is defined by CDK. However setting this option allows to write files into a subdirectory. \\\nFor example `{ outdir: 'js' }` will create an asset with a single directory called `js`, which contains all built files. This approach can be useful for static website deployments, where JavaScript code should be placed into a subdirectory. \\\n*Cannot be used together with `outfile`*.\n- `buildOptions.outfile: string`\nRelative path to a file inside the CDK asset output directory.\nFor example `{ outfile: 'js/index.js' }` will create an asset with a single directory called `js`, which contains a single file `index.js`. This can be useful to rename the entry point. \\\n*Cannot be used with multiple entryPoints or together with `outdir`.*\n- `buildOptions.absWorkingDir: string`\nAbsolute path to the [esbuild working directory](https://esbuild.github.io/api/#working-directory) and defaults to the [current working directory](https://en.wikipedia.org/wiki/Working_directory). \\\nIf paths cannot be found, a good starting point is to look at the concatenation of `absWorkingDir + entryPoint`. It must always be a valid absolute path pointing to the entry point. When needed, the probably easiest way to set absWorkingDir is to use a combination of `resolve` and `__dirname` (see \"Library authors\" section in the documentation).",
+            "remarks": "* `buildOptions.outdir: string`\nThe actual path for the output directory is defined by CDK. However setting this option allows to write files into a subdirectory. \\\nFor example `{ outdir: 'js' }` will create an asset with a single directory called `js`, which contains all built files. This approach can be useful for static website deployments, where JavaScript code should be placed into a subdirectory. \\\n*Cannot be used together with `outfile`*.\n* `buildOptions.outfile: string`\nRelative path to a file inside the CDK asset output directory.\nFor example `{ outfile: 'js/index.js' }` will create an asset with a single directory called `js`, which contains a single file `index.js`. This can be useful to rename the entry point. \\\n*Cannot be used with multiple entryPoints or together with `outdir`.*\n* `buildOptions.absWorkingDir: string`\nAbsolute path to the [esbuild working directory](https://esbuild.github.io/api/#working-directory) and defaults to the [current working directory](https://en.wikipedia.org/wiki/Working_directory). \\\nIf paths cannot be found, a good starting point is to look at the concatenation of `absWorkingDir + entryPoint`. It must always be a valid absolute path pointing to the entry point. When needed, the probably easiest way to set absWorkingDir is to use a combination of `resolve` and `__dirname` (see \"Library authors\" section in the documentation).",
             "see": "https://esbuild.github.io/api/#build-api",
             "stability": "stable",
             "summary": "Build options passed on to esbuild. Please refer to the esbuild Build API docs for details."
@@ -3993,7 +3993,7 @@
           "immutable": true,
           "locationInModule": {
             "filename": "src/bundler.ts",
-            "line": 41
+            "line": 42
           },
           "name": "buildOptions",
           "optional": true,
@@ -4004,19 +4004,55 @@
         {
           "abstract": true,
           "docs": {
-            "remarks": "Files copied like this will be overwritten by esbuild if they share the same name as any of the outputs.",
+            "remarks": "* When provided with a `string` or `array`, all files are copied to the root of asset staging directory.\n* When given a `map`, the key indicates the destination relative to the asset staging directory and the value is a list of all sources to be copied.\n\nTherefore the following values for `copyDir` are all equivalent:\n```ts\n{ copyDir: \"path/to/source\" }\n{ copyDir: [\"path/to/source\"] }\n{ copyDir: { \".\": \"path/to/source\" } }\n{ copyDir: { \".\": [\"path/to/source\"] } }\n```\nThe destination cannot be outside of the asset staging directory.\nIf you are receiving the error \"Cannot copy files to outside of the asset staging directory.\"\nyou are likely using `..` or an absolute path as key on the `copyDir` map.\nInstead use only relative paths and avoid `..`.",
             "stability": "stable",
-            "summary": "Copy additional files to the output directory, before the build runs."
+            "summary": "Copy additional files to the code [asset staging directory](https://docs.aws.amazon.com/cdk/api/v2/docs/aws-cdk-lib.AssetStaging.html#absolutestagedpath), before the build runs. Files copied like this will be overwritten by esbuild if they share the same name as any of the outputs."
           },
           "immutable": true,
           "locationInModule": {
             "filename": "src/bundler.ts",
-            "line": 49
+            "line": 65
           },
           "name": "copyDir",
           "optional": true,
           "type": {
-            "primitive": "string"
+            "union": {
+              "types": [
+                {
+                  "primitive": "string"
+                },
+                {
+                  "collection": {
+                    "elementtype": {
+                      "primitive": "string"
+                    },
+                    "kind": "array"
+                  }
+                },
+                {
+                  "collection": {
+                    "elementtype": {
+                      "union": {
+                        "types": [
+                          {
+                            "primitive": "string"
+                          },
+                          {
+                            "collection": {
+                              "elementtype": {
+                                "primitive": "string"
+                              },
+                              "kind": "array"
+                            }
+                          }
+                        ]
+                      }
+                    },
+                    "kind": "map"
+                  }
+                }
+              ]
+            }
           }
         }
       ],
@@ -4069,7 +4105,7 @@
         },
         "locationInModule": {
           "filename": "src/bundler.ts",
-          "line": 90
+          "line": 106
         },
         "parameters": [
           {
@@ -4120,7 +4156,7 @@
       "kind": "class",
       "locationInModule": {
         "filename": "src/bundler.ts",
-        "line": 72
+        "line": 88
       },
       "name": "EsbuildBundler",
       "properties": [
@@ -4133,7 +4169,7 @@
           "immutable": true,
           "locationInModule": {
             "filename": "src/bundler.ts",
-            "line": 97
+            "line": 113
           },
           "name": "entryPoints",
           "type": {
@@ -4170,7 +4206,7 @@
           "immutable": true,
           "locationInModule": {
             "filename": "src/bundler.ts",
-            "line": 85
+            "line": 101
           },
           "name": "image",
           "type": {
@@ -4185,7 +4221,7 @@
           "immutable": true,
           "locationInModule": {
             "filename": "src/bundler.ts",
-            "line": 78
+            "line": 94
           },
           "name": "local",
           "type": {
@@ -4200,7 +4236,7 @@
           "immutable": true,
           "locationInModule": {
             "filename": "src/bundler.ts",
-            "line": 104
+            "line": 120
           },
           "name": "props",
           "type": {
@@ -6056,6 +6092,6 @@
       "symbolId": "src/source:TypeScriptSourceProps"
     }
   },
-  "version": "3.3.0",
-  "fingerprint": "Q2F6iETZiRfNYQpToAP4z9DFp9FZ44lOZazVBzIGdEU="
+  "version": "3.4.0",
+  "fingerprint": "KLIX/Vq9D/NBEka2gtCgAIO/3cBKSHQNOCxdNGupRg4="
 }

package/.projenrc.ts

@@ -85,14 +85,9 @@ const project = new awscdk.AwsCdkConstructLibrary({
 
   // Dependencies
   cdkVersion: '2.0.0',
-  peerDeps: [
-    'aws-cdk-lib@^2.0.0',
-  ],
   devDeps: [
-    '@aws-cdk/aws-synthetics-alpha',
+    '@aws-cdk/aws-synthetics-alpha@2.0.0-alpha.11',
     '@types/eslint',
-    'aws-cdk-lib@2.0.0',
-    'constructs@10.0.5',
     'esbuild@^0.14.0',
     'jest-mock',
     'ts-morph',
@@ -191,6 +186,7 @@ new TypeScriptSourceFile(project, 'src/esbuild-types.ts', {
     esbuildTypes.getInterface('CommonOptions')?.getProperty('mangleProps')?.setType('any');
     esbuildTypes.getInterface('CommonOptions')?.getProperty('reserveProps')?.setType('any');
     esbuildTypes.getInterface('TransformOptions')?.getProperty('tsconfigRaw')?.setType('string');
+    esbuildTypes.getInterface('InitializeOptions')?.getProperty('wasmModule')?.setType('any');
   },
 });
 

package/API.md

@@ -39,15 +39,15 @@ public readonly buildOptions: BuildOptions;
 
 Build options passed on to esbuild. Please refer to the esbuild Build API docs for details.
 
-`buildOptions.outdir: string`
+* `buildOptions.outdir: string`
 The actual path for the output directory is defined by CDK. However setting this option allows to write files into a subdirectory. \
 For example `{ outdir: 'js' }` will create an asset with a single directory called `js`, which contains all built files. This approach can be useful for static website deployments, where JavaScript code should be placed into a subdirectory. \
 *Cannot be used together with `outfile`*.
-- `buildOptions.outfile: string`
+* `buildOptions.outfile: string`
 Relative path to a file inside the CDK asset output directory.
 For example `{ outfile: 'js/index.js' }` will create an asset with a single directory called `js`, which contains a single file `index.js`. This can be useful to rename the entry point. \
 *Cannot be used with multiple entryPoints or together with `outdir`.*
-- `buildOptions.absWorkingDir: string`
+* `buildOptions.absWorkingDir: string`
 Absolute path to the [esbuild working directory](https://esbuild.github.io/api/#working-directory) and defaults to the [current working directory](https://en.wikipedia.org/wiki/Working_directory). \
 If paths cannot be found, a good starting point is to look at the concatenation of `absWorkingDir + entryPoint`. It must always be a valid absolute path pointing to the entry point. When needed, the probably easiest way to set absWorkingDir is to use a combination of `resolve` and `__dirname` (see "Library authors" section in the documentation).
 
@@ -58,14 +58,27 @@ If paths cannot be found, a good starting point is to look at the concatenation
 ##### `copyDir`<sup>Optional</sup> <a name="@mrgrain/cdk-esbuild.AssetProps.property.copyDir"></a>
 
 ```typescript
-public readonly copyDir: string;
+public readonly copyDir: string | string[] | {[ key: string ]: string | string[]};
 ```
 
-- *Type:* `string`
+- *Type:* `string` | `string`[] | {[ key: string ]: `string` | `string`[]}
+
+Copy additional files to the code [asset staging directory](https://docs.aws.amazon.com/cdk/api/v2/docs/aws-cdk-lib.AssetStaging.html#absolutestagedpath), before the build runs. Files copied like this will be overwritten by esbuild if they share the same name as any of the outputs.
 
-Copy additional files to the output directory, before the build runs.
+* When provided with a `string` or `array`, all files are copied to the root of asset staging directory.
+* When given a `map`, the key indicates the destination relative to the asset staging directory and the value is a list of all sources to be copied.
 
-Files copied like this will be overwritten by esbuild if they share the same name as any of the outputs.
+Therefore the following values for `copyDir` are all equivalent:
+```ts
+{ copyDir: "path/to/source" }
+{ copyDir: ["path/to/source"] }
+{ copyDir: { ".": "path/to/source" } }
+{ copyDir: { ".": ["path/to/source"] } }
+```
+The destination cannot be outside of the asset staging directory.
+If you are receiving the error "Cannot copy files to outside of the asset staging directory."
+you are likely using `..` or an absolute path as key on the `copyDir` map.
+Instead use only relative paths and avoid `..`.
 
 ---
 
@@ -805,15 +818,15 @@ public readonly buildOptions: BuildOptions;
 
 Build options passed on to esbuild. Please refer to the esbuild Build API docs for details.
 
-`buildOptions.outdir: string`
+* `buildOptions.outdir: string`
 The actual path for the output directory is defined by CDK. However setting this option allows to write files into a subdirectory. \
 For example `{ outdir: 'js' }` will create an asset with a single directory called `js`, which contains all built files. This approach can be useful for static website deployments, where JavaScript code should be placed into a subdirectory. \
 *Cannot be used together with `outfile`*.
-- `buildOptions.outfile: string`
+* `buildOptions.outfile: string`
 Relative path to a file inside the CDK asset output directory.
 For example `{ outfile: 'js/index.js' }` will create an asset with a single directory called `js`, which contains a single file `index.js`. This can be useful to rename the entry point. \
 *Cannot be used with multiple entryPoints or together with `outdir`.*
-- `buildOptions.absWorkingDir: string`
+* `buildOptions.absWorkingDir: string`
 Absolute path to the [esbuild working directory](https://esbuild.github.io/api/#working-directory) and defaults to the [current working directory](https://en.wikipedia.org/wiki/Working_directory). \
 If paths cannot be found, a good starting point is to look at the concatenation of `absWorkingDir + entryPoint`. It must always be a valid absolute path pointing to the entry point. When needed, the probably easiest way to set absWorkingDir is to use a combination of `resolve` and `__dirname` (see "Library authors" section in the documentation).
 
@@ -824,14 +837,27 @@ If paths cannot be found, a good starting point is to look at the concatenation
 ##### `copyDir`<sup>Optional</sup> <a name="@mrgrain/cdk-esbuild.BundlerProps.property.copyDir"></a>
 
 ```typescript
-public readonly copyDir: string;
+public readonly copyDir: string | string[] | {[ key: string ]: string | string[]};
 ```
 
-- *Type:* `string`
+- *Type:* `string` | `string`[] | {[ key: string ]: `string` | `string`[]}
 
-Copy additional files to the output directory, before the build runs.
+Copy additional files to the code [asset staging directory](https://docs.aws.amazon.com/cdk/api/v2/docs/aws-cdk-lib.AssetStaging.html#absolutestagedpath), before the build runs. Files copied like this will be overwritten by esbuild if they share the same name as any of the outputs.
 
-Files copied like this will be overwritten by esbuild if they share the same name as any of the outputs.
+* When provided with a `string` or `array`, all files are copied to the root of asset staging directory.
+* When given a `map`, the key indicates the destination relative to the asset staging directory and the value is a list of all sources to be copied.
+
+Therefore the following values for `copyDir` are all equivalent:
+```ts
+{ copyDir: "path/to/source" }
+{ copyDir: ["path/to/source"] }
+{ copyDir: { ".": "path/to/source" } }
+{ copyDir: { ".": ["path/to/source"] } }
+```
+The destination cannot be outside of the asset staging directory.
+If you are receiving the error "Cannot copy files to outside of the asset staging directory."
+you are likely using `..` or an absolute path as key on the `copyDir` map.
+Instead use only relative paths and avoid `..`.
 
 ---
 
@@ -893,15 +919,15 @@ public readonly buildOptions: BuildOptions;
 
 Build options passed on to esbuild. Please refer to the esbuild Build API docs for details.
 
-`buildOptions.outdir: string`
+* `buildOptions.outdir: string`
 The actual path for the output directory is defined by CDK. However setting this option allows to write files into a subdirectory. \
 For example `{ outdir: 'js' }` will create an asset with a single directory called `js`, which contains all built files. This approach can be useful for static website deployments, where JavaScript code should be placed into a subdirectory. \
 *Cannot be used together with `outfile`*.
-- `buildOptions.outfile: string`
+* `buildOptions.outfile: string`
 Relative path to a file inside the CDK asset output directory.
 For example `{ outfile: 'js/index.js' }` will create an asset with a single directory called `js`, which contains a single file `index.js`. This can be useful to rename the entry point. \
 *Cannot be used with multiple entryPoints or together with `outdir`.*
-- `buildOptions.absWorkingDir: string`
+* `buildOptions.absWorkingDir: string`
 Absolute path to the [esbuild working directory](https://esbuild.github.io/api/#working-directory) and defaults to the [current working directory](https://en.wikipedia.org/wiki/Working_directory). \
 If paths cannot be found, a good starting point is to look at the concatenation of `absWorkingDir + entryPoint`. It must always be a valid absolute path pointing to the entry point. When needed, the probably easiest way to set absWorkingDir is to use a combination of `resolve` and `__dirname` (see "Library authors" section in the documentation).
 
@@ -912,14 +938,27 @@ If paths cannot be found, a good starting point is to look at the concatenation
 ##### `copyDir`<sup>Optional</sup> <a name="@mrgrain/cdk-esbuild.JavaScriptCodeProps.property.copyDir"></a>
 
 ```typescript
-public readonly copyDir: string;
+public readonly copyDir: string | string[] | {[ key: string ]: string | string[]};
 ```
 
-- *Type:* `string`
+- *Type:* `string` | `string`[] | {[ key: string ]: `string` | `string`[]}
 
-Copy additional files to the output directory, before the build runs.
+Copy additional files to the code [asset staging directory](https://docs.aws.amazon.com/cdk/api/v2/docs/aws-cdk-lib.AssetStaging.html#absolutestagedpath), before the build runs. Files copied like this will be overwritten by esbuild if they share the same name as any of the outputs.
 
-Files copied like this will be overwritten by esbuild if they share the same name as any of the outputs.
+* When provided with a `string` or `array`, all files are copied to the root of asset staging directory.
+* When given a `map`, the key indicates the destination relative to the asset staging directory and the value is a list of all sources to be copied.
+
+Therefore the following values for `copyDir` are all equivalent:
+```ts
+{ copyDir: "path/to/source" }
+{ copyDir: ["path/to/source"] }
+{ copyDir: { ".": "path/to/source" } }
+{ copyDir: { ".": ["path/to/source"] } }
+```
+The destination cannot be outside of the asset staging directory.
+If you are receiving the error "Cannot copy files to outside of the asset staging directory."
+you are likely using `..` or an absolute path as key on the `copyDir` map.
+Instead use only relative paths and avoid `..`.
 
 ---
 
@@ -975,15 +1014,15 @@ public readonly buildOptions: BuildOptions;
 
 Build options passed on to esbuild. Please refer to the esbuild Build API docs for details.
 
-`buildOptions.outdir: string`
+* `buildOptions.outdir: string`
 The actual path for the output directory is defined by CDK. However setting this option allows to write files into a subdirectory. \
 For example `{ outdir: 'js' }` will create an asset with a single directory called `js`, which contains all built files. This approach can be useful for static website deployments, where JavaScript code should be placed into a subdirectory. \
 *Cannot be used together with `outfile`*.
-- `buildOptions.outfile: string`
+* `buildOptions.outfile: string`
 Relative path to a file inside the CDK asset output directory.
 For example `{ outfile: 'js/index.js' }` will create an asset with a single directory called `js`, which contains a single file `index.js`. This can be useful to rename the entry point. \
 *Cannot be used with multiple entryPoints or together with `outdir`.*
-- `buildOptions.absWorkingDir: string`
+* `buildOptions.absWorkingDir: string`
 Absolute path to the [esbuild working directory](https://esbuild.github.io/api/#working-directory) and defaults to the [current working directory](https://en.wikipedia.org/wiki/Working_directory). \
 If paths cannot be found, a good starting point is to look at the concatenation of `absWorkingDir + entryPoint`. It must always be a valid absolute path pointing to the entry point. When needed, the probably easiest way to set absWorkingDir is to use a combination of `resolve` and `__dirname` (see "Library authors" section in the documentation).
 
@@ -994,14 +1033,27 @@ If paths cannot be found, a good starting point is to look at the concatenation
 ##### `copyDir`<sup>Optional</sup> <a name="@mrgrain/cdk-esbuild.JavaScriptSourceProps.property.copyDir"></a>
 
 ```typescript
-public readonly copyDir: string;
+public readonly copyDir: string | string[] | {[ key: string ]: string | string[]};
 ```
 
-- *Type:* `string`
+- *Type:* `string` | `string`[] | {[ key: string ]: `string` | `string`[]}
+
+Copy additional files to the code [asset staging directory](https://docs.aws.amazon.com/cdk/api/v2/docs/aws-cdk-lib.AssetStaging.html#absolutestagedpath), before the build runs. Files copied like this will be overwritten by esbuild if they share the same name as any of the outputs.
 
-Copy additional files to the output directory, before the build runs.
+* When provided with a `string` or `array`, all files are copied to the root of asset staging directory.
+* When given a `map`, the key indicates the destination relative to the asset staging directory and the value is a list of all sources to be copied.
 
-Files copied like this will be overwritten by esbuild if they share the same name as any of the outputs.
+Therefore the following values for `copyDir` are all equivalent:
+```ts
+{ copyDir: "path/to/source" }
+{ copyDir: ["path/to/source"] }
+{ copyDir: { ".": "path/to/source" } }
+{ copyDir: { ".": ["path/to/source"] } }
+```
+The destination cannot be outside of the asset staging directory.
+If you are receiving the error "Cannot copy files to outside of the asset staging directory."
+you are likely using `..` or an absolute path as key on the `copyDir` map.
+Instead use only relative paths and avoid `..`.
 
 ---
 
@@ -1495,15 +1547,15 @@ public readonly buildOptions: BuildOptions;
 
 Build options passed on to esbuild. Please refer to the esbuild Build API docs for details.
 
-`buildOptions.outdir: string`
+* `buildOptions.outdir: string`
 The actual path for the output directory is defined by CDK. However setting this option allows to write files into a subdirectory. \
 For example `{ outdir: 'js' }` will create an asset with a single directory called `js`, which contains all built files. This approach can be useful for static website deployments, where JavaScript code should be placed into a subdirectory. \
 *Cannot be used together with `outfile`*.
-- `buildOptions.outfile: string`
+* `buildOptions.outfile: string`
 Relative path to a file inside the CDK asset output directory.
 For example `{ outfile: 'js/index.js' }` will create an asset with a single directory called `js`, which contains a single file `index.js`. This can be useful to rename the entry point. \
 *Cannot be used with multiple entryPoints or together with `outdir`.*
-- `buildOptions.absWorkingDir: string`
+* `buildOptions.absWorkingDir: string`
 Absolute path to the [esbuild working directory](https://esbuild.github.io/api/#working-directory) and defaults to the [current working directory](https://en.wikipedia.org/wiki/Working_directory). \
 If paths cannot be found, a good starting point is to look at the concatenation of `absWorkingDir + entryPoint`. It must always be a valid absolute path pointing to the entry point. When needed, the probably easiest way to set absWorkingDir is to use a combination of `resolve` and `__dirname` (see "Library authors" section in the documentation).
 
@@ -1514,14 +1566,27 @@ If paths cannot be found, a good starting point is to look at the concatenation
 ##### `copyDir`<sup>Optional</sup> <a name="@mrgrain/cdk-esbuild.TypeScriptCodeProps.property.copyDir"></a>
 
 ```typescript
-public readonly copyDir: string;
+public readonly copyDir: string | string[] | {[ key: string ]: string | string[]};
 ```
 
-- *Type:* `string`
+- *Type:* `string` | `string`[] | {[ key: string ]: `string` | `string`[]}
 
-Copy additional files to the output directory, before the build runs.
+Copy additional files to the code [asset staging directory](https://docs.aws.amazon.com/cdk/api/v2/docs/aws-cdk-lib.AssetStaging.html#absolutestagedpath), before the build runs. Files copied like this will be overwritten by esbuild if they share the same name as any of the outputs.
 
-Files copied like this will be overwritten by esbuild if they share the same name as any of the outputs.
+* When provided with a `string` or `array`, all files are copied to the root of asset staging directory.
+* When given a `map`, the key indicates the destination relative to the asset staging directory and the value is a list of all sources to be copied.
+
+Therefore the following values for `copyDir` are all equivalent:
+```ts
+{ copyDir: "path/to/source" }
+{ copyDir: ["path/to/source"] }
+{ copyDir: { ".": "path/to/source" } }
+{ copyDir: { ".": ["path/to/source"] } }
+```
+The destination cannot be outside of the asset staging directory.
+If you are receiving the error "Cannot copy files to outside of the asset staging directory."
+you are likely using `..` or an absolute path as key on the `copyDir` map.
+Instead use only relative paths and avoid `..`.
 
 ---
 
@@ -1577,15 +1642,15 @@ public readonly buildOptions: BuildOptions;
 
 Build options passed on to esbuild. Please refer to the esbuild Build API docs for details.
 
-`buildOptions.outdir: string`
+* `buildOptions.outdir: string`
 The actual path for the output directory is defined by CDK. However setting this option allows to write files into a subdirectory. \
 For example `{ outdir: 'js' }` will create an asset with a single directory called `js`, which contains all built files. This approach can be useful for static website deployments, where JavaScript code should be placed into a subdirectory. \
 *Cannot be used together with `outfile`*.
-- `buildOptions.outfile: string`
+* `buildOptions.outfile: string`
 Relative path to a file inside the CDK asset output directory.
 For example `{ outfile: 'js/index.js' }` will create an asset with a single directory called `js`, which contains a single file `index.js`. This can be useful to rename the entry point. \
 *Cannot be used with multiple entryPoints or together with `outdir`.*
-- `buildOptions.absWorkingDir: string`
+* `buildOptions.absWorkingDir: string`
 Absolute path to the [esbuild working directory](https://esbuild.github.io/api/#working-directory) and defaults to the [current working directory](https://en.wikipedia.org/wiki/Working_directory). \
 If paths cannot be found, a good starting point is to look at the concatenation of `absWorkingDir + entryPoint`. It must always be a valid absolute path pointing to the entry point. When needed, the probably easiest way to set absWorkingDir is to use a combination of `resolve` and `__dirname` (see "Library authors" section in the documentation).
 
@@ -1596,14 +1661,27 @@ If paths cannot be found, a good starting point is to look at the concatenation
 ##### `copyDir`<sup>Optional</sup> <a name="@mrgrain/cdk-esbuild.TypeScriptSourceProps.property.copyDir"></a>
 
 ```typescript
-public readonly copyDir: string;
+public readonly copyDir: string | string[] | {[ key: string ]: string | string[]};
 ```
 
-- *Type:* `string`
+- *Type:* `string` | `string`[] | {[ key: string ]: `string` | `string`[]}
 
-Copy additional files to the output directory, before the build runs.
+Copy additional files to the code [asset staging directory](https://docs.aws.amazon.com/cdk/api/v2/docs/aws-cdk-lib.AssetStaging.html#absolutestagedpath), before the build runs. Files copied like this will be overwritten by esbuild if they share the same name as any of the outputs.
 
-Files copied like this will be overwritten by esbuild if they share the same name as any of the outputs.
+* When provided with a `string` or `array`, all files are copied to the root of asset staging directory.
+* When given a `map`, the key indicates the destination relative to the asset staging directory and the value is a list of all sources to be copied.
+
+Therefore the following values for `copyDir` are all equivalent:
+```ts
+{ copyDir: "path/to/source" }
+{ copyDir: ["path/to/source"] }
+{ copyDir: { ".": "path/to/source" } }
+{ copyDir: { ".": ["path/to/source"] } }
+```
+The destination cannot be outside of the asset staging directory.
+If you are receiving the error "Cannot copy files to outside of the asset staging directory."
+you are likely using `..` or an absolute path as key on the `copyDir` map.
+Instead use only relative paths and avoid `..`.
 
 ---
 

package/CHANGELOG.md

@@ -1,7 +1,7 @@
 
-## [3.3.0](https://github.com/mrgrain/cdk-esbuild/compare/v3.2.0...v3.3.0) (2022-03-06)
+## [3.4.0](https://github.com/mrgrain/cdk-esbuild/compare/v3.3.0...v3.4.0) (2022-05-26)
 
 
 ### Features
 
-* support mangleQuoted option ([f4d8859](https://github.com/mrgrain/cdk-esbuild/commit/f4d88597c2f93064f7e3f6d4f591630eacfe7b80))
+* copyDir supports more complex scenarios ([08c59fb](https://github.com/mrgrain/cdk-esbuild/commit/08c59fba7bf1ee68ca103520b3e0b7ea5359a925))