Interface BundlingOptions
- All Superinterfaces:
software.amazon.jsii.JsiiSerializable
- All Known Implementing Classes:
BundlingOptions.Jsii$Proxy
Example:
NodejsFunction.Builder.create(this, "my-handler") .bundling(BundlingOptions.builder() .dockerImage(DockerImage.fromBuild("/path/to/Dockerfile")) .build()) .build();
-
Nested Class Summary
Modifier and TypeInterfaceDescriptionstatic final class
A builder forBundlingOptions
static final class
An implementation forBundlingOptions
-
Method Summary
Modifier and TypeMethodDescriptionstatic BundlingOptions.Builder
builder()
default String
Specify a custom hash for this asset.default String
Use this to insert an arbitrary string at the beginning of generated JavaScript files.Build arguments to pass when building the bundling image.default Charset
The charset to use for esbuild's output.default ICommandHooks
Command hooks.Replace global identifiers with constant expressions.default DockerImage
A custom bundling Docker image.Environment variables defined when bundling runs.Build arguments to pass into esbuild.default String
The version of esbuild to use when running in a Docker container.A list of modules that should be considered as externals (already available in the runtime).default String
Use this to insert an arbitrary string at the end of generated JavaScript files.default Boolean
Force bundling in a Docker container even if local bundling is possible.default OutputFormat
Output format for the generated JavaScript files.This option allows you to automatically replace a global variable with an import from another file.default Boolean
Whether to preserve the originalname
values even in minified code.Use loaders to change how a given input file is interpreted.default LogLevel
Log level for esbuild.How to determine the entry point for modules.default Boolean
This option tells esbuild to write out a JSON file relative to output directory with metadata about the build.default Boolean
Whether to minify files when bundling.A list of modules that should be installed instead of bundled.default Boolean
Run compilation using tsc before running file through bundling step.default Boolean
Whether to include source maps when bundling.default SourceMapMode
Source map mode to be used when bundling.default Boolean
Whether to include original source code in source maps when bundling.default String
Target environment for the generated JavaScript code.default String
Normally the esbuild automatically discoverstsconfig.json
files and reads their contents during a build.Methods inherited from interface software.amazon.jsii.JsiiSerializable
$jsii$toJson
-
Method Details
-
getAssetHash
Specify a custom hash for this asset.For consistency, this custom hash will be SHA256 hashed and encoded as hex. The resulting hash will be the asset hash.
NOTE: the hash is used in order to identify a specific revision of the asset, and used for optimizing and caching deployment activities related to this asset such as packaging, uploading to Amazon S3, etc. If you chose to customize the hash, you will need to make sure it is updated every time the asset changes, or otherwise it is possible that some deployments will not be invalidated.
Default: - asset hash is calculated based on the bundled output
-
getBanner
Use this to insert an arbitrary string at the beginning of generated JavaScript files.This is similar to footer which inserts at the end instead of the beginning.
This is commonly used to insert comments:
Default: - no comments are passed
-
getBuildArgs
Build arguments to pass when building the bundling image.Default: - no build arguments are passed
-
getCharset
The charset to use for esbuild's output.By default esbuild's output is ASCII-only. Any non-ASCII characters are escaped using backslash escape sequences. Using escape sequences makes the generated output slightly bigger, and also makes it harder to read. If you would like for esbuild to print the original characters without using escape sequences, use
Charset.UTF8
.Default: Charset.ASCII
- See Also:
-
getCommandHooks
Command hooks.Default: - do not run additional commands
-
getDefine
Replace global identifiers with constant expressions.For example,
{ 'process.env.DEBUG': 'true' }
.Another example,
{ 'process.env.API_KEY': JSON.stringify('xxx-xxxx-xxx') }
.Default: - no replacements are made
-
getDockerImage
A custom bundling Docker image.This image should have esbuild installed globally. If you plan to use
nodeModules
it should also havenpm
oryarn
depending on the lock file you're using.See https://github.com/aws/aws-cdk/blob/master/packages/%40aws-cdk/aws-lambda-nodejs/lib/Dockerfile for the default image provided by @aws-cdk/aws-lambda-nodejs.
Default: - use the Docker image provided by
-
getEnvironment
Environment variables defined when bundling runs.Default: - no environment variables are defined.
-
getEsbuildArgs
Build arguments to pass into esbuild.For example, to add the --log-limit flag:
new NodejsFunction(scope, id, { ... bundling: { esbuildArgs: { "--log-limit": "0", } } });
Default: - no additional esbuild arguments are passed
-
getEsbuildVersion
The version of esbuild to use when running in a Docker container.Default: - latest v0
-
getExternalModules
A list of modules that should be considered as externals (already available in the runtime).Default: ['aws-sdk']
-
getForceDockerBundling
Force bundling in a Docker container even if local bundling is possible.This is useful if your function relies on node modules that should be installed (
nodeModules
) in a Lambda compatible environment.Default: false
-
getFormat
Output format for the generated JavaScript files.Default: OutputFormat.CJS
-
getInject
This option allows you to automatically replace a global variable with an import from another file.Default: - no code is injected
- See Also:
-
getKeepNames
Whether to preserve the originalname
values even in minified code.In JavaScript the
name
property on functions and classes defaults to a nearby identifier in the source code.However, minification renames symbols to reduce code size and bundling sometimes need to rename symbols to avoid collisions. That changes value of the
name
property for many of these cases. This is usually fine because thename
property is normally only used for debugging. However, some frameworks rely on thename
property for registration and binding purposes. If this is the case, you can enable this option to preserve the originalname
values even in minified code.Default: false
-
getLoader
Use loaders to change how a given input file is interpreted.Configuring a loader for a given file type lets you load that file type with an
import
statement or arequire
call.Default: - use esbuild default loaders
- See Also:
-
getLogLevel
Log level for esbuild.This is also propagated to the package manager and applies to its specific install command.
Default: LogLevel.WARNING
-
getMainFields
How to determine the entry point for modules.Try ['module', 'main'] to default to ES module versions.
Default: ['main', 'module']
-
getMetafile
This option tells esbuild to write out a JSON file relative to output directory with metadata about the build.The metadata in this JSON file follows this schema (specified using TypeScript syntax):
{ outputs: { [path: string]: { bytes: number inputs: { [path: string]: { bytesInOutput: number } } imports: { path: string }[] exports: string[] } } }
This data can then be analyzed by other tools. For example, bundle buddy can consume esbuild's metadata format and generates a treemap visualization of the modules in your bundle and how much space each one takes up.
Default: false
- See Also:
-
getMinify
Whether to minify files when bundling.Default: false
-
getNodeModules
A list of modules that should be installed instead of bundled.Modules are installed in a Lambda compatible environment only when bundling runs in Docker.
Default: - all modules are bundled
-
getPreCompilation
Run compilation using tsc before running file through bundling step.This usually is not required unless you are using new experimental features that are only supported by typescript's
tsc
compiler. One example of such feature isemitDecoratorMetadata
.Default: false
-
getSourceMap
Whether to include source maps when bundling.Default: false
-
getSourceMapMode
Source map mode to be used when bundling.Default: SourceMapMode.DEFAULT
- See Also:
-
getSourcesContent
Whether to include original source code in source maps when bundling.Default: true
- See Also:
-
getTarget
Target environment for the generated JavaScript code.Default: - the node version of the runtime
- See Also:
-
getTsconfig
Normally the esbuild automatically discoverstsconfig.json
files and reads their contents during a build.However, you can also configure a custom
tsconfig.json
file to use instead.This is similar to entry path, you need to provide path to your custom
tsconfig.json
.This can be useful if you need to do multiple builds of the same code with different settings.
For example,
{ 'tsconfig': 'path/custom.tsconfig.json' }
.Default: - automatically discovered by `esbuild`
-
builder
- Returns:
- a
BundlingOptions.Builder
ofBundlingOptions
-