chore: cleanup #109
chore: cleanup #109
Conversation
WalkthroughUpdates CHANGELOG.md for v2.13.1/2.13.0, simplifies ESLint config, converts two client option interfaces to type aliases, adds error logging and state passthrough in OAuth2 flows, enhances token util error messages, converts sdk-version.js to ESM, adds ts-nocheck to a template, and tightens a test type assertion. Changes
Sequence Diagram(s)sequenceDiagram
autonumber
actor Dev as Consumer Code
participant AC as AuthCodeAbstract
participant URL as Authorization Server
Note over Dev,AC: Generate authorization URL (state passthrough)
Dev->>AC: generateAuthURLParams(options with authUrlParams.state?)
AC->>AC: build searchParams incl. state if provided
AC-->>Dev: URLSearchParams
Note over Dev,AC: Authentication check with error logging
Dev->>AC: isAuthenticated()
AC->>AC: validate tokens/session
alt validation fails (throws)
AC->>AC: console.error(error.message)
AC-->>Dev: false
else valid
AC-->>Dev: true
end
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~25 minutes Possibly related PRs
Suggested reviewers
✨ Finishing Touches
🧪 Generate unit tests
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. CodeRabbit Commands (Invoked using PR/Issue comments)Type Other keywords and placeholders
CodeRabbit Configuration File (
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 6
🧹 Nitpick comments (7)
templates/index.mustache (1)
3-3: Avoid blanket TypeScript suppression on generated index
// @ts-nocheckhides real typing issues and can mask regressions. Prefer narrowing (e.g., exclude generated file from type-checking in tsconfig) or add a clear “generated” header to reduce confusion.Suggested tweak to make intent explicit:
+// This file is generated. Do not edit. // @ts-nocheckvitest.setup.ts (1)
7-7: Use globalThis for portability and safer mutationPrefer
globalThisoverglobalto match the web platform and avoid Node-only globals. Define the property to avoid type/readonly issues.- global.crypto = webcrypto as Crypto; + // Prefer globalThis to align with the web platform + Object.defineProperty(globalThis as any, 'crypto', { + value: webcrypto as Crypto, + configurable: true, + writable: true, + });lib/sdk/oauth2-flows/AuthCodeAbstract.ts (1)
171-173: Sanitize error logging to avoid leaking sensitive detailsCatching and logging
.messagecan inadvertently expose secrets if upstream errors include tokens. Log a generic message or a safe error code instead.- console.error(`Error checking if authenticated: ${(error as Error).message}`); + console.error('Error checking if authenticated.');Please confirm upstream errors never embed raw tokens in messages after the token-utils fix below.
lib/sdk/oauth2-flows/ClientCredentials.ts (1)
108-110: Mirror sanitized logging here as wellSame concern as in AuthCodeAbstract: prefer not to log raw error messages.
- console.error(`Error checking if authenticated: ${(error as Error).message}`); + console.error('Error checking if authenticated.');lib/sdk/utilities/token-utils.ts (1)
186-188: Consider gating noisy error logs in hot path
isTokenExpiredmay run frequently; unconditionalconsole.errorcan flood logs. Gate behind a debug flag or use a configurable logger.sdk-version.js (1)
19-20: Replace all occurrences, not just the firstString.replace only updates the first match. Use replaceAll so clean/build toggles are idempotent even if the placeholder appears more than once.
- const updatedContent = fileContent.replace(searchValue, replaceValue); + const updatedContent = fileContent.replaceAll(searchValue, replaceValue);eslint.config.mjs (1)
9-10: Consider type-aware rules if desiredThe current setup uses tseslint.configs.recommended (no type-checking). If you want type-aware linting, switch to recommendedTypeChecked and provide project tsconfig.
- ...tseslint.configs.recommended, + ...tseslint.configs.recommendedTypeChecked, + { + languageOptions: { + parserOptions: { project: ['./tsconfig.json'] }, + }, + },
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
💡 Knowledge Base configuration:
- MCP integration is disabled by default for public repositories
- Jira integration is disabled by default for public repositories
- Linear integration is disabled by default for public repositories
You can enable these sources in your CodeRabbit configuration.
⛔ Files ignored due to path filters (3)
package.jsonis excluded by!**/*.jsonpnpm-lock.yamlis excluded by!**/pnpm-lock.yaml,!**/*.yamltsconfig.jsonis excluded by!**/*.json
📒 Files selected for processing (9)
CHANGELOG.md(2 hunks)eslint.config.mjs(1 hunks)lib/sdk/clients/types.ts(1 hunks)lib/sdk/oauth2-flows/AuthCodeAbstract.ts(1 hunks)lib/sdk/oauth2-flows/ClientCredentials.ts(1 hunks)lib/sdk/utilities/token-utils.ts(2 hunks)sdk-version.js(1 hunks)templates/index.mustache(1 hunks)vitest.setup.ts(1 hunks)
🧰 Additional context used
🧬 Code graph analysis (2)
lib/sdk/utilities/token-utils.ts (1)
lib/sdk/exceptions.ts (1)
KindeSDKError(6-15)
lib/sdk/clients/types.ts (1)
lib/sdk/oauth2-flows/types.ts (2)
AuthorizationCodeOptions(44-48)ClientCredentialsOptions(50-54)
🪛 GitHub Actions: Build and test TypeScript SDK CI
eslint.config.mjs
[error] 1-1: ESLint failed: Cannot find package 'globals' imported from eslint.config.mjs. Did you mean to import [email protected]/node_modules/globals/index.js?
🔇 Additional comments (1)
sdk-version.js (1)
1-1: Verify Node version compatibility before changing JSON import
I couldn’t locate any CI workflow configs or an “engines.node” setting to confirm which Node versions you support, so please verify your build environment’s Node versions before replacingimport packageJson from './package.json' with { type: 'json' };with either the
assert { type: 'json' }import or the fs-based JSON load.
| Generated by [`auto-changelog`](https://github.com/CookPete/auto-changelog). | ||
|
|
||
| #### [2.13.0](https://github.com/kinde-oss/kinde-typescript-sdk/compare/4.6.2...2.13.0) | ||
| #### [2.13.1](https://github.com/kinde-oss/kinde-typescript-sdk/compare/4.6.2...2.13.1) |
There was a problem hiding this comment.
Incorrect compare link in 2.13.1 header
"compare/4.6.2...2.13.1" appears wrong; likely should compare v2.13.0...v2.13.1.
-#### [2.13.1](https://github.com/kinde-oss/kinde-typescript-sdk/compare/4.6.2...2.13.1)
+#### [v2.13.1](https://github.com/kinde-oss/kinde-typescript-sdk/compare/v2.13.0...v2.13.1)📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| #### [2.13.1](https://github.com/kinde-oss/kinde-typescript-sdk/compare/4.6.2...2.13.1) | |
| #### [v2.13.1](https://github.com/kinde-oss/kinde-typescript-sdk/compare/v2.13.0...v2.13.1) |
🤖 Prompt for AI Agents
CHANGELOG.md around lines 7 to 7: the release header for 2.13.1 contains an
incorrect GitHub compare link "compare/4.6.2...2.13.1"; update the URL to
compare the previous tag to this tag (e.g., "compare/v2.13.0...v2.13.1" or the
repo's tag naming convention) so the link correctly shows changes between the
prior release and 2.13.1.
| ### [4.6.2](https://github.com/kinde-oss/kinde-typescript-sdk/compare/v2.13.0...4.6.2) | ||
|
|
||
| > 24 January 2024 | ||
| #### [v2.13.0](https://github.com/kinde-oss/kinde-typescript-sdk/compare/v2.12.0...v2.13.0) | ||
|
|
||
| > 31 August 2025 | ||
| - chore(deps): update dependency @typescript-eslint/eslint-plugin to v8 [`#99`](https://github.com/kinde-oss/kinde-typescript-sdk/pull/99) | ||
| - chore(deps): update dependency prettier to v3.6.2 [`#94`](https://github.com/kinde-oss/kinde-typescript-sdk/pull/94) | ||
| - chore(deps): update dependency lint-staged to v16 [`#102`](https://github.com/kinde-oss/kinde-typescript-sdk/pull/102) | ||
| - chore(deps): update dependency husky to v9 [`#100`](https://github.com/kinde-oss/kinde-typescript-sdk/pull/100) | ||
| - chore(deps): update dependency @tsconfig/node18 to v18 [`#97`](https://github.com/kinde-oss/kinde-typescript-sdk/pull/97) | ||
| - chore(deps): update actions/setup-node action to v4 [`#96`](https://github.com/kinde-oss/kinde-typescript-sdk/pull/96) | ||
| - chore(deps): update actions/checkout action to v5 [`#95`](https://github.com/kinde-oss/kinde-typescript-sdk/pull/95) | ||
| - chore(deps): update dependency @types/node to v22 [`#98`](https://github.com/kinde-oss/kinde-typescript-sdk/pull/98) | ||
| - chore(deps): update dependency jose to v6.1.0 [`#93`](https://github.com/kinde-oss/kinde-typescript-sdk/pull/93) | ||
| - chore(deps): update dependency eslint-plugin-prettier to v5.5.4 [`#92`](https://github.com/kinde-oss/kinde-typescript-sdk/pull/92) | ||
| - chore(deps): update dependency eslint-plugin-n to v17.21.3 [`#91`](https://github.com/kinde-oss/kinde-typescript-sdk/pull/91) | ||
| - chore(deps): update dependency eslint-plugin-import to v2.32.0 [`#90`](https://github.com/kinde-oss/kinde-typescript-sdk/pull/90) | ||
| - chore(deps): update dependency eslint to v9.34.0 [`#89`](https://github.com/kinde-oss/kinde-typescript-sdk/pull/89) | ||
| - chore(deps): update dependency @types/node to v20.19.11 [`#88`](https://github.com/kinde-oss/kinde-typescript-sdk/pull/88) | ||
| - fix(deps): update dependency @kinde/js-utils to v0.23.0 [`#86`](https://github.com/kinde-oss/kinde-typescript-sdk/pull/86) | ||
| - fix(deps): update dependency @typescript-eslint/parser to v8.41.0 [`#87`](https://github.com/kinde-oss/kinde-typescript-sdk/pull/87) | ||
| - chore(deps): update dependency typescript to v5.9.2 [`#85`](https://github.com/kinde-oss/kinde-typescript-sdk/pull/85) | ||
| - chore(deps): update dependency @openapitools/openapi-generator-cli to v2.23.1 [`#83`](https://github.com/kinde-oss/kinde-typescript-sdk/pull/83) | ||
| - chore(deps): update dependency eslint-config-prettier to v10.1.8 [`#82`](https://github.com/kinde-oss/kinde-typescript-sdk/pull/82) | ||
| - [Snyk] Upgrade @kinde/js-utils from 0.19.0 to 0.20.1 [`#78`](https://github.com/kinde-oss/kinde-typescript-sdk/pull/78) | ||
| - chore: Configure Renovate [`#81`](https://github.com/kinde-oss/kinde-typescript-sdk/pull/81) | ||
| - chore: release v2.13.0 [`557836b`](https://github.com/kinde-oss/kinde-typescript-sdk/commit/557836bfa077bed72569babc052f5e73e6356263) | ||
| - Merge pull request #80 from kinde-oss/feat/session-persistence [`057e5c0`](https://github.com/kinde-oss/kinde-typescript-sdk/commit/057e5c0857f104f4f4f9c5f0a5f48deea0af0dce) | ||
| - feat: set sessionManager persistent property depending on accessToken flag [`7fe1a6c`](https://github.com/kinde-oss/kinde-typescript-sdk/commit/7fe1a6c61053d804ec1e688602880ec29ce730cb) | ||
|
|
There was a problem hiding this comment.
💡 Verification agent
🧩 Analysis chain
Misordered/duplicated sections: v2.13.0 nested under 4.6.2
The "4.6.2" section precedes and embeds "v2.13.0" dated 31 August 2025, which is chronologically inconsistent and confusing.
Proposed cleanup (outline):
- Keep v2.13.1 at top.
- Follow with v2.13.0 (31 August 2025).
- Move 4.6.2 back to its correct 2024 position.
- Use consistent "v" prefix for tags.
If using auto-changelog, regenerate:
🏁 Script executed:
#!/bin/bash
npx auto-changelog -p -u --tag-prefix vLength of output: 510
🏁 Script executed:
#!/bin/bash
echo "Searching for package.json..."
fd -t f package.json || echo "package.json not found"
echo "Searching for CHANGELOG.md..."
fd -t f CHANGELOG.md || echo "CHANGELOG.md not found"Length of output: 196
🏁 Script executed:
sed -n '40,100p' CHANGELOG.mdLength of output: 5715
Reorder and dedupe CHANGELOG.md sections
- Remove the nested
#### [v2.13.0]under### [4.6.2](it’s already listed at the top). - Move
### [4.6.2](24 January 2024) below the v2.12.0 block to restore chronological order. - Prefix all release headers consistently with
v(e.g.,### [v4.6.2]). - Note: there’s no root package.json, so
npx auto-changelogwill fail—either add package.json or apply these edits manually.
🤖 Prompt for AI Agents
In CHANGELOG.md around lines 51-83, the v2.13.0 block is incorrectly nested
under the 4.6.2 entry and header formats/ordering are inconsistent; remove the
nested "#### [v2.13.0]" block from under "### [4.6.2]" (it already exists at the
top), move the entire "### [4.6.2] (24 January 2024)" section so it appears
chronologically below the v2.12.0 block, and update all release headers to
consistently use the "v" prefix (e.g., change "### [4.6.2]" to "### [v4.6.2]");
apply these edits directly in the file (manual change) since there is no root
package.json for auto-changelog.
| import globals from 'globals'; | ||
| import pluginJs from '@eslint/js'; | ||
| import tseslint from 'typescript-eslint'; |
There was a problem hiding this comment.
💡 Verification agent
🧩 Analysis chain
CI failing: missing 'globals' dependency; add it or avoid the import
Build pipeline error: "Cannot find package 'globals'". Add it to devDependencies (preferred) or drop the dependency and inline minimal globals.
Option A (add dependency):
--- a/package.json
+++ b/package.json
@@
"devDependencies": {
+ "globals": "^15.0.0"
}
}Option B (avoid dependency; inline minimal globals):
-import globals from 'globals';
+const browserGlobals = { window: 'readonly', document: 'readonly', navigator: 'readonly' };
@@
-export default defineConfig([
- { languageOptions: { globals: globals.browser } },
+export default defineConfig([
+ { languageOptions: { globals: browserGlobals } },Additionally, to fix Node globals for scripts (and remove no-undef comments), scope Node globals:
+ { files: ['sdk-version.js', 'scripts/**'], languageOptions: { globals: { process: 'readonly', __dirname: 'readonly', module: 'readonly', require: 'readonly' } } },After applying, re-run ESLint locally/CI.
Also applies to: 7-11
🏁 Script executed:
#!/bin/bash
node -v
npm ls globals || echo "globals not installed"
npx eslint . -vLength of output: 232
Add missing ‘globals’ package (or inline minimal globals) to fix ESLint CI
CI is failing: 'globals' is not installed (npm ls globals reports “globals not installed”).
Option A: add to devDependencies (preferred)
--- a/package.json
+++ b/package.json
@@ -...devDependencies
"devDependencies": {
+ "globals": "^15.0.0"
}Option B: inline minimal browser globals in eslint.config.mjs
-import globals from 'globals';
+const browserGlobals = { window: 'readonly', document: 'readonly', navigator: 'readonly' };
@@
-export default defineConfig([
- { languageOptions: { globals: globals.browser } },
+export default defineConfig([
+ { languageOptions: { globals: browserGlobals } },Also scope Node globals for scripts:
+ { files: ['sdk-version.js', 'scripts/**'], languageOptions: { globals: { process: 'readonly', __dirname: 'readonly', module: 'readonly', require: 'readonly' } } },Re-run ESLint locally/CI to confirm.
Committable suggestion skipped: line range outside the PR's diff.
🧰 Tools
🪛 GitHub Actions: Build and test TypeScript SDK CI
[error] 1-1: ESLint failed: Cannot find package 'globals' imported from eslint.config.mjs. Did you mean to import [email protected]/node_modules/globals/index.js?
🤖 Prompt for AI Agents
In eslint.config.mjs around lines 1-3, CI is failing because the 'globals'
package is not installed; fix by either (preferred) adding "globals" to
devDependencies (run npm/yarn add --dev globals and update package.json) and
re-run ESLint, or (alternative) remove the import and inline a minimal globals
object (e.g., declare needed browser globals and Node globals scoped to scripts)
directly in eslint.config.mjs so ESLint can resolve them; after applying either
change, run ESLint locally/CI to confirm the failure is resolved.
| export type PKCEClientOptions = AuthorizationCodeOptions; | ||
| export type CCClientOptions = ClientCredentialsOptions; |
There was a problem hiding this comment.
💡 Verification agent
🧩 Analysis chain
Changing interface to type alias may break declaration merging
External consumers can augment interfaces via declaration merging; type aliases cannot be merged. This can be a subtle semver break.
If any consumer augments PKCEClientOptions/CCClientOptions, keep them as interfaces. Otherwise, add a note to the changelog under "Potentially breaking (types only)". To verify in-repo usage:
If you want the newer style without risk, keep interfaces but export companion aliases:
export interface PKCEClientOptions extends AuthorizationCodeOptions {}
export type PKCEClientOptionsT = AuthorizationCodeOptions;
export interface CCClientOptions extends ClientCredentialsOptions {}
export type CCClientOptionsT = ClientCredentialsOptions;🏁 Script executed:
#!/bin/bash
rg -nP '\b(interface|type)\s+PKCEClientOptions\b|extends\s+PKCEClientOptions\b|declare\s+module[^\n]*\{[^\}]*interface\s+PKCEClientOptions' -C2
rg -nP '\b(interface|type)\s+CCClientOptions\b|extends\s+CCClientOptions\b|declare\s+module[^\n]*\{[^\}]*interface\s+CCClientOptions' -C2Length of output: 1612
Add changelog entry for potential type-breaking change
No internal declaration merges for PKCEClientOptions/CCClientOptions were found; both are now type aliases. Add a note under “Potentially breaking (types only)” in CHANGELOG.md. If you need to preserve declaration-merging compatibility for external consumers, revert these to interfaces or export companion aliases.
🤖 Prompt for AI Agents
In lib/sdk/clients/types.ts around lines 18-19, PKCEClientOptions and
CCClientOptions were changed to type aliases which can break external
declaration-merging; either add a note under “Potentially breaking (types only)”
in CHANGELOG.md describing this change and its impact, or restore
declaration-merging compatibility by reverting these to exported interfaces (or
add companion exported interface aliases) so external consumers relying on
declaration merging won’t break—update CHANGELOG.md if you keep the aliases, or
change the types back to interfaces and run a quick type-check to confirm no
regressions.
| } catch (error) { | ||
| throw new KindeSDKError( | ||
| KindeSDKErrorCode.INVALID_TOKEN_MEMORY_COMMIT, | ||
| `Attempting to commit invalid ${type} token "${token}" to memory` | ||
| `Attempting to commit invalid ${type} token "${token}" to memory: ${(error as Error).message}` | ||
| ); |
There was a problem hiding this comment.
💡 Verification agent
🧩 Analysis chain
Secret leakage: error message includes the raw token
Embedding the full access/id token in the thrown error is a high-severity issue. These errors are now logged by callers, which would leak tokens to logs.
Apply this to remove the token from the message (or replace with a minimal fingerprint if you need correlation):
- `Attempting to commit invalid ${type} token "${token}" to memory: ${(error as Error).message}`
+ `Attempting to commit invalid ${type} token to memory: ${(error as Error).message}`Please scan for any other error/log strings that include secrets (tokens, client secrets).
🏁 Script executed:
#!/bin/bash
set -e
# Search for any string interpolation including “token” (potential secret leakage)
rg -n --color=never '\$\{[^}]*token' -C2 .
# Search for console.log/error/warn usages including “token”
rg -n --color=never 'console\.(log|error|warn).*token' -C2 .
# Search for thrown errors that reference “token”
rg -n --color=never 'throw new .*token' -C2 .
# Search for any literal “secret” in error/log messages
rg -n --color=never 'secret' -C2 .Length of output: 12689
Sanitize secret values in error messages
- lib/sdk/utilities/token-utils.ts: remove raw
${token}from the KindeSDKError message (replace with a fingerprint or omit entirely)- `Attempting to commit invalid ${type} token "${token}" to memory: ${(error as Error).message}` + `Attempting to commit invalid ${type} token to memory: ${(error as Error).message}`
- lib/sdk/oauth2-flows/ClientCredentials.ts (generateTokenURLParams): remove
${this.config.clientSecret}from the thrown Error - lib/sdk/oauth2-flows/AuthorizationCode.ts: remove
${this.clientSecret}from all thrown Errors
Scan the codebase for any other error/log strings that interpolate tokens or client secrets and mask or omit them.
📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| } catch (error) { | |
| throw new KindeSDKError( | |
| KindeSDKErrorCode.INVALID_TOKEN_MEMORY_COMMIT, | |
| `Attempting to commit invalid ${type} token "${token}" to memory` | |
| `Attempting to commit invalid ${type} token "${token}" to memory: ${(error as Error).message}` | |
| ); | |
| } catch (error) { | |
| throw new KindeSDKError( | |
| KindeSDKErrorCode.INVALID_TOKEN_MEMORY_COMMIT, | |
| `Attempting to commit invalid ${type} token to memory: ${(error as Error).message}` | |
| ); |
🤖 Prompt for AI Agents
In lib/sdk/utilities/token-utils.ts around lines 43-47, remove the raw
`${token}` from the KindeSDKError message and either omit the token or replace
it with a non-reversible fingerprint (e.g., short hash or last 4 chars only) to
avoid leaking secrets; similarly, in lib/sdk/oauth2-flows/ClientCredentials.ts
(generateTokenURLParams) and lib/sdk/oauth2-flows/AuthorizationCode.ts remove
any interpolation of `${this.config.clientSecret}` / `${this.clientSecret}` from
thrown Errors and logs and replace with a masked placeholder or fingerprint.
Apply the same change across the codebase: search for error/log strings that
interpolate tokens, client secrets, or other credentials and replace them with
masked values or omit them entirely, ensuring no raw secrets are present in
exceptions or logging messages.
| // eslint-disable-next-line no-undef | ||
| const isCleanArg = process.argv[2] === 'clean'; |
There was a problem hiding this comment.
🛠️ Refactor suggestion
Remove eslint-disable by scoping Node globals in ESLint
This file runs in Node; configure ESLint to know about process instead of disabling the rule.
In eslint.config.mjs add a file override:
export default defineConfig([
- { languageOptions: { globals: globals.browser } },
+ { languageOptions: { globals: { ...globals.browser } } },
+ { files: ['sdk-version.js', 'scripts/**'], languageOptions: { globals: { ...globals.node } } },
globalIgnores(['dist', 'node_modules', 'coverage/**', 'dist-cjs']),
pluginJs.configs.recommended,
...tseslint.configs.recommended,
]);📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| // eslint-disable-next-line no-undef | |
| const isCleanArg = process.argv[2] === 'clean'; | |
| export default defineConfig([ | |
| // explicitly spread the browser globals object | |
| { languageOptions: { globals: { ...globals.browser } } }, | |
| // enable Node globals (e.g. `process`) for sdk-version.js and scripts/** | |
| { files: ['sdk-version.js', 'scripts/**'], languageOptions: { globals: { ...globals.node } } }, | |
| globalIgnores(['dist', 'node_modules', 'coverage/**', 'dist-cjs']), | |
| pluginJs.configs.recommended, | |
| ...tseslint.configs.recommended, | |
| ]); |
🤖 Prompt for AI Agents
In sdk-version.js around lines 13 to 14, the rule is disabled with an inline
eslint comment for the Node global "process"; instead configure ESLint to
recognize Node globals by adding a file override in eslint.config.mjs that
targets this file (or its pattern) and sets env: { node: true } (or declares the
needed globals), then remove the inline eslint-disable comment from
sdk-version.js so the file relies on the linter config.
Explain your changes
Removing redundant dependencies and cleaning up some bits.
Checklist
🛟 If you need help, consider asking for advice over in the Kinde community.