src/version.ts (1)

1-1: Consider automating version synchronisation with package.json.

Manually maintaining the SDK version in this file creates a risk of drift from package.json. Consider importing the version from package.json at build time or using a build script to inject it, ensuring consistency.

That said, the current approach is functional and acceptable for now.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/version.ts` at line 1, The SDK_VERSION constant is manually maintained
and can drift from package.json; change the implementation so SDK_VERSION is
sourced from package.json at build/runtime (or injected by a build script)
instead of a hardcoded string: replace the current SDK_VERSION export with logic
that reads the "version" field from package.json (or uses an injected env var
during build) and export that value so SDK_VERSION always matches package.json’s
version.

src/__tests__/context.test.js (1)

480-484: Remove unused systemAttributes constant.

This constant is defined but never used in the test file. The tests directly check individual attributes inline instead. Consider removing this dead code to avoid confusion.

🧹 Suggested fix

 client.getAgent.mockReturnValue("absmartly-javascript-sdk");
 client.getApplication.mockReturnValue({ name: "website", version: 0 });
 client.getEnvironment.mockReturnValue("production");
-
-const systemAttributes = [
-	{ name: "sdk_version", value: expect.any(String), setAt: expect.any(Number) },
-	{ name: "application", value: "website", setAt: expect.any(Number) },
-	{ name: "environment", value: "production", setAt: expect.any(Number) },
-];

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/__tests__/context.test.js` around lines 480 - 484, Remove the dead
variable declaration systemAttributes from the test file (the const named
systemAttributes in src/__tests__/context.test.js) since it is never referenced;
simply delete the entire const systemAttributes = [...] block to clean up unused
code and keep the tests focused on the inline expectations that already assert
those attributes.

README.md (1)

160-160: Consider tightening wording in Line 160 for readability.

“prepended to the publish payload” reads a bit awkwardly; “prepended to the published payload” (or “publish request payload”) is clearer.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@README.md` at line 160, The sentence "When enabled, the following attributes
are automatically prepended to the publish payload:" is awkward; update that
line (the string "When enabled, the following attributes are automatically
prepended to the publish payload:") to clearer wording such as "When enabled,
the following attributes are automatically prepended to the published payload:"
or "When enabled, the following attributes are automatically prepended to the
publish request payload:" to improve readability.