awesome-emulator-cli 0.6.2 → 0.6.4

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.
package/README.md CHANGED
@@ -4,7 +4,7 @@
4
4
  <img src="./assets/social-preview-v2.png" alt="Awesome Emulator CLI — Local emulator testing for AWS SDKs" width="100%">
5
5
  </p>
6
6
 
7
- A Node.js CLI that manages AWS Emulator in Docker and passes its connection settings to your test command. Your tests can use any AWS SDK language; they do not need to run in Node.js.
7
+ A Node.js CLI that manages AWS Emulator in Docker and passes its connection settings to your test command. Your tests can use any AWS SDK language; they do not need to run in Node.js. The CLI itself has no production npm dependencies.
8
8
 
9
9
  This is an independent project and is not affiliated with or endorsed by Amazon Web Services.
10
10
 
@@ -49,6 +49,10 @@ npm exec --yes --package=awesome-emulator-cli -- awesome-emulator run -- python
49
49
 
50
50
  The same pattern works with AWS CLI, Go, Java, Rust, and .NET projects. Use `--sdk` when a command needs SDK-specific TLS settings; see the [SDK configuration guide](./docs/sdk-configuration.md).
51
51
 
52
+ ## Examples
53
+
54
+ See [awesome-emulator-cli-samples](https://github.com/c19yamamoto/awesome-emulator-cli-samples) for end-to-end S3 examples and integration tests using AWS SDKs in JavaScript, Python, Go, Java, Rust, and .NET.
55
+
52
56
  ## Reuse the emulator across commands
53
57
 
54
58
  Use a named session when setup and tests run as separate commands or CI steps. Set `AWS_EMULATOR_STATE_DIR` to keep emulator files outside `~/.aws/emulator` without changing `HOME`; the same value is used by `up`, `exec`, and `down`:
@@ -33,6 +33,6 @@ export type ResolvedEmulatorOptions = {
33
33
  startupTimeoutMs: number;
34
34
  };
35
35
  export declare function resolveEmulatorStateDirectory(value: string | undefined, environment?: NodeJS.ProcessEnv, homeDirectory?: string, workingDirectory?: string): string;
36
- export declare const DEFAULT_VERSION = "1.0.533";
36
+ export declare const DEFAULT_VERSION = "1.0.550";
37
37
  export declare function resolveEmulatorVersion(value: string | undefined, environment?: NodeJS.ProcessEnv): string;
38
38
  export declare function resolveEmulatorOptions(options: StartEmulatorOptions, environment?: NodeJS.ProcessEnv): ResolvedEmulatorOptions;
@@ -14,7 +14,7 @@ export function resolveEmulatorStateDirectory(value, environment = process.env,
14
14
  }
15
15
  return path.resolve(workingDirectory, configuredDirectory ?? path.join(homeDirectory, ".aws", "emulator"));
16
16
  }
17
- export const DEFAULT_VERSION = "1.0.533";
17
+ export const DEFAULT_VERSION = "1.0.550";
18
18
  const DEFAULT_PORT = 9297;
19
19
  const DEFAULT_MEMORY = "2g";
20
20
  function normalizeVersion(value, environment) {
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "awesome-emulator-cli",
3
- "version": "0.6.2",
3
+ "version": "0.6.4",
4
4
  "description": "Run tests for AWS SDKs in any language; the CLI manages the local emulator in Docker.",
5
5
  "type": "module",
6
6
  "main": "./dist/index.js",