Conversation
|
Caution Review failedFailed to post review comments. Summary by CodeRabbit
Summary by CodeRabbit
WalkthroughThis update introduces a configurable log queue size and exposes dropped log metrics in the Bifrost HTTP transport and UI. The backend now tracks and reports dropped log entries, centralizes default client config, and persists environment variable references in config files. The UI reflects these changes, adds live dropped log stats, and updates branding, static assets, and layout. Changes
Sequence Diagram(s)sequenceDiagram
participant User
participant UI
participant API
participant LoggingPlugin
User->>UI: Change log queue size in settings
UI->>API: PATCH /api/config (with log_queue_size)
API->>LoggingPlugin: Update log queue size
API-->>UI: 200 OK
User->>UI: View dropped logs metric
UI->>API: GET /api/logs/dropped
API->>LoggingPlugin: GetDroppedRequests()
LoggingPlugin-->>API: dropped_requests count
API-->>UI: { dropped_requests: N }
Suggested reviewers
Poem
✨ Finishing Touches
🧪 Generate unit tests
🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
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: 4
📜 Review details
Configuration used: CodeRabbit UI
Review profile: ASSERTIVE
Plan: Pro
📒 Files selected for processing (28)
transports/bifrost-http/handlers/config.go(1 hunks)transports/bifrost-http/handlers/logging.go(2 hunks)transports/bifrost-http/lib/config.go(1 hunks)transports/bifrost-http/lib/store.go(6 hunks)transports/bifrost-http/main.go(1 hunks)transports/bifrost-http/plugins/logging/main.go(8 hunks)transports/bifrost-http/plugins/logging/utils.go(8 hunks)transports/bifrost-http/ui/404.html(2 hunks)transports/bifrost-http/ui/404/index.html(2 hunks)transports/bifrost-http/ui/_next/static/chunks/341-25f02d71bd620aa0.js(1 hunks)transports/bifrost-http/ui/_next/static/chunks/341-5aa9f869e119bce4.js(0 hunks)transports/bifrost-http/ui/_next/static/chunks/app/config/page-afdfa4a22ecb6a17.js(1 hunks)transports/bifrost-http/ui/_next/static/chunks/app/config/page-bf3c65256b3fc98b.js(0 hunks)transports/bifrost-http/ui/_next/static/chunks/app/page-3018cf06890a2414.js(1 hunks)transports/bifrost-http/ui/_next/static/chunks/app/page-9c52c1dd03452de9.js(0 hunks)transports/bifrost-http/ui/_next/static/css/0451d03ec40c67fa.css(0 hunks)transports/bifrost-http/ui/_next/static/css/d3f26c86d016c77c.css(1 hunks)transports/bifrost-http/ui/config/index.html(2 hunks)transports/bifrost-http/ui/config/index.txt(1 hunks)transports/bifrost-http/ui/docs/index.txt(1 hunks)transports/bifrost-http/ui/index.html(2 hunks)transports/bifrost-http/ui/index.txt(1 hunks)transports/go.mod(0 hunks)ui/app/plugins/page.tsx(1 hunks)ui/components/config/core-settings-list.tsx(5 hunks)ui/components/config/providers-list.tsx(1 hunks)ui/lib/api.ts(1 hunks)ui/lib/types/config.ts(1 hunks)
💤 Files with no reviewable changes (5)
- transports/go.mod
- transports/bifrost-http/ui/_next/static/chunks/341-5aa9f869e119bce4.js
- transports/bifrost-http/ui/_next/static/chunks/app/config/page-bf3c65256b3fc98b.js
- transports/bifrost-http/ui/_next/static/css/0451d03ec40c67fa.css
- transports/bifrost-http/ui/_next/static/chunks/app/page-9c52c1dd03452de9.js
🧰 Additional context used
🧠 Learnings (13)
📓 Common learnings
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#148
File: transports/bifrost-http/lib/store.go:1081-1098
Timestamp: 2025-07-08T17:16:50.780Z
Learning: Pratham-Mishra04 prefers practical redaction approaches over theoretical security improvements when the threat model is low-risk, such as admin-only interfaces in the Bifrost project. Fixed-length redaction is acceptable when only trusted administrators will see the redacted values.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#55
File: core/providers/anthropic.go:358-388
Timestamp: 2025-06-04T05:37:59.699Z
Learning: User Pratham-Mishra04 prefers not to extract small code duplications (around 2 lines) into helper functions, considering the overhead not worth it for such minor repetition.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#102
File: README.md:62-66
Timestamp: 2025-06-19T17:03:03.639Z
Learning: Pratham-Mishra04 prefers using the implicit 'latest' tag for the maximhq/bifrost Docker image rather than pinning to specific versions.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#143
File: core/mcp.go:155-196
Timestamp: 2025-07-08T15:33:47.645Z
Learning: Pratham-Mishra04 prefers not to add explanatory comments for obvious code patterns, such as the unlock/lock strategy around network I/O operations, considering them self-explanatory to experienced developers.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#141
File: core/bifrost.go:198-272
Timestamp: 2025-07-08T18:30:08.221Z
Learning: Pratham-Mishra04 follows a pattern of implementing core functionality first and deferring non-critical improvements (like race condition fixes, optimizations) to later PRs. This is a reasonable development approach that prioritizes getting the main feature working before addressing edge cases.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#138
File: docs/usage/go-package/mcp.md:408-412
Timestamp: 2025-07-01T12:40:08.576Z
Learning: Pratham-Mishra04 is okay with keeping bullet list formatting that uses colons after dashes in markdown documentation, even if it triggers linter warnings, preferring functionality over strict formatting rules.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#148
File: transports/bifrost-http/lib/store.go:880-910
Timestamp: 2025-07-08T17:14:21.532Z
Learning: Pratham-Mishra04 prefers resilient system design where missing environment variables for MCP connections should not cause complete system failure. The system should continue processing other MCP connections even when some fail, maintaining partial functionality rather than implementing fail-fast behavior.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#138
File: transports/README.md:26-28
Timestamp: 2025-07-01T12:45:06.906Z
Learning: Pratham-Mishra04 prefers keeping documentation examples simple and concise, trusting users to handle production-specific considerations like version pinning themselves rather than cluttering examples with additional notes.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#144
File: transports/bifrost-http/plugins/logging/utils.go:286-292
Timestamp: 2025-07-08T16:40:59.079Z
Learning: Pratham-Mishra04 prefers to keep simpler error handling patterns when errors are unlikely to occur in practice, such as safety checks in BadgerDB iterations where item.Value() is called on valid items. The user considers the overhead of explicit error handling not worth it in such scenarios.
transports/bifrost-http/main.go (2)
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#149
File: transports/bifrost-http/plugins/logging/main.go:0-0
Timestamp: 2025-07-08T18:09:32.114Z
Learning: In the Bifrost HTTP transport logging plugin (transports/bifrost-http/plugins/logging/main.go), the DatabasePath is explicitly set from main.go via a config struct pointing to appDir/logs, so the default value in the NewLoggerPlugin constructor is only used for standalone plugin usage and doesn't affect the main application flow.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#149
File: transports/bifrost-http/main.go:259-261
Timestamp: 2025-07-08T18:20:24.042Z
Learning: In transports/bifrost-http/lib/store.go, the LoadFromConfig method already handles missing config files gracefully by initializing defaults and auto-detecting providers from environment variables. It only returns errors for actual parsing/processing failures, not missing files, making log.Fatalf appropriate in main.go since real errors should terminate the program.
transports/bifrost-http/handlers/config.go (1)
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#149
File: transports/bifrost-http/main.go:259-261
Timestamp: 2025-07-08T18:20:24.042Z
Learning: In transports/bifrost-http/lib/store.go, the LoadFromConfig method already handles missing config files gracefully by initializing defaults and auto-detecting providers from environment variables. It only returns errors for actual parsing/processing failures, not missing files, making log.Fatalf appropriate in main.go since real errors should terminate the program.
transports/bifrost-http/handlers/logging.go (2)
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#144
File: transports/bifrost-http/handlers/websocket.go:44-46
Timestamp: 2025-07-08T15:55:40.453Z
Learning: In the Bifrost HTTP transport WebSocket handler (transports/bifrost-http/handlers/websocket.go), the WebSocket `/ws/logs` endpoint is designed to be used by HTML served on the same port, making it a same-origin connection which reduces the security risk of allowing all origins in the CheckOrigin function.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#149
File: transports/bifrost-http/plugins/logging/main.go:0-0
Timestamp: 2025-07-08T18:09:32.114Z
Learning: In the Bifrost HTTP transport logging plugin (transports/bifrost-http/plugins/logging/main.go), the DatabasePath is explicitly set from main.go via a config struct pointing to appDir/logs, so the default value in the NewLoggerPlugin constructor is only used for standalone plugin usage and doesn't affect the main application flow.
transports/bifrost-http/ui/index.txt (2)
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#103
File: .github/workflows/transport-dependency-update.yml:53-75
Timestamp: 2025-06-20T16:21:18.912Z
Learning: In the bifrost repository's transport dependency update workflow, when updating the core dependency to a new version using `go get`, the go.mod and go.sum files will always change in normal operation, making the safety check for changes more of a defensive programming practice rather than handling a common scenario.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#54
File: core/schemas/provider.go:148-148
Timestamp: 2025-06-04T03:57:50.981Z
Learning: Breaking changes in the Bifrost codebase are managed by first merging and tagging core schema changes, then updating dependent code references in subsequent steps after the core version is released.
transports/bifrost-http/lib/config.go (3)
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#94
File: core/schemas/bifrost.go:20-23
Timestamp: 2025-06-18T15:16:23.127Z
Learning: In the Bifrost project, BifrostConfig struct is never marshaled/unmarshaled, so serialization tags (json, yaml) are not needed for its fields.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#149
File: transports/bifrost-http/main.go:259-261
Timestamp: 2025-07-08T18:20:24.042Z
Learning: In transports/bifrost-http/lib/store.go, the LoadFromConfig method already handles missing config files gracefully by initializing defaults and auto-detecting providers from environment variables. It only returns errors for actual parsing/processing failures, not missing files, making log.Fatalf appropriate in main.go since real errors should terminate the program.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#144
File: transports/bifrost-http/plugins/logging/utils.go:509-514
Timestamp: 2025-07-08T16:48:25.373Z
Learning: In the Bifrost logging system (transports/bifrost-http/plugins/logging/utils.go), the Content field in message structures is a struct value type, not a pointer, so it will never be nil and doesn't require nil checks. However, ContentStr within Content is a pointer and should be checked for nil.
transports/bifrost-http/ui/index.html (2)
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#54
File: core/schemas/provider.go:148-148
Timestamp: 2025-06-04T03:57:50.981Z
Learning: Breaking changes in the Bifrost codebase are managed by first merging and tagging core schema changes, then updating dependent code references in subsequent steps after the core version is released.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#103
File: .github/workflows/transport-dependency-update.yml:53-75
Timestamp: 2025-06-20T16:21:18.912Z
Learning: In the bifrost repository's transport dependency update workflow, when updating the core dependency to a new version using `go get`, the go.mod and go.sum files will always change in normal operation, making the safety check for changes more of a defensive programming practice rather than handling a common scenario.
transports/bifrost-http/plugins/logging/main.go (10)
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#149
File: transports/bifrost-http/plugins/logging/main.go:0-0
Timestamp: 2025-07-08T18:09:32.114Z
Learning: In the Bifrost HTTP transport logging plugin (transports/bifrost-http/plugins/logging/main.go), the DatabasePath is explicitly set from main.go via a config struct pointing to appDir/logs, so the default value in the NewLoggerPlugin constructor is only used for standalone plugin usage and doesn't affect the main application flow.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#79
File: core/bifrost.go:94-103
Timestamp: 2025-06-14T04:06:58.240Z
Learning: In core/bifrost.go, the count parameter in RunPostHooks method is intentionally kept separate from p.executedPreHooks to support circuit breaker plugins that may need to trigger PostHooks for only a subset of executed plugins when detecting failure conditions mid-execution.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#144
File: transports/bifrost-http/plugins/logging/utils.go:509-514
Timestamp: 2025-07-08T16:48:25.373Z
Learning: In the Bifrost logging system (transports/bifrost-http/plugins/logging/utils.go), the Content field in message structures is a struct value type, not a pointer, so it will never be nil and doesn't require nil checks. However, ContentStr within Content is a pointer and should be checked for nil.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#144
File: transports/bifrost-http/plugins/logging/utils.go:286-292
Timestamp: 2025-07-08T16:40:59.079Z
Learning: Pratham-Mishra04 prefers to keep simpler error handling patterns when errors are unlikely to occur in practice, such as safety checks in BadgerDB iterations where item.Value() is called on valid items. The user considers the overhead of explicit error handling not worth it in such scenarios.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#55
File: core/providers/bedrock.go:443-468
Timestamp: 2025-06-04T09:32:15.826Z
Learning: In core/providers/bedrock.go, for tool call result messages (ModelChatMessageRoleTool), the Content field represents the actual tool call output. A tool result message should only be created when msg.Content is non-nil, as there's no semantic meaning to a tool result without output content.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#55
File: core/providers/bedrock.go:750-791
Timestamp: 2025-06-04T06:09:18.600Z
Learning: In the Bedrock provider, tool result messages maintain their original tool role in the input messages. The remapping from tool role to user role only occurs during message preparation for the Bedrock API request in `prepareChatCompletionMessages`, not in the original input. The `extractToolsFromHistory` function operates on unprocessed input messages where tool results retain their tool role.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#54
File: core/schemas/bifrost.go:46-49
Timestamp: 2025-06-04T09:22:18.123Z
Learning: In core/schemas/bifrost.go, the RequestInput struct uses ChatCompletionInput *[]BifrostMessage (pointer-to-slice) rather than []BifrostMessage to properly represent union type semantics. For text completion requests, ChatCompletionInput should be nil to indicate "no chat payload at all", while for chat completion requests it should be non-nil (even if empty slice). This distinguishes between different request types rather than just empty vs non-empty chat messages.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#65
File: transports/bifrost-http/integrations/utils.go:169-173
Timestamp: 2025-06-09T17:33:52.234Z
Learning: The ChatCompletionRequest method in the Bifrost client follows a contract where the result parameter will never be nil if the error parameter is nil. This means when error checking passes (err == nil), the result is guaranteed to be valid and can be safely used without additional nil checks.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#55
File: core/providers/anthropic.go:526-550
Timestamp: 2025-06-04T09:29:46.287Z
Learning: In core/providers/anthropic.go, the content field in formattedMessages is always of type []interface{} because it's explicitly constructed that way upstream in the prepareAnthropicChatRequest function. Defensive type casting for multiple types is not needed since the type is guaranteed by the construction logic.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#81
File: tests/core-providers/scenarios/end_to_end_tool_calling.go:43-45
Timestamp: 2025-06-16T04:13:55.437Z
Learning: In the Bifrost codebase, errors returned from client methods like ChatCompletionRequest are of type BifrostError, not the standard error interface. For testing these errors, use require.Nilf instead of require.NoErrorf since BifrostError doesn't work with the standard error assertion methods.
transports/bifrost-http/ui/_next/static/chunks/app/config/page-afdfa4a22ecb6a17.js (1)
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#85
File: core/providers/anthropic.go:150-156
Timestamp: 2025-06-15T16:07:53.140Z
Learning: In the Bifrost codebase, constructor functions are allowed to mutate input ProviderConfig objects in-place (e.g., setting default BaseURL values and trimming trailing slashes). This pattern is acceptable and doesn't need to be flagged as a code review issue.
transports/bifrost-http/ui/config/index.txt (2)
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#103
File: .github/workflows/transport-dependency-update.yml:53-75
Timestamp: 2025-06-20T16:21:18.912Z
Learning: In the bifrost repository's transport dependency update workflow, when updating the core dependency to a new version using `go get`, the go.mod and go.sum files will always change in normal operation, making the safety check for changes more of a defensive programming practice rather than handling a common scenario.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#54
File: core/schemas/provider.go:148-148
Timestamp: 2025-06-04T03:57:50.981Z
Learning: Breaking changes in the Bifrost codebase are managed by first merging and tagging core schema changes, then updating dependent code references in subsequent steps after the core version is released.
transports/bifrost-http/lib/store.go (6)
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#149
File: transports/bifrost-http/main.go:259-261
Timestamp: 2025-07-08T18:20:24.042Z
Learning: In transports/bifrost-http/lib/store.go, the LoadFromConfig method already handles missing config files gracefully by initializing defaults and auto-detecting providers from environment variables. It only returns errors for actual parsing/processing failures, not missing files, making log.Fatalf appropriate in main.go since real errors should terminate the program.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#149
File: transports/bifrost-http/plugins/logging/main.go:0-0
Timestamp: 2025-07-08T18:09:32.114Z
Learning: In the Bifrost HTTP transport logging plugin (transports/bifrost-http/plugins/logging/main.go), the DatabasePath is explicitly set from main.go via a config struct pointing to appDir/logs, so the default value in the NewLoggerPlugin constructor is only used for standalone plugin usage and doesn't affect the main application flow.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#84
File: core/providers/ollama.go:59-61
Timestamp: 2025-06-15T14:34:29.401Z
Learning: The `CheckAndSetDefaults()` method on `*schemas.ProviderConfig` in Go does not return any error - it has a void return type and only sets default values on the configuration struct.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#85
File: core/providers/anthropic.go:150-156
Timestamp: 2025-06-15T16:07:53.140Z
Learning: In the Bifrost codebase, constructor functions are allowed to mutate input ProviderConfig objects in-place (e.g., setting default BaseURL values and trimming trailing slashes). This pattern is acceptable and doesn't need to be flagged as a code review issue.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#131
File: transports/bifrost-http/lib/config.go:35-68
Timestamp: 2025-06-26T07:37:24.385Z
Learning: In the Bifrost project's MCP configuration handling, empty environment variables should be treated as missing/invalid rather than as valid empty values. The current implementation using `os.Getenv(envKey); envValue != ""` to check for non-empty values is the desired behavior.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#100
File: core/mcp.go:489-490
Timestamp: 2025-06-19T12:38:07.544Z
Learning: In the Bifrost MCP manager (core/mcp.go), the connectToMCPClient method is called during initialization/connection setup, not frequently during runtime. Logging operations like m.logger.Info inside critical sections in this context have negligible performance impact and don't require optimization for lock contention.
transports/bifrost-http/plugins/logging/utils.go (1)
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#144
File: transports/bifrost-http/plugins/logging/utils.go:286-292
Timestamp: 2025-07-08T16:40:59.079Z
Learning: Pratham-Mishra04 prefers to keep simpler error handling patterns when errors are unlikely to occur in practice, such as safety checks in BadgerDB iterations where item.Value() is called on valid items. The user considers the overhead of explicit error handling not worth it in such scenarios.
transports/bifrost-http/ui/_next/static/chunks/app/page-3018cf06890a2414.js (1)
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#144
File: transports/bifrost-http/handlers/websocket.go:44-46
Timestamp: 2025-07-08T15:55:40.453Z
Learning: In the Bifrost HTTP transport WebSocket handler (transports/bifrost-http/handlers/websocket.go), the WebSocket `/ws/logs` endpoint is designed to be used by HTML served on the same port, making it a same-origin connection which reduces the security risk of allowing all origins in the CheckOrigin function.
🧬 Code Graph Analysis (5)
transports/bifrost-http/main.go (1)
transports/bifrost-http/lib/config.go (1)
ClientConfig(11-16)
transports/bifrost-http/handlers/logging.go (1)
transports/bifrost-http/handlers/utils.go (1)
SendJSON(14-22)
transports/bifrost-http/plugins/logging/main.go (1)
core/schemas/logger.go (1)
Logger(18-35)
ui/components/config/core-settings-list.tsx (2)
ui/lib/api.ts (1)
apiService(226-226)ui/components/ui/input.tsx (1)
Input(7-22)
transports/bifrost-http/lib/store.go (6)
transports/bifrost-http/lib/config.go (1)
ClientConfig(11-16)core/schemas/mcp.go (2)
MCPConfig(6-8)MCPClientConfig(11-18)ui/lib/types/config.ts (3)
Key(7-11)MetaConfig(30-49)ModelProvider(4-4)core/schemas/meta/azure.go (1)
AzureMetaConfig(8-12)core/schemas/meta/bedrock.go (1)
BedrockMetaConfig(8-14)core/schemas/meta/vertex.go (1)
VertexMetaConfig(8-12)
🪛 Biome (1.9.4)
transports/bifrost-http/ui/_next/static/chunks/341-25f02d71bd620aa0.js
[error] 1-1: Redundant use strict directive.
The entire contents of JavaScript modules are automatically in strict mode, with no statement needed to initiate it.
Safe fix: Remove the redundant use strict directive.
(lint/suspicious/noRedundantUseStrict)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Change to an optional chain.
Unsafe fix: Change to an optional chain.
(lint/complexity/useOptionalChain)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'a' is never reassigned.
'n' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'a' is never reassigned.
'n' is never reassigned.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
'e' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
'i' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares a variable that is only assigned once.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'let' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'a' is never reassigned.
'i' is never reassigned.
'o' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'a' is never reassigned.
's' is never reassigned.
'i' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'a' is never reassigned.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'a' is never reassigned.
'i' is never reassigned.
'o' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares a variable that is only assigned once.
'l' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'a' is never reassigned.
'n' is never reassigned.
's' is never reassigned.
'i' is never reassigned.
'l' is never reassigned.
'd' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'a' is never reassigned.
's' is never reassigned.
'o' is never reassigned.
'd' is never reassigned.
'c' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'r' is never reassigned.
'n' is never reassigned.
's' is never reassigned.
'i' is never reassigned.
'o' is never reassigned.
'l' is never reassigned.
'd' is never reassigned.
'c' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares a variable that is only assigned once.
'o' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'a' is never reassigned.
's' is never reassigned.
'l' is never reassigned.
'd' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares a variable that is only assigned once.
'i' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'a' is never reassigned.
'n' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'a' is never reassigned.
'o' is never reassigned.
'c' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares a variable that is only assigned once.
'i' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'a' is never reassigned.
'n' is never reassigned.
'i' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
ui/components/config/core-settings-list.tsx
[error] 136-136: Use Number.parseInt instead of the equivalent global.
ES2015 moved some globals into the Number namespace for consistency.
Safe fix: Use Number.parseInt instead.
(lint/style/useNumberNamespace)
[error] 213-213: A form label must be associated with an input.
Consider adding a for or htmlFor attribute to the label element or moving the input element to inside the label element.
(lint/a11y/noLabelWithoutControl)
transports/bifrost-http/ui/_next/static/chunks/app/config/page-afdfa4a22ecb6a17.js
[error] 1-1: Redundant use strict directive.
The entire contents of JavaScript modules are automatically in strict mode, with no statement needed to initiate it.
Safe fix: Remove the redundant use strict directive.
(lint/suspicious/noRedundantUseStrict)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Using this in a static context can be confusing.
this refers to the class.
Unsafe fix: Use the class name instead.
(lint/complexity/noThisInStatic)
[error] 1-1: Using this in a static context can be confusing.
this refers to the class.
Unsafe fix: Use the class name instead.
(lint/complexity/noThisInStatic)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Template literals are preferred over string concatenation.
Unsafe fix: Use a template literal.
(lint/style/useTemplate)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Redundant use strict directive.
The entire contents of JavaScript modules are automatically in strict mode, with no statement needed to initiate it.
Safe fix: Remove the redundant use strict directive.
(lint/suspicious/noRedundantUseStrict)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Redundant use strict directive.
The entire contents of JavaScript modules are automatically in strict mode, with no statement needed to initiate it.
Safe fix: Remove the redundant use strict directive.
(lint/suspicious/noRedundantUseStrict)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
's' is never reassigned.
't' is never reassigned.
'n' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares a variable that is only assigned once.
'v' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
's' is never reassigned.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'A' is never reassigned.
'k' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'e' is never reassigned.
's' is never reassigned.
't' is never reassigned.
'r' is never reassigned.
'i' is never reassigned.
'l' is never reassigned.
'o' is never reassigned.
'c' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'e' is never reassigned.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'd' is never reassigned.
'u' is never reassigned.
'm' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'e' is never reassigned.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'let' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
'h' is never reassigned.
'f' is never reassigned.
'g' is never reassigned.
'k' is never reassigned.
'S' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
'r' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use Number.parseInt instead of the equivalent global.
ES2015 moved some globals into the Number namespace for consistency.
Safe fix: Use Number.parseInt instead.
(lint/style/useNumberNamespace)
[error] 1-1: This let declares a variable that is only assigned once.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use Number.parseInt instead of the equivalent global.
ES2015 moved some globals into the Number namespace for consistency.
Safe fix: Use Number.parseInt instead.
(lint/style/useNumberNamespace)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares a variable that is only assigned once.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
's' is never reassigned.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
's' is never reassigned.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
's' is never reassigned.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
's' is never reassigned.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
's' is never reassigned.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
's' is never reassigned.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
's' is never reassigned.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
's' is never reassigned.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares a variable that is only assigned once.
'W' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'r' is never reassigned.
'i' is never reassigned.
'l' is never reassigned.
'c' is never reassigned.
'd' is never reassigned.
'u' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
'ea' is never reassigned.
'er' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
's' is never reassigned.
't' is never reassigned.
'a' is never reassigned.
'r' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
'i' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
'e' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
'eo' is never reassigned.
'ec' is never reassigned.
'ed' is never reassigned.
'eu' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'n' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
's' is never reassigned.
't' is never reassigned.
'r' is never reassigned.
'i' is never reassigned.
'o' is never reassigned.
'd' is never reassigned.
'm' is never reassigned.
'h' is never reassigned.
'f' is never reassigned.
'v' is never reassigned.
'y' is never reassigned.
'_' is never reassigned.
'w' is never reassigned.
'A' is never reassigned.
'k' is never reassigned.
'S' is never reassigned.
'z' is never reassigned.
'V' is never reassigned.
'q' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'I' is never reassigned.
'R' is never reassigned.
'M' is never reassigned.
'B' is never reassigned.
'D' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'n' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'n' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
'e' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'L' is never reassigned.
'Z' is never reassigned.
'F' is never reassigned.
'U' is never reassigned.
'H' is never reassigned.
'O' is never reassigned.
'$' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
'e' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
'e' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'n' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use Number.parseFloat instead of the equivalent global.
ES2015 moved some globals into the Number namespace for consistency.
Safe fix: Use Number.parseFloat instead.
(lint/style/useNumberNamespace)
[error] 1-1: Use Number.parseInt instead of the equivalent global.
ES2015 moved some globals into the Number namespace for consistency.
Safe fix: Use Number.parseInt instead.
(lint/style/useNumberNamespace)
[error] 1-1: Use Number.parseInt instead of the equivalent global.
ES2015 moved some globals into the Number namespace for consistency.
Safe fix: Use Number.parseInt instead.
(lint/style/useNumberNamespace)
[error] 1-1: Use Number.parseInt instead of the equivalent global.
ES2015 moved some globals into the Number namespace for consistency.
Safe fix: Use Number.parseInt instead.
(lint/style/useNumberNamespace)
[error] 1-1: Use Number.parseInt instead of the equivalent global.
ES2015 moved some globals into the Number namespace for consistency.
Safe fix: Use Number.parseInt instead.
(lint/style/useNumberNamespace)
[error] 1-1: This let declares some variables that are only assigned once.
's' is never reassigned.
't' is never reassigned.
'r' is never reassigned.
'i' is never reassigned.
'c' is never reassigned.
'd' is never reassigned.
'u' is never reassigned.
'm' is never reassigned.
'h' is never reassigned.
'f' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'let' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
's' is never reassigned.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'ej' is never reassigned.
'ef' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'let' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
'd' is never reassigned.
'u' is never reassigned.
'm' is never reassigned.
'x' is never reassigned.
'j' is never reassigned.
'f' is never reassigned.
'g' is never reassigned.
'v' is never reassigned.
'y' is never reassigned.
'_' is never reassigned.
'S' is never reassigned.
'z' is never reassigned.
'P' is never reassigned.
'E' is never reassigned.
'V' is never reassigned.
'q' is never reassigned.
'T' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'let' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
'I' is never reassigned.
'R' is never reassigned.
'M' is never reassigned.
'B' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'n' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
'e' is never reassigned.
's' is never reassigned.
't' is never reassigned.
'r' is never reassigned.
'i' is never reassigned.
'c' is never reassigned.
'd' is never reassigned.
'u' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'e' is never reassigned.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'm' is never reassigned.
'x' is never reassigned.
'f' is never reassigned.
'g' is never reassigned.
'v' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'let' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
'e' is never reassigned.
's' is never reassigned.
't' is never reassigned.
'x' is never reassigned.
'j' is never reassigned.
'f' is never reassigned.
'g' is never reassigned.
'v' is never reassigned.
'y' is never reassigned.
'b' is never reassigned.
'_' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'N' is never reassigned.
'C' is never reassigned.
'w' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'e' is never reassigned.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'e' is never reassigned.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
'e' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares a variable that is only assigned once.
'u' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
's' is never reassigned.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
's' is never reassigned.
't' is never reassigned.
'i' is never reassigned.
'l' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
transports/bifrost-http/ui/_next/static/css/d3f26c86d016c77c.css
[error] 1-1: Unexpected nonstandard direction
You should fix the direction value to follow the syntax.
See MDN web docs for more details.
(lint/correctness/noInvalidDirectionInLinearGradient)
[error] 1-1: Duplicate font names are redundant and unnecessary: Geist
Remove duplicate font names within the property
(lint/suspicious/noDuplicateFontNames)
[error] 1-1: Generic font family missing.
Consider adding a generic font family as a fallback.
For examples and more information, see the MDN Web Docs
(lint/a11y/useGenericFontNames)
[error] 1-1: Duplicate font names are redundant and unnecessary: Geist
Remove duplicate font names within the property
(lint/suspicious/noDuplicateFontNames)
[error] 1-1: Generic font family missing.
Consider adding a generic font family as a fallback.
For examples and more information, see the MDN Web Docs
(lint/a11y/useGenericFontNames)
transports/bifrost-http/ui/_next/static/chunks/app/page-3018cf06890a2414.js
[error] 1-1: Redundant use strict directive.
The entire contents of JavaScript modules are automatically in strict mode, with no statement needed to initiate it.
Safe fix: Remove the redundant use strict directive.
(lint/suspicious/noRedundantUseStrict)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Redundant use strict directive.
The entire contents of JavaScript modules are automatically in strict mode, with no statement needed to initiate it.
Safe fix: Remove the redundant use strict directive.
(lint/suspicious/noRedundantUseStrict)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Change to an optional chain.
Unsafe fix: Change to an optional chain.
(lint/complexity/useOptionalChain)
[error] 1-1: Change to an optional chain.
Unsafe fix: Change to an optional chain.
(lint/complexity/useOptionalChain)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Change to an optional chain.
Unsafe fix: Change to an optional chain.
(lint/complexity/useOptionalChain)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
's' is never reassigned.
'r' is never reassigned.
'd' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
's' is never reassigned.
'a' is never reassigned.
'l' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares a variable that is only assigned once.
'H' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
's' is never reassigned.
'l' is never reassigned.
'o' is never reassigned.
'r' is never reassigned.
'i' is never reassigned.
'd' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'u' is never reassigned.
'm' is never reassigned.
'p' is never reassigned.
'f' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'a' is never reassigned.
'l' is never reassigned.
'o' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
'n' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
's' is never reassigned.
'n' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
's' is never reassigned.
'l' is never reassigned.
'h' is never reassigned.
'x' is never reassigned.
'g' is never reassigned.
'f' is never reassigned.
'j' is never reassigned.
'v' is never reassigned.
'y' is never reassigned.
'N' is never reassigned.
'b' is never reassigned.
'w' is never reassigned.
'_' is never reassigned.
'k' is never reassigned.
'S' is never reassigned.
'A' is never reassigned.
'C' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'e' is never reassigned.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares a variable that is only assigned once.
'K' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'let' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
'y' is never reassigned.
'N' is never reassigned.
'b' is never reassigned.
'w' is never reassigned.
'_' is never reassigned.
'k' is never reassigned.
'S' is never reassigned.
'A' is never reassigned.
'C' is never reassigned.
'L' is never reassigned.
'H' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'T' is never reassigned.
'z' is never reassigned.
'B' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
'e' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'let' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
'Y' is never reassigned.
'J' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'let' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
'd' is never reassigned.
'u' is never reassigned.
'm' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
'p' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
'V' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares a variable that is only assigned once.
'X' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
'ep' is never reassigned.
'eh' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
's' is never reassigned.
'a' is never reassigned.
'l' is never reassigned.
'o' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
'eg' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
's' is never reassigned.
'l' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
'e' is never reassigned.
't' is never reassigned.
's' is never reassigned.
'o' is never reassigned.
'r' is never reassigned.
'i' is never reassigned.
'c' is never reassigned.
'd' is never reassigned.
'u' is never reassigned.
'm' is never reassigned.
'p' is never reassigned.
'h' is never reassigned.
'x' is never reassigned.
'g' is never reassigned.
'f' is never reassigned.
'j' is never reassigned.
'v' is never reassigned.
'y' is never reassigned.
'N' is never reassigned.
'b' is never reassigned.
'w' is never reassigned.
'_' is never reassigned.
'k' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
's' is never reassigned.
'n' is never reassigned.
'l' is never reassigned.
'o' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'e' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'let' instead.
(lint/style/noVar)
[error] 1-1: This let declares a variable that is only assigned once.
'r' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
'n' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'e' is never reassigned.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'S' is never reassigned.
'A' is never reassigned.
'C' is never reassigned.
'L' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'let' instead.
(lint/style/noVar)
[error] 1-1: This let declares a variable that is only assigned once.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)
- GitHub Check: Graphite / mergeability_check
- GitHub Check: Graphite / mergeability_check
🔇 Additional comments (38)
ui/lib/types/config.ts (1)
120-120: LGTM: Well-defined type addition for log queue size configuration.The addition of the optional
log_queue_sizefield to theCoreConfiginterface is properly typed and follows the established naming conventions. This aligns with the backend implementation for configurable logging queue size.ui/app/plugins/page.tsx (1)
357-357: LGTM: Minor UI styling update.The gradient color change from blue to green is a harmless cosmetic improvement that aligns with the broader UI refresh.
ui/components/config/providers-list.tsx (1)
100-100: LGTM: Correct column span fix.The change from
colSpan={5}tocolSpan={6}properly aligns with the table having 6 columns (Provider, Concurrency, Buffer Size, Max Retries, API Keys, Actions), ensuring the "No providers found" message spans the full table width.transports/bifrost-http/main.go (1)
299-299: LGTM: Excellent configuration management improvement.Replacing the hardcoded
LogQueueSize: 1000with the dynamicstore.ClientConfig.LogQueueSizeproperly enables runtime configuration of the log queue size. This change aligns with the broader feature implementation and improves system flexibility.transports/bifrost-http/ui/docs/index.txt (1)
19-20: LGTM: Standard UI asset refresh.The CSS and chunk reference updates are typical of frontend build artifacts being refreshed. These changes ensure the UI loads the correct version of static assets and align with the broader UI modernization effort.
transports/bifrost-http/handlers/logging.go (2)
35-35: LGTM: New route registration follows established patterns.The new route is properly registered alongside other logging routes.
143-147: LGTM: Handler implementation is clean and consistent.The
GetDroppedRequestshandler follows the same pattern as other handlers in the file, using the establishedSendJSONutility and maintaining consistency with the codebase.transports/bifrost-http/handlers/config.go (1)
77-79: LGTM: Configuration update follows established pattern.The
LogQueueSizeconfiguration update is implemented consistently with other configuration parameters. Note that unlikeDropExcessRequests, this change only updates the stored configuration without immediate runtime application, which is appropriate if the log queue size is applied at plugin initialization.transports/bifrost-http/ui/404/index.html (1)
1-122: LGTM: Standard Next.js asset updates and progress bar styles.The CSS stylesheet reference has been updated to a new hash, and inline progress bar styles have been added. These appear to be routine Next.js build output updates with no functional changes to the 404 page logic.
ui/lib/api.ts (1)
96-103: LGTM: API method follows established patterns.The
getDroppedRequestsmethod is implemented consistently with other API methods in the class, using the same error handling pattern and proper TypeScript typing.transports/bifrost-http/ui/index.txt (1)
10-19: LGTM: Standard Next.js build output with updated asset references.The chunk references and CSS stylesheet hashes have been updated, which is typical for Next.js build system asset updates. The structure and format remain consistent with Next.js conventions.
transports/bifrost-http/lib/config.go (1)
12-16: Ignore invalid suggestion:loadClientConfigdoes not exist
- transports/bifrost-http/lib/config.go only defines the
ClientConfigstruct—there is noloadClientConfigfunction to patch.- Default
LogQueueSizeis already initialized in NewConfigStore (transports/bifrost-http/lib/store.go:56–61).- UI input enforces
min="1"in core-settings-list.tsx, and any additional runtime validation should be implemented in the HTTP handler (transports/bifrost-http/handlers/config.go) if needed.No changes required here.
Likely an incorrect or invalid review comment.
transports/bifrost-http/ui/404.html (1)
1-122: Generated asset – no manual review requiredThe diff only swaps hashed asset names and injects build-time CSS; no actionable source changes.
transports/bifrost-http/ui/index.html (1)
1-122: Generated asset – no manual review requiredChanges are build artefacts (hashed CSS/JS chunks). Nothing to review.
transports/bifrost-http/ui/config/index.html (1)
1-122: Generated asset – no manual review requiredStatic asset hashes and chunk names updated; the HTML is generated.
transports/bifrost-http/plugins/logging/main.go (8)
10-10: Good addition for atomic operations.The
sync/atomicimport is correctly added to support thread-safe operations for the dropped requests counter.
29-29: New index type aligns with enhanced search capabilities.The
ObjectIndexconstant supports filtering by request type (chat.completion, text.completion, embedding), which enhances the logging system's search functionality.
133-133: Atomic counter correctly implemented for thread safety.Using
atomic.Int64for the dropped requests counter ensures thread-safe access in the concurrent logging environment.
157-157: Configurable queue size improves flexibility.Replacing the hardcoded queue size with
config.LogQueueSizeallows runtime configuration, which is a significant improvement for operational flexibility.
283-287: UUID generation ensures unique log identifiers.Always generating a UUID upfront guarantees every log entry has a unique identifier, which is essential for log tracking and retrieval.
315-328: Conditional ID overwriting and object field logic is well-implemented.The logic correctly:
- Uses the result ID when available, otherwise keeps the generated UUID
- Sets the object field from the result or falls back to context
- Handles the object field assignment gracefully
362-368: Good defensive programming with context nil check.The nil check for context before accessing chat history prevents potential panics and follows defensive programming practices. Based on the retrieved learnings, this aligns with Pratham-Mishra04's preference for resilient system design.
385-385: Atomic increment correctly implements thread-safe counting.Using
droppedRequests.Add(1)provides thread-safe incrementation of the dropped requests counter, which is essential for accurate metrics in a concurrent environment.transports/bifrost-http/ui/_next/static/css/d3f26c86d016c77c.css (1)
1-1: Compiled Tailwind CSS asset with expected build artifacts.This is a compiled Tailwind CSS v4.1.11 stylesheet. The static analysis warnings about nonstandard directions, duplicate font names, and missing generic font families are typical for compiled CSS assets and don't represent actionable issues for this generated file.
transports/bifrost-http/ui/config/index.txt (2)
10-10: Asset references updated for new configuration UI.The JavaScript chunk references have been updated to support the enhanced configuration UI that includes the new
log_queue_sizeparameter and dropped logs display functionality.
18-19: CSS stylesheet reference updated consistently.The CSS reference has been updated to use the new Tailwind CSS stylesheet (
d3f26c86d016c77c.css), maintaining consistency with the UI refresh across the application.transports/bifrost-http/ui/_next/static/chunks/341-25f02d71bd620aa0.js (1)
1-1: Skip review of generated build artifacts.This is a minified production build file generated by Next.js. Any code review should be performed on the source TypeScript/JavaScript files rather than these build artifacts.
transports/bifrost-http/plugins/logging/utils.go (4)
63-69: Object indexing implementation looks good.The object index creation follows the established pattern for other indexes with proper empty string validation.
106-107: Good improvement using read lock for better concurrency.Switching from
Lock()toRLock()allows multiple concurrent searches, which improves performance under load.
330-332: Error handling approach aligns with your preferences.The simplified error handling for
item.Value()continues processing on error, which is appropriate given the low likelihood of errors in BadgerDB iterations.
827-828: Clean addition of dropped requests metric.The
GetDroppedRequests()method provides thread-safe access to the dropped requests counter.Also applies to: 838-840
transports/bifrost-http/lib/store.go (5)
52-57: Good centralization of default configuration values.Moving default client configuration to a global variable improves maintainability and ensures consistency across the codebase.
93-93: Log message accurately reflects UI capability.
96-96: Consistent use of centralized defaults.Using
DefaultClientConfiginstead of inline struct initialization ensures consistency and makes it easier to update defaults in one place.Also applies to: 128-128
247-330: Excellent implementation of environment variable reference preservation.The enhanced
writeConfigToFilemethod properly restores environment variable references (env.VAR_NAME) when saving configuration, maintaining the dynamic nature of the config. Making this method unexported is appropriate sinceSaveConfigserves as the public interface.Note: The removal of asterisk redaction for actual values (lines 291, 361) is a behavioral change that should be documented in the changelog.
332-368: Well-implemented MCP config restoration logic.The method correctly creates a deep copy of the MCP configuration and restores environment variable references. Good attention to detail with array cloning and nil checks.
transports/bifrost-http/ui/_next/static/chunks/app/page-3018cf06890a2414.js (1)
1-1: Production build looks good!This minified chunk properly implements the new real-time request logging UI with WebSocket support, advanced filtering, and integration examples. The build artifact aligns with the PR objectives for enhanced logging capabilities.
transports/bifrost-http/ui/_next/static/chunks/app/config/page-afdfa4a22ecb6a17.js (1)
1-1: Skip review of minified build output.This is a production build artifact (minified JavaScript). Any code changes should be made in the source files, not in the compiled output.
Pratham-Mishra04
force-pushed
the
07-09-fix_onsave_keys_redact_logging_and_added_configurable_logging_queue_size
branch
2 times, most recently
from
73be514 to
352ebbd
Compare
There was a problem hiding this comment.
Actionable comments posted: 9
🔭 Outside diff range comments (2)
transports/bifrost-http/ui/_next/static/css/d3f26c86d016c77c.css (1)
3300-3350: Duplicate family names confuse the font stack
font-family:"Geist","Geist Fallback"appears twice in multiple rules (e.g..__variable_5cfdac). Browsers stop at the first successful match, so repeating the same name is redundant and flags a Biome warning.-font-family:"Geist","Geist Fallback","Geist","Geist Fallback"; +font-family:"Geist","Geist Fallback";transports/bifrost-http/lib/store.go (1)
247-330: Excellent security enhancement for configuration persistence.The refactored
writeConfigToFilemethod now properly restores environment variable references instead of persisting resolved values. This prevents sensitive data leakage in saved configurations.Consider adding a documentation comment explaining that this method restores env var references for security:
// writeConfigToFile writes the current in-memory configuration back to a JSON file // in the exact same format that LoadFromConfig expects. This enables persistence // of runtime configuration changes with environment variable references restored. // // Security: This method ensures that sensitive values loaded from environment // variables are saved back as env.VAR_NAME references rather than their actual // values, preventing credential leakage in configuration files.
♻️ Duplicate comments (3)
ui/components/config/core-settings-list.tsx (2)
136-136: UseNumber.parseIntfor consistency with ES2015 standards.- const numValue = parseInt(value); + const numValue = Number.parseInt(value);
213-225: Associate the label with its input for accessibility.The label element should be associated with its corresponding input using the
htmlForattribute.- <label className="text-sm font-medium">Log Queue Size</label> + <label htmlFor="log-queue-size" className="text-sm font-medium">Log Queue Size</label>And update the Input component:
<Input + id="log-queue-size" type="number" className="w-24" value={localValues.log_queue_size} onChange={(e) => handleLogQueueSizeChange(e.target.value)} min="1" />transports/bifrost-http/plugins/logging/utils.go (1)
461-509: Consider edge cases in latency range bucket calculation.As previously noted, the current implementation has potential issues when
minLatencyormaxLatencyare close to bucket boundaries. For example, withminLatency=99msandmaxLatency=101ms, the search includes buckets 10 and 100, potentially returning logs with latencies from 10-1000ms.After collecting IDs by bucket, add filtering by actual latency values in the
matchesFiltersmethod to ensure precise range queries.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: ASSERTIVE
Plan: Pro
📒 Files selected for processing (30)
.github/workflows/transport-ci.yml(1 hunks)docs/benchmarks.md(1 hunks)transports/bifrost-http/handlers/config.go(1 hunks)transports/bifrost-http/handlers/logging.go(2 hunks)transports/bifrost-http/lib/config.go(1 hunks)transports/bifrost-http/lib/store.go(6 hunks)transports/bifrost-http/main.go(1 hunks)transports/bifrost-http/plugins/logging/main.go(8 hunks)transports/bifrost-http/plugins/logging/utils.go(8 hunks)transports/bifrost-http/ui/404.html(2 hunks)transports/bifrost-http/ui/404/index.html(2 hunks)transports/bifrost-http/ui/_next/static/chunks/341-25f02d71bd620aa0.js(1 hunks)transports/bifrost-http/ui/_next/static/chunks/341-5aa9f869e119bce4.js(0 hunks)transports/bifrost-http/ui/_next/static/chunks/app/config/page-afdfa4a22ecb6a17.js(1 hunks)transports/bifrost-http/ui/_next/static/chunks/app/config/page-bf3c65256b3fc98b.js(0 hunks)transports/bifrost-http/ui/_next/static/chunks/app/page-3018cf06890a2414.js(1 hunks)transports/bifrost-http/ui/_next/static/chunks/app/page-9c52c1dd03452de9.js(0 hunks)transports/bifrost-http/ui/_next/static/css/0451d03ec40c67fa.css(0 hunks)transports/bifrost-http/ui/_next/static/css/d3f26c86d016c77c.css(1 hunks)transports/bifrost-http/ui/config/index.html(2 hunks)transports/bifrost-http/ui/config/index.txt(1 hunks)transports/bifrost-http/ui/docs/index.txt(1 hunks)transports/bifrost-http/ui/index.html(2 hunks)transports/bifrost-http/ui/index.txt(1 hunks)transports/go.mod(0 hunks)ui/app/plugins/page.tsx(1 hunks)ui/components/config/core-settings-list.tsx(5 hunks)ui/components/config/providers-list.tsx(1 hunks)ui/lib/api.ts(1 hunks)ui/lib/types/config.ts(1 hunks)
💤 Files with no reviewable changes (5)
- transports/go.mod
- transports/bifrost-http/ui/_next/static/chunks/341-5aa9f869e119bce4.js
- transports/bifrost-http/ui/_next/static/css/0451d03ec40c67fa.css
- transports/bifrost-http/ui/_next/static/chunks/app/config/page-bf3c65256b3fc98b.js
- transports/bifrost-http/ui/_next/static/chunks/app/page-9c52c1dd03452de9.js
🧰 Additional context used
🧠 Learnings (16)
📓 Common learnings
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#141
File: core/bifrost.go:198-272
Timestamp: 2025-07-08T18:30:08.221Z
Learning: Pratham-Mishra04 follows a pattern of implementing core functionality first and deferring non-critical improvements (like race condition fixes, optimizations) to later PRs. This is a reasonable development approach that prioritizes getting the main feature working before addressing edge cases.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#103
File: .github/workflows/transport-dependency-update.yml:30-36
Timestamp: 2025-06-19T16:57:25.177Z
Learning: In the bifrost repository, Pratham-Mishra04 prefers to keep GitHub Actions workflows lean and trusts their controlled tagging process for core releases, avoiding unnecessary validation steps that they consider overkill.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#150
File: transports/bifrost-http/lib/store.go:370-466
Timestamp: 2025-07-09T04:58:08.205Z
Learning: Pratham-Mishra04 prefers not to add logging or error handling for unreachable code paths in the Bifrost project. When provider types or similar entities are predefined in the system, defensive programming like logging in default cases is considered unnecessary overhead.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#55
File: core/providers/anthropic.go:358-388
Timestamp: 2025-06-04T05:37:59.699Z
Learning: User Pratham-Mishra04 prefers not to extract small code duplications (around 2 lines) into helper functions, considering the overhead not worth it for such minor repetition.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#102
File: README.md:62-66
Timestamp: 2025-06-19T17:03:03.639Z
Learning: Pratham-Mishra04 prefers using the implicit 'latest' tag for the maximhq/bifrost Docker image rather than pinning to specific versions.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#143
File: core/mcp.go:155-196
Timestamp: 2025-07-08T15:33:47.645Z
Learning: Pratham-Mishra04 prefers not to add explanatory comments for obvious code patterns, such as the unlock/lock strategy around network I/O operations, considering them self-explanatory to experienced developers.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#138
File: docs/usage/go-package/mcp.md:408-412
Timestamp: 2025-07-01T12:40:08.576Z
Learning: Pratham-Mishra04 is okay with keeping bullet list formatting that uses colons after dashes in markdown documentation, even if it triggers linter warnings, preferring functionality over strict formatting rules.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#148
File: transports/bifrost-http/lib/store.go:880-910
Timestamp: 2025-07-08T17:14:21.532Z
Learning: Pratham-Mishra04 prefers resilient system design where missing environment variables for MCP connections should not cause complete system failure. The system should continue processing other MCP connections even when some fail, maintaining partial functionality rather than implementing fail-fast behavior.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#138
File: transports/README.md:26-28
Timestamp: 2025-07-01T12:45:06.906Z
Learning: Pratham-Mishra04 prefers keeping documentation examples simple and concise, trusting users to handle production-specific considerations like version pinning themselves rather than cluttering examples with additional notes.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#148
File: transports/bifrost-http/lib/store.go:1081-1098
Timestamp: 2025-07-08T17:16:50.780Z
Learning: Pratham-Mishra04 prefers practical redaction approaches over theoretical security improvements when the threat model is low-risk, such as admin-only interfaces in the Bifrost project. Fixed-length redaction is acceptable when only trusted administrators will see the redacted values.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#144
File: transports/bifrost-http/plugins/logging/utils.go:286-292
Timestamp: 2025-07-08T16:40:59.079Z
Learning: Pratham-Mishra04 prefers to keep simpler error handling patterns when errors are unlikely to occur in practice, such as safety checks in BadgerDB iterations where item.Value() is called on valid items. The user considers the overhead of explicit error handling not worth it in such scenarios.
docs/benchmarks.md (1)
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#83
File: core/providers/mistral.go:168-170
Timestamp: 2025-06-15T14:24:49.882Z
Learning: In the Bifrost codebase, performance is prioritized over defensive copying for HTTP service operations. Specifically, shallow slice assignments in provider response handling are acceptable due to object pool reset patterns and JSON unmarshaling behavior that minimize practical data corruption risks.
transports/bifrost-http/main.go (2)
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#149
File: transports/bifrost-http/plugins/logging/main.go:0-0
Timestamp: 2025-07-08T18:09:32.114Z
Learning: In the Bifrost HTTP transport logging plugin (transports/bifrost-http/plugins/logging/main.go), the DatabasePath is explicitly set from main.go via a config struct pointing to appDir/logs, so the default value in the NewLoggerPlugin constructor is only used for standalone plugin usage and doesn't affect the main application flow.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#149
File: transports/bifrost-http/main.go:259-261
Timestamp: 2025-07-08T18:20:24.042Z
Learning: In transports/bifrost-http/lib/store.go, the LoadFromConfig method already handles missing config files gracefully by initializing defaults and auto-detecting providers from environment variables. It only returns errors for actual parsing/processing failures, not missing files, making log.Fatalf appropriate in main.go since real errors should terminate the program.
transports/bifrost-http/handlers/logging.go (2)
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#144
File: transports/bifrost-http/handlers/websocket.go:44-46
Timestamp: 2025-07-08T15:55:40.453Z
Learning: In the Bifrost HTTP transport WebSocket handler (transports/bifrost-http/handlers/websocket.go), the WebSocket `/ws/logs` endpoint is designed to be used by HTML served on the same port, making it a same-origin connection which reduces the security risk of allowing all origins in the CheckOrigin function.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#149
File: transports/bifrost-http/plugins/logging/main.go:0-0
Timestamp: 2025-07-08T18:09:32.114Z
Learning: In the Bifrost HTTP transport logging plugin (transports/bifrost-http/plugins/logging/main.go), the DatabasePath is explicitly set from main.go via a config struct pointing to appDir/logs, so the default value in the NewLoggerPlugin constructor is only used for standalone plugin usage and doesn't affect the main application flow.
transports/bifrost-http/handlers/config.go (2)
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#149
File: transports/bifrost-http/main.go:259-261
Timestamp: 2025-07-08T18:20:24.042Z
Learning: In transports/bifrost-http/lib/store.go, the LoadFromConfig method already handles missing config files gracefully by initializing defaults and auto-detecting providers from environment variables. It only returns errors for actual parsing/processing failures, not missing files, making log.Fatalf appropriate in main.go since real errors should terminate the program.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#103
File: .github/workflows/transport-dependency-update.yml:53-75
Timestamp: 2025-06-20T16:21:18.912Z
Learning: In the bifrost repository's transport dependency update workflow, when updating the core dependency to a new version using `go get`, the go.mod and go.sum files will always change in normal operation, making the safety check for changes more of a defensive programming practice rather than handling a common scenario.
.github/workflows/transport-ci.yml (2)
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#103
File: .github/workflows/transport-dependency-update.yml:53-75
Timestamp: 2025-06-20T16:21:18.912Z
Learning: In the bifrost repository's transport dependency update workflow, when updating the core dependency to a new version using `go get`, the go.mod and go.sum files will always change in normal operation, making the safety check for changes more of a defensive programming practice rather than handling a common scenario.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#103
File: .github/workflows/transport-dependency-update.yml:30-36
Timestamp: 2025-06-19T16:57:25.177Z
Learning: In the bifrost repository, Pratham-Mishra04 prefers to keep GitHub Actions workflows lean and trusts their controlled tagging process for core releases, avoiding unnecessary validation steps that they consider overkill.
transports/bifrost-http/ui/index.txt (2)
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#103
File: .github/workflows/transport-dependency-update.yml:53-75
Timestamp: 2025-06-20T16:21:18.912Z
Learning: In the bifrost repository's transport dependency update workflow, when updating the core dependency to a new version using `go get`, the go.mod and go.sum files will always change in normal operation, making the safety check for changes more of a defensive programming practice rather than handling a common scenario.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#54
File: core/schemas/provider.go:148-148
Timestamp: 2025-06-04T03:57:50.981Z
Learning: Breaking changes in the Bifrost codebase are managed by first merging and tagging core schema changes, then updating dependent code references in subsequent steps after the core version is released.
transports/bifrost-http/lib/config.go (3)
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#94
File: core/schemas/bifrost.go:20-23
Timestamp: 2025-06-18T15:16:23.127Z
Learning: In the Bifrost project, BifrostConfig struct is never marshaled/unmarshaled, so serialization tags (json, yaml) are not needed for its fields.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#149
File: transports/bifrost-http/main.go:259-261
Timestamp: 2025-07-08T18:20:24.042Z
Learning: In transports/bifrost-http/lib/store.go, the LoadFromConfig method already handles missing config files gracefully by initializing defaults and auto-detecting providers from environment variables. It only returns errors for actual parsing/processing failures, not missing files, making log.Fatalf appropriate in main.go since real errors should terminate the program.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#144
File: transports/bifrost-http/plugins/logging/utils.go:509-514
Timestamp: 2025-07-08T16:48:25.373Z
Learning: In the Bifrost logging system (transports/bifrost-http/plugins/logging/utils.go), the Content field in message structures is a struct value type, not a pointer, so it will never be nil and doesn't require nil checks. However, ContentStr within Content is a pointer and should be checked for nil.
transports/bifrost-http/ui/config/index.txt (3)
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#103
File: .github/workflows/transport-dependency-update.yml:53-75
Timestamp: 2025-06-20T16:21:18.912Z
Learning: In the bifrost repository's transport dependency update workflow, when updating the core dependency to a new version using `go get`, the go.mod and go.sum files will always change in normal operation, making the safety check for changes more of a defensive programming practice rather than handling a common scenario.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#54
File: core/schemas/provider.go:148-148
Timestamp: 2025-06-04T03:57:50.981Z
Learning: Breaking changes in the Bifrost codebase are managed by first merging and tagging core schema changes, then updating dependent code references in subsequent steps after the core version is released.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#85
File: core/providers/anthropic.go:150-156
Timestamp: 2025-06-15T16:07:53.140Z
Learning: In the Bifrost codebase, constructor functions are allowed to mutate input ProviderConfig objects in-place (e.g., setting default BaseURL values and trimming trailing slashes). This pattern is acceptable and doesn't need to be flagged as a code review issue.
transports/bifrost-http/ui/index.html (2)
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#54
File: core/schemas/provider.go:148-148
Timestamp: 2025-06-04T03:57:50.981Z
Learning: Breaking changes in the Bifrost codebase are managed by first merging and tagging core schema changes, then updating dependent code references in subsequent steps after the core version is released.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#103
File: .github/workflows/transport-dependency-update.yml:53-75
Timestamp: 2025-06-20T16:21:18.912Z
Learning: In the bifrost repository's transport dependency update workflow, when updating the core dependency to a new version using `go get`, the go.mod and go.sum files will always change in normal operation, making the safety check for changes more of a defensive programming practice rather than handling a common scenario.
transports/bifrost-http/plugins/logging/main.go (11)
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#149
File: transports/bifrost-http/plugins/logging/main.go:0-0
Timestamp: 2025-07-08T18:09:32.114Z
Learning: In the Bifrost HTTP transport logging plugin (transports/bifrost-http/plugins/logging/main.go), the DatabasePath is explicitly set from main.go via a config struct pointing to appDir/logs, so the default value in the NewLoggerPlugin constructor is only used for standalone plugin usage and doesn't affect the main application flow.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#79
File: core/bifrost.go:94-103
Timestamp: 2025-06-14T04:06:58.240Z
Learning: In core/bifrost.go, the count parameter in RunPostHooks method is intentionally kept separate from p.executedPreHooks to support circuit breaker plugins that may need to trigger PostHooks for only a subset of executed plugins when detecting failure conditions mid-execution.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#144
File: transports/bifrost-http/plugins/logging/utils.go:509-514
Timestamp: 2025-07-08T16:48:25.373Z
Learning: In the Bifrost logging system (transports/bifrost-http/plugins/logging/utils.go), the Content field in message structures is a struct value type, not a pointer, so it will never be nil and doesn't require nil checks. However, ContentStr within Content is a pointer and should be checked for nil.
Learnt from: connyay
PR: maximhq/bifrost#92
File: core/providers/utils.go:60-64
Timestamp: 2025-06-17T14:04:21.104Z
Learning: The bifrost codebase uses string alias types (like `type ContextKey string`) for context keys consistently across multiple packages including plugins/maxim/main.go and transports/bifrost-http/tracking/plugin.go. This pattern should be maintained for consistency rather than switching to the canonical struct{} approach.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#144
File: transports/bifrost-http/plugins/logging/utils.go:286-292
Timestamp: 2025-07-08T16:40:59.079Z
Learning: Pratham-Mishra04 prefers to keep simpler error handling patterns when errors are unlikely to occur in practice, such as safety checks in BadgerDB iterations where item.Value() is called on valid items. The user considers the overhead of explicit error handling not worth it in such scenarios.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#55
File: core/providers/bedrock.go:443-468
Timestamp: 2025-06-04T09:32:15.826Z
Learning: In core/providers/bedrock.go, for tool call result messages (ModelChatMessageRoleTool), the Content field represents the actual tool call output. A tool result message should only be created when msg.Content is non-nil, as there's no semantic meaning to a tool result without output content.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#55
File: core/providers/bedrock.go:750-791
Timestamp: 2025-06-04T06:09:18.600Z
Learning: In the Bedrock provider, tool result messages maintain their original tool role in the input messages. The remapping from tool role to user role only occurs during message preparation for the Bedrock API request in `prepareChatCompletionMessages`, not in the original input. The `extractToolsFromHistory` function operates on unprocessed input messages where tool results retain their tool role.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#54
File: core/schemas/bifrost.go:46-49
Timestamp: 2025-06-04T09:22:18.123Z
Learning: In core/schemas/bifrost.go, the RequestInput struct uses ChatCompletionInput *[]BifrostMessage (pointer-to-slice) rather than []BifrostMessage to properly represent union type semantics. For text completion requests, ChatCompletionInput should be nil to indicate "no chat payload at all", while for chat completion requests it should be non-nil (even if empty slice). This distinguishes between different request types rather than just empty vs non-empty chat messages.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#65
File: transports/bifrost-http/integrations/utils.go:169-173
Timestamp: 2025-06-09T17:33:52.234Z
Learning: The ChatCompletionRequest method in the Bifrost client follows a contract where the result parameter will never be nil if the error parameter is nil. This means when error checking passes (err == nil), the result is guaranteed to be valid and can be safely used without additional nil checks.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#55
File: core/providers/anthropic.go:526-550
Timestamp: 2025-06-04T09:29:46.287Z
Learning: In core/providers/anthropic.go, the content field in formattedMessages is always of type []interface{} because it's explicitly constructed that way upstream in the prepareAnthropicChatRequest function. Defensive type casting for multiple types is not needed since the type is guaranteed by the construction logic.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#81
File: tests/core-providers/scenarios/end_to_end_tool_calling.go:43-45
Timestamp: 2025-06-16T04:13:55.437Z
Learning: In the Bifrost codebase, errors returned from client methods like ChatCompletionRequest are of type BifrostError, not the standard error interface. For testing these errors, use require.Nilf instead of require.NoErrorf since BifrostError doesn't work with the standard error assertion methods.
transports/bifrost-http/ui/config/index.html (2)
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#54
File: core/schemas/provider.go:148-148
Timestamp: 2025-06-04T03:57:50.981Z
Learning: Breaking changes in the Bifrost codebase are managed by first merging and tagging core schema changes, then updating dependent code references in subsequent steps after the core version is released.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#103
File: .github/workflows/transport-dependency-update.yml:53-75
Timestamp: 2025-06-20T16:21:18.912Z
Learning: In the bifrost repository's transport dependency update workflow, when updating the core dependency to a new version using `go get`, the go.mod and go.sum files will always change in normal operation, making the safety check for changes more of a defensive programming practice rather than handling a common scenario.
transports/bifrost-http/lib/store.go (13)
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#149
File: transports/bifrost-http/main.go:259-261
Timestamp: 2025-07-08T18:20:24.042Z
Learning: In transports/bifrost-http/lib/store.go, the LoadFromConfig method already handles missing config files gracefully by initializing defaults and auto-detecting providers from environment variables. It only returns errors for actual parsing/processing failures, not missing files, making log.Fatalf appropriate in main.go since real errors should terminate the program.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#149
File: transports/bifrost-http/plugins/logging/main.go:0-0
Timestamp: 2025-07-08T18:09:32.114Z
Learning: In the Bifrost HTTP transport logging plugin (transports/bifrost-http/plugins/logging/main.go), the DatabasePath is explicitly set from main.go via a config struct pointing to appDir/logs, so the default value in the NewLoggerPlugin constructor is only used for standalone plugin usage and doesn't affect the main application flow.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#84
File: core/providers/ollama.go:59-61
Timestamp: 2025-06-15T14:34:29.401Z
Learning: The `CheckAndSetDefaults()` method on `*schemas.ProviderConfig` in Go does not return any error - it has a void return type and only sets default values on the configuration struct.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#85
File: core/providers/anthropic.go:150-156
Timestamp: 2025-06-15T16:07:53.140Z
Learning: In the Bifrost codebase, constructor functions are allowed to mutate input ProviderConfig objects in-place (e.g., setting default BaseURL values and trimming trailing slashes). This pattern is acceptable and doesn't need to be flagged as a code review issue.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#131
File: transports/bifrost-http/lib/config.go:35-68
Timestamp: 2025-06-26T07:37:24.385Z
Learning: In the Bifrost project's MCP configuration handling, empty environment variables should be treated as missing/invalid rather than as valid empty values. The current implementation using `os.Getenv(envKey); envValue != ""` to check for non-empty values is the desired behavior.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#55
File: core/providers/anthropic.go:0-0
Timestamp: 2025-06-04T05:44:09.141Z
Learning: For the Anthropic provider in core/providers/anthropic.go, it's acceptable to pass potentially malformed messages with invalid roles because Anthropic's API will return suitable error responses for role issues, eliminating the need for additional validation logging.
Learnt from: connyay
PR: maximhq/bifrost#92
File: core/providers/utils.go:60-64
Timestamp: 2025-06-17T14:04:21.104Z
Learning: The bifrost codebase uses string alias types (like `type ContextKey string`) for context keys consistently across multiple packages including plugins/maxim/main.go and transports/bifrost-http/tracking/plugin.go. This pattern should be maintained for consistency rather than switching to the canonical struct{} approach.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#150
File: transports/bifrost-http/lib/store.go:370-466
Timestamp: 2025-07-09T04:58:08.205Z
Learning: Pratham-Mishra04 prefers not to add logging or error handling for unreachable code paths in the Bifrost project. When provider types or similar entities are predefined in the system, defensive programming like logging in default cases is considered unnecessary overhead.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#89
File: transports/bifrost-http/integrations/genai/types.go:151-155
Timestamp: 2025-06-16T14:45:48.563Z
Learning: In transports/bifrost-http/integrations/genai/types.go, when SystemInstruction has an empty role, the user prefers to let the downstream provider (Google GenAI) handle validation and return errors, rather than implementing validation in the bifrost layer. This represents a design preference for delegating validation to the appropriate service rather than duplicating validation logic in the proxy layer.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#55
File: core/providers/anthropic.go:483-494
Timestamp: 2025-06-04T09:36:27.956Z
Learning: In the Anthropic provider (core/providers/anthropic.go), the user has confirmed through practical experience that the tool_choice parameter should always use an object format with a "type" field (e.g., {"type": "auto"}, {"type": "tool", "name": "function_name"}), even though the official documentation examples sometimes show "auto" as a direct string. The current implementation correctly handles all tool choice types with the object format.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#55
File: core/providers/anthropic.go:526-550
Timestamp: 2025-06-04T09:29:46.287Z
Learning: In core/providers/anthropic.go, the content field in formattedMessages is always of type []interface{} because it's explicitly constructed that way upstream in the prepareAnthropicChatRequest function. Defensive type casting for multiple types is not needed since the type is guaranteed by the construction logic.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#83
File: core/providers/cohere.go:327-335
Timestamp: 2025-06-15T13:46:24.869Z
Learning: For Cohere v1 API in core/providers/cohere.go, the tool_choice parameter formatting uses uppercase strings for the "type" field (e.g., "AUTO", "TOOL") and follows a different structure than initially assumed. The current implementation with strings.ToUpper() for the type field is correct for the v1 API.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#100
File: core/mcp.go:489-490
Timestamp: 2025-06-19T12:38:07.544Z
Learning: In the Bifrost MCP manager (core/mcp.go), the connectToMCPClient method is called during initialization/connection setup, not frequently during runtime. Logging operations like m.logger.Info inside critical sections in this context have negligible performance impact and don't require optimization for lock contention.
transports/bifrost-http/ui/_next/static/chunks/app/config/page-afdfa4a22ecb6a17.js (1)
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#85
File: core/providers/anthropic.go:150-156
Timestamp: 2025-06-15T16:07:53.140Z
Learning: In the Bifrost codebase, constructor functions are allowed to mutate input ProviderConfig objects in-place (e.g., setting default BaseURL values and trimming trailing slashes). This pattern is acceptable and doesn't need to be flagged as a code review issue.
transports/bifrost-http/ui/_next/static/chunks/app/page-3018cf06890a2414.js (1)
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#144
File: transports/bifrost-http/handlers/websocket.go:44-46
Timestamp: 2025-07-08T15:55:40.453Z
Learning: In the Bifrost HTTP transport WebSocket handler (transports/bifrost-http/handlers/websocket.go), the WebSocket `/ws/logs` endpoint is designed to be used by HTML served on the same port, making it a same-origin connection which reduces the security risk of allowing all origins in the CheckOrigin function.
transports/bifrost-http/plugins/logging/utils.go (1)
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#144
File: transports/bifrost-http/plugins/logging/utils.go:286-292
Timestamp: 2025-07-08T16:40:59.079Z
Learning: Pratham-Mishra04 prefers to keep simpler error handling patterns when errors are unlikely to occur in practice, such as safety checks in BadgerDB iterations where item.Value() is called on valid items. The user considers the overhead of explicit error handling not worth it in such scenarios.
🧬 Code Graph Analysis (5)
transports/bifrost-http/main.go (1)
transports/bifrost-http/lib/config.go (1)
ClientConfig(11-16)
transports/bifrost-http/handlers/logging.go (1)
transports/bifrost-http/handlers/utils.go (1)
SendJSON(14-22)
transports/bifrost-http/lib/store.go (6)
transports/bifrost-http/lib/config.go (1)
ClientConfig(11-16)core/schemas/mcp.go (2)
MCPConfig(6-8)MCPClientConfig(11-18)ui/lib/types/config.ts (3)
Key(7-11)MetaConfig(30-49)ModelProvider(4-4)core/schemas/meta/azure.go (1)
AzureMetaConfig(8-12)core/schemas/meta/bedrock.go (1)
BedrockMetaConfig(8-14)core/schemas/meta/vertex.go (1)
VertexMetaConfig(8-12)
ui/components/config/core-settings-list.tsx (2)
ui/lib/api.ts (1)
apiService(226-226)ui/components/ui/input.tsx (1)
Input(7-22)
transports/bifrost-http/plugins/logging/utils.go (1)
transports/bifrost-http/plugins/logging/main.go (9)
IndexPrefix(23-23)ObjectIndex(29-29)LoggerPlugin(123-134)SearchFilters(67-79)PaginationOptions(82-87)SearchResult(90-99)LogEntry(48-64)LatencyIndex(32-32)TokenIndex(33-33)
🪛 LanguageTool
docs/benchmarks.md
[typographical] ~46-~46: To join two clauses or set off examples, consider using an em dash.
Context: ... When using the UI, there is no drop in performance - only memory usage increases due to the a...
(QB_NEW_EN_DASH_RULE_EM)
[grammar] ~46-~46: Use correct spacing
Context: ...es due to the additional UI build being served. --- ## 🎯 Key Performance Highlights - **Perf...
(QB_NEW_EN_OTHER_ERROR_IDS_5)
🪛 Biome (1.9.4)
transports/bifrost-http/ui/_next/static/chunks/341-25f02d71bd620aa0.js
[error] 1-1: Redundant use strict directive.
The entire contents of JavaScript modules are automatically in strict mode, with no statement needed to initiate it.
Safe fix: Remove the redundant use strict directive.
(lint/suspicious/noRedundantUseStrict)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Change to an optional chain.
Unsafe fix: Change to an optional chain.
(lint/complexity/useOptionalChain)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'a' is never reassigned.
'n' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'a' is never reassigned.
'n' is never reassigned.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
'e' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
'i' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares a variable that is only assigned once.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'let' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'a' is never reassigned.
'i' is never reassigned.
'o' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'a' is never reassigned.
's' is never reassigned.
'i' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'a' is never reassigned.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'a' is never reassigned.
'i' is never reassigned.
'o' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares a variable that is only assigned once.
'l' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'a' is never reassigned.
'n' is never reassigned.
's' is never reassigned.
'i' is never reassigned.
'l' is never reassigned.
'd' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'a' is never reassigned.
's' is never reassigned.
'o' is never reassigned.
'd' is never reassigned.
'c' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'r' is never reassigned.
'n' is never reassigned.
's' is never reassigned.
'i' is never reassigned.
'o' is never reassigned.
'l' is never reassigned.
'd' is never reassigned.
'c' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares a variable that is only assigned once.
'o' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'a' is never reassigned.
's' is never reassigned.
'l' is never reassigned.
'd' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares a variable that is only assigned once.
'i' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'a' is never reassigned.
'n' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'a' is never reassigned.
'o' is never reassigned.
'c' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares a variable that is only assigned once.
'i' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'a' is never reassigned.
'n' is never reassigned.
'i' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
transports/bifrost-http/ui/_next/static/css/d3f26c86d016c77c.css
[error] 1-1: Unexpected nonstandard direction
You should fix the direction value to follow the syntax.
See MDN web docs for more details.
(lint/correctness/noInvalidDirectionInLinearGradient)
[error] 1-1: Duplicate font names are redundant and unnecessary: Geist
Remove duplicate font names within the property
(lint/suspicious/noDuplicateFontNames)
[error] 1-1: Generic font family missing.
Consider adding a generic font family as a fallback.
For examples and more information, see the MDN Web Docs
(lint/a11y/useGenericFontNames)
[error] 1-1: Duplicate font names are redundant and unnecessary: Geist
Remove duplicate font names within the property
(lint/suspicious/noDuplicateFontNames)
[error] 1-1: Generic font family missing.
Consider adding a generic font family as a fallback.
For examples and more information, see the MDN Web Docs
(lint/a11y/useGenericFontNames)
ui/components/config/core-settings-list.tsx
[error] 136-136: Use Number.parseInt instead of the equivalent global.
ES2015 moved some globals into the Number namespace for consistency.
Safe fix: Use Number.parseInt instead.
(lint/style/useNumberNamespace)
[error] 213-213: A form label must be associated with an input.
Consider adding a for or htmlFor attribute to the label element or moving the input element to inside the label element.
(lint/a11y/noLabelWithoutControl)
transports/bifrost-http/ui/_next/static/chunks/app/config/page-afdfa4a22ecb6a17.js
[error] 1-1: Redundant use strict directive.
The entire contents of JavaScript modules are automatically in strict mode, with no statement needed to initiate it.
Safe fix: Remove the redundant use strict directive.
(lint/suspicious/noRedundantUseStrict)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Using this in a static context can be confusing.
this refers to the class.
Unsafe fix: Use the class name instead.
(lint/complexity/noThisInStatic)
[error] 1-1: Using this in a static context can be confusing.
this refers to the class.
Unsafe fix: Use the class name instead.
(lint/complexity/noThisInStatic)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Template literals are preferred over string concatenation.
Unsafe fix: Use a template literal.
(lint/style/useTemplate)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Redundant use strict directive.
The entire contents of JavaScript modules are automatically in strict mode, with no statement needed to initiate it.
Safe fix: Remove the redundant use strict directive.
(lint/suspicious/noRedundantUseStrict)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Redundant use strict directive.
The entire contents of JavaScript modules are automatically in strict mode, with no statement needed to initiate it.
Safe fix: Remove the redundant use strict directive.
(lint/suspicious/noRedundantUseStrict)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
's' is never reassigned.
't' is never reassigned.
'n' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares a variable that is only assigned once.
'v' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
's' is never reassigned.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'A' is never reassigned.
'k' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'e' is never reassigned.
's' is never reassigned.
't' is never reassigned.
'r' is never reassigned.
'i' is never reassigned.
'l' is never reassigned.
'o' is never reassigned.
'c' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'e' is never reassigned.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'd' is never reassigned.
'u' is never reassigned.
'm' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'e' is never reassigned.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'let' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
'h' is never reassigned.
'f' is never reassigned.
'g' is never reassigned.
'k' is never reassigned.
'S' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
'r' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use Number.parseInt instead of the equivalent global.
ES2015 moved some globals into the Number namespace for consistency.
Safe fix: Use Number.parseInt instead.
(lint/style/useNumberNamespace)
[error] 1-1: This let declares a variable that is only assigned once.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use Number.parseInt instead of the equivalent global.
ES2015 moved some globals into the Number namespace for consistency.
Safe fix: Use Number.parseInt instead.
(lint/style/useNumberNamespace)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares a variable that is only assigned once.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
's' is never reassigned.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
's' is never reassigned.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
's' is never reassigned.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
's' is never reassigned.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
's' is never reassigned.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
's' is never reassigned.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
's' is never reassigned.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
's' is never reassigned.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares a variable that is only assigned once.
'W' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'r' is never reassigned.
'i' is never reassigned.
'l' is never reassigned.
'c' is never reassigned.
'd' is never reassigned.
'u' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
'ea' is never reassigned.
'er' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
's' is never reassigned.
't' is never reassigned.
'a' is never reassigned.
'r' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
'i' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
'e' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
'eo' is never reassigned.
'ec' is never reassigned.
'ed' is never reassigned.
'eu' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'n' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
's' is never reassigned.
't' is never reassigned.
'r' is never reassigned.
'i' is never reassigned.
'o' is never reassigned.
'd' is never reassigned.
'm' is never reassigned.
'h' is never reassigned.
'f' is never reassigned.
'v' is never reassigned.
'y' is never reassigned.
'_' is never reassigned.
'w' is never reassigned.
'A' is never reassigned.
'k' is never reassigned.
'S' is never reassigned.
'z' is never reassigned.
'V' is never reassigned.
'q' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'I' is never reassigned.
'R' is never reassigned.
'M' is never reassigned.
'B' is never reassigned.
'D' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'n' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'n' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
'e' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'L' is never reassigned.
'Z' is never reassigned.
'F' is never reassigned.
'U' is never reassigned.
'H' is never reassigned.
'O' is never reassigned.
'$' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
'e' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
'e' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'n' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use Number.parseFloat instead of the equivalent global.
ES2015 moved some globals into the Number namespace for consistency.
Safe fix: Use Number.parseFloat instead.
(lint/style/useNumberNamespace)
[error] 1-1: Use Number.parseInt instead of the equivalent global.
ES2015 moved some globals into the Number namespace for consistency.
Safe fix: Use Number.parseInt instead.
(lint/style/useNumberNamespace)
[error] 1-1: Use Number.parseInt instead of the equivalent global.
ES2015 moved some globals into the Number namespace for consistency.
Safe fix: Use Number.parseInt instead.
(lint/style/useNumberNamespace)
[error] 1-1: Use Number.parseInt instead of the equivalent global.
ES2015 moved some globals into the Number namespace for consistency.
Safe fix: Use Number.parseInt instead.
(lint/style/useNumberNamespace)
[error] 1-1: Use Number.parseInt instead of the equivalent global.
ES2015 moved some globals into the Number namespace for consistency.
Safe fix: Use Number.parseInt instead.
(lint/style/useNumberNamespace)
[error] 1-1: This let declares some variables that are only assigned once.
's' is never reassigned.
't' is never reassigned.
'r' is never reassigned.
'i' is never reassigned.
'c' is never reassigned.
'd' is never reassigned.
'u' is never reassigned.
'm' is never reassigned.
'h' is never reassigned.
'f' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'let' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
's' is never reassigned.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'ej' is never reassigned.
'ef' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'let' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
'd' is never reassigned.
'u' is never reassigned.
'm' is never reassigned.
'x' is never reassigned.
'j' is never reassigned.
'f' is never reassigned.
'g' is never reassigned.
'v' is never reassigned.
'y' is never reassigned.
'_' is never reassigned.
'S' is never reassigned.
'z' is never reassigned.
'P' is never reassigned.
'E' is never reassigned.
'V' is never reassigned.
'q' is never reassigned.
'T' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'let' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
'I' is never reassigned.
'R' is never reassigned.
'M' is never reassigned.
'B' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'n' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
'e' is never reassigned.
's' is never reassigned.
't' is never reassigned.
'r' is never reassigned.
'i' is never reassigned.
'c' is never reassigned.
'd' is never reassigned.
'u' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'e' is never reassigned.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'm' is never reassigned.
'x' is never reassigned.
'f' is never reassigned.
'g' is never reassigned.
'v' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'let' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
'e' is never reassigned.
's' is never reassigned.
't' is never reassigned.
'x' is never reassigned.
'j' is never reassigned.
'f' is never reassigned.
'g' is never reassigned.
'v' is never reassigned.
'y' is never reassigned.
'b' is never reassigned.
'_' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'N' is never reassigned.
'C' is never reassigned.
'w' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'e' is never reassigned.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'e' is never reassigned.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
'e' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares a variable that is only assigned once.
'u' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
's' is never reassigned.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
's' is never reassigned.
't' is never reassigned.
'i' is never reassigned.
'l' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
transports/bifrost-http/ui/_next/static/chunks/app/page-3018cf06890a2414.js
[error] 1-1: Redundant use strict directive.
The entire contents of JavaScript modules are automatically in strict mode, with no statement needed to initiate it.
Safe fix: Remove the redundant use strict directive.
(lint/suspicious/noRedundantUseStrict)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Redundant use strict directive.
The entire contents of JavaScript modules are automatically in strict mode, with no statement needed to initiate it.
Safe fix: Remove the redundant use strict directive.
(lint/suspicious/noRedundantUseStrict)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Change to an optional chain.
Unsafe fix: Change to an optional chain.
(lint/complexity/useOptionalChain)
[error] 1-1: Change to an optional chain.
Unsafe fix: Change to an optional chain.
(lint/complexity/useOptionalChain)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Change to an optional chain.
Unsafe fix: Change to an optional chain.
(lint/complexity/useOptionalChain)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
's' is never reassigned.
'r' is never reassigned.
'd' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
's' is never reassigned.
'a' is never reassigned.
'l' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares a variable that is only assigned once.
'H' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
's' is never reassigned.
'l' is never reassigned.
'o' is never reassigned.
'r' is never reassigned.
'i' is never reassigned.
'd' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'u' is never reassigned.
'm' is never reassigned.
'p' is never reassigned.
'f' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'a' is never reassigned.
'l' is never reassigned.
'o' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
'n' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
's' is never reassigned.
'n' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
's' is never reassigned.
'l' is never reassigned.
'h' is never reassigned.
'x' is never reassigned.
'g' is never reassigned.
'f' is never reassigned.
'j' is never reassigned.
'v' is never reassigned.
'y' is never reassigned.
'N' is never reassigned.
'b' is never reassigned.
'w' is never reassigned.
'_' is never reassigned.
'k' is never reassigned.
'S' is never reassigned.
'A' is never reassigned.
'C' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'e' is never reassigned.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares a variable that is only assigned once.
'K' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'let' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
'y' is never reassigned.
'N' is never reassigned.
'b' is never reassigned.
'w' is never reassigned.
'_' is never reassigned.
'k' is never reassigned.
'S' is never reassigned.
'A' is never reassigned.
'C' is never reassigned.
'L' is never reassigned.
'H' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'T' is never reassigned.
'z' is never reassigned.
'B' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
'e' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'let' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
'Y' is never reassigned.
'J' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'let' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
'd' is never reassigned.
'u' is never reassigned.
'm' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
'p' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
'V' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares a variable that is only assigned once.
'X' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
'ep' is never reassigned.
'eh' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
's' is never reassigned.
'a' is never reassigned.
'l' is never reassigned.
'o' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
'eg' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
's' is never reassigned.
'l' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
'e' is never reassigned.
't' is never reassigned.
's' is never reassigned.
'o' is never reassigned.
'r' is never reassigned.
'i' is never reassigned.
'c' is never reassigned.
'd' is never reassigned.
'u' is never reassigned.
'm' is never reassigned.
'p' is never reassigned.
'h' is never reassigned.
'x' is never reassigned.
'g' is never reassigned.
'f' is never reassigned.
'j' is never reassigned.
'v' is never reassigned.
'y' is never reassigned.
'N' is never reassigned.
'b' is never reassigned.
'w' is never reassigned.
'_' is never reassigned.
'k' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
's' is never reassigned.
'n' is never reassigned.
'l' is never reassigned.
'o' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'e' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'let' instead.
(lint/style/noVar)
[error] 1-1: This let declares a variable that is only assigned once.
'r' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
'n' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'e' is never reassigned.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'S' is never reassigned.
'A' is never reassigned.
'C' is never reassigned.
'L' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'let' instead.
(lint/style/noVar)
[error] 1-1: This let declares a variable that is only assigned once.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)
- GitHub Check: Graphite / mergeability_check
- GitHub Check: Graphite / mergeability_check
🔇 Additional comments (25)
.github/workflows/transport-ci.yml (1)
226-226: Good improvement to scope the git add command.Restricting the git add operation to only the
transports/uidirectory is more precise than adding all files and aligns well with the job's specific purpose of updating transport UI files. This reduces the risk of unintended file commits.ui/app/plugins/page.tsx (1)
357-357: LGTM: UI color theme update.The background gradient color change from blue to green is a straightforward cosmetic update that aligns with the broader UI refresh mentioned in the PR.
ui/lib/types/config.ts (1)
120-120: LGTM: Type definition for configurable log queue size.The addition of the optional
log_queue_sizeproperty to theCoreConfiginterface is properly typed and follows the existing naming convention. This aligns with the backend implementation for configurable logging queue functionality.ui/components/config/providers-list.tsx (1)
100-100: Correct fix for table layout.The
colSpanvalue of 6 now properly matches the number of columns in the table header (Provider, Concurrency, Buffer Size, Max Retries, API Keys, Actions), ensuring the "No providers found" message spans the entire table width.transports/bifrost-http/main.go (1)
299-299: LGTM! Good improvement to make log queue size configurable.This change correctly replaces the hardcoded value with a dynamic configuration value, allowing runtime adjustment of the log queue size.
transports/bifrost-http/ui/docs/index.txt (1)
19-20: UI build artifact update - no functional changes.The CSS stylesheet reference is being updated to a new build version. This is expected when the UI is rebuilt.
transports/bifrost-http/handlers/logging.go (1)
35-35: Good addition of the dropped requests endpoint.The new route correctly exposes the dropped requests count for monitoring purposes.
transports/bifrost-http/ui/index.txt (1)
10-10: UI build artifact updates - no functional changes.The JavaScript chunks and CSS stylesheet references are being updated to new build versions, which is expected when the UI is rebuilt.
Also applies to: 18-19
transports/bifrost-http/handlers/config.go (1)
77-80: LGTM! Consistent implementation of LogQueueSize configuration updates.The logic correctly follows the established pattern for runtime configuration updates and enables dynamic adjustment of the log queue size.
ui/lib/api.ts (1)
96-103: LGTM! Clean implementation following established patterns.The new
getDroppedRequestsmethod is correctly implemented and follows the same consistent pattern as other API methods in the class, including proper error handling and return type structure.transports/bifrost-http/ui/404/index.html (1)
1-122: Asset updates look good.The stylesheet reference update and addition of the progress bar CSS component are part of a standard UI build refresh. The inline CSS is well-structured with proper custom properties and animations.
transports/bifrost-http/ui/404.html (1)
1-122: Consistent asset updates across UI files.The stylesheet reference update and progress bar CSS addition are consistent with the broader UI build refresh across all HTML files.
transports/bifrost-http/ui/config/index.html (1)
1-122: UI build refresh with updated assets.The comprehensive asset reference updates (CSS and JS chunks) along with the progress bar CSS addition are part of a standard UI build refresh process.
transports/bifrost-http/lib/config.go (1)
12-15: Clean addition of configurable log queue size.The new
LogQueueSizefield is properly implemented with appropriate naming, JSON tag, and clear documentation. The addition of comments to existing fields also improves code documentation.transports/bifrost-http/ui/index.html (1)
120-130: Two separate<script src="…webpack…">tags: verify you aren’t double-executingThe chunk
webpack-f94117c709bbd3ec.jsis preloaded in the<head>and executed again at the bottom.
Preload + execute is fine, but ensure there isn’t another execution earlier in the async list – double execution of the runtime can break the module graph subtly.transports/bifrost-http/plugins/logging/main.go (3)
283-318: LGTM! Good defensive programming for ID generation.The upfront UUID generation ensures every log entry has a valid ID, even for error cases, while still preserving the result ID when available.
322-328: Good improvement to Object field setting logic.The prioritization of result.Object over context value provides better flexibility while maintaining backwards compatibility.
385-385: Correct use of atomic operations for tracking dropped requests.The atomic increment ensures thread-safe tracking of dropped log entries when the queue is full.
ui/components/config/core-settings-list.tsx (1)
34-44: Well-implemented dropped requests tracking display.The implementation fetches the dropped count on mount and displays it inline with the queue size description, providing valuable feedback to users about system behavior.
Also applies to: 215-217
transports/bifrost-http/plugins/logging/utils.go (3)
63-69: LGTM! Object index creation follows established patterns.The implementation correctly creates an index for the Object field when non-empty, maintaining consistency with other index types.
106-107: Good optimization: Using read lock for search operations.Switching from write lock to read lock improves concurrency by allowing multiple simultaneous search operations.
826-827: Well-implemented interface extension for dropped requests.The
GetDroppedRequestsmethod correctly exposes the atomic counter through the LogManager interface, enabling monitoring of dropped log entries.Also applies to: 838-840
transports/bifrost-http/lib/store.go (2)
52-57: Good centralization of default configuration values.The introduction of
DefaultClientConfigproperly centralizes default values and includes the newLogQueueSizefield. This improves maintainability by having a single source of truth for defaults.
93-93: Accurate log message update.The change from "API" to "UI" correctly reflects that providers can now be added dynamically via the user interface.
transports/bifrost-http/ui/_next/static/chunks/app/config/page-afdfa4a22ecb6a17.js (1)
1-1: Minified frontend code aligns with backend changes.This minified Next.js chunk implements the UI for managing the new
log_queue_sizeconfiguration parameter and displays dropped log counts. The functionality properly integrates with the backend API changes.Note: The static analysis warnings about code style (var usage, const vs let) are not applicable to minified production code.
Pratham-Mishra04
force-pushed
the
07-07-feat_transport_flags_simplified_and_logs_updated
branch
from
535682b to
5ad3df8
Compare
Pratham-Mishra04
force-pushed
the
07-09-fix_onsave_keys_redact_logging_and_added_configurable_logging_queue_size
branch
from
352ebbd to
5c59105
Compare
There was a problem hiding this comment.
Actionable comments posted: 5
🔭 Outside diff range comments (1)
transports/bifrost-http/ui/404/index.html (1)
2-66: Duplicate inline BProgress CSS – extract to shared stylesheetThe full
.bprogressblock (~120 lines) is repeated verbatim in both 404 pages. Embedding large CSS blobs inline:
- Inflates HTML payloads.
- Bypasses browser caching.
- Makes maintenance harder – the two copies can silently diverge.
Move the rules into
bprogress.css(or the main hashed CSS bundle) and<link>it here.
♻️ Duplicate comments (8)
docs/benchmarks.md (1)
46-47: Fix typography issues in the disclaimer.The disclaimer content is valuable, but there are typography issues that need to be addressed as previously noted.
transports/bifrost-http/handlers/logging.go (1)
143-147: Fix the route comment as previously noted.The implementation is correct, but the comment still mentions the wrong route path.
transports/bifrost-http/ui/index.html (1)
1-1: Consider strengthening CSP / SRI for in-lined asset URLsThe updated script tags still lack
integrityandcrossorigin="anonymous"attributes. This security enhancement would help ensure the exact bytes expected are loaded and enable stricter Content-Security-Policy.ui/components/config/core-settings-list.tsx (1)
136-136: UseNumber.parseIntfor consistency with ES2015 standards.- const numValue = Number.parseInt(value); + const numValue = Number.parseInt(value);transports/bifrost-http/plugins/logging/utils.go (2)
330-332: Add actual error logging instead of just a comment.
461-509: Consider edge cases in latency range bucket calculation.transports/bifrost-http/lib/store.go (2)
332-368: Documentation already requested in previous review.
370-466: Documentation already requested in previous review.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: ASSERTIVE
Plan: Pro
📒 Files selected for processing (36)
.github/workflows/transport-ci.yml(1 hunks)core/bifrost.go(1 hunks)docs/benchmarks.md(1 hunks)transports/bifrost-http/handlers/config.go(1 hunks)transports/bifrost-http/handlers/logging.go(2 hunks)transports/bifrost-http/handlers/mcp.go(3 hunks)transports/bifrost-http/handlers/providers.go(3 hunks)transports/bifrost-http/lib/config.go(1 hunks)transports/bifrost-http/lib/store.go(6 hunks)transports/bifrost-http/main.go(1 hunks)transports/bifrost-http/plugins/logging/main.go(8 hunks)transports/bifrost-http/plugins/logging/utils.go(8 hunks)transports/bifrost-http/ui/404.html(2 hunks)transports/bifrost-http/ui/404/index.html(2 hunks)transports/bifrost-http/ui/_next/static/chunks/273-9756261fec6bc01b.js(1 hunks)transports/bifrost-http/ui/_next/static/chunks/529-26467b76604e8781.js(1 hunks)transports/bifrost-http/ui/_next/static/chunks/678-56244c2aeff7b5e2.js(1 hunks)transports/bifrost-http/ui/_next/static/chunks/812-4eac91fa641b7ecf.js(1 hunks)transports/bifrost-http/ui/_next/static/chunks/app/config/page-400ac111d2c44d93.js(1 hunks)transports/bifrost-http/ui/_next/static/chunks/app/layout-188bea908cf68435.js(1 hunks)transports/bifrost-http/ui/_next/static/chunks/app/page-26aa3339d9cf36ab.js(1 hunks)transports/bifrost-http/ui/_next/static/css/04f1137b8e39b139.css(1 hunks)transports/bifrost-http/ui/config/index.html(2 hunks)transports/bifrost-http/ui/config/index.txt(1 hunks)transports/bifrost-http/ui/docs/index.txt(2 hunks)transports/bifrost-http/ui/index.html(2 hunks)transports/bifrost-http/ui/index.txt(1 hunks)transports/go.mod(0 hunks)ui/app/config/page.tsx(2 hunks)ui/app/docs/page.tsx(1 hunks)ui/app/layout.tsx(1 hunks)ui/app/plugins/page.tsx(2 hunks)ui/components/config/core-settings-list.tsx(8 hunks)ui/components/config/providers-list.tsx(1 hunks)ui/lib/api.ts(1 hunks)ui/lib/types/config.ts(1 hunks)
💤 Files with no reviewable changes (1)
- transports/go.mod
🧰 Additional context used
🧠 Learnings (17)
📓 Common learnings
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#141
File: core/bifrost.go:198-272
Timestamp: 2025-07-08T18:30:08.258Z
Learning: Pratham-Mishra04 follows a pattern of implementing core functionality first and deferring non-critical improvements (like race condition fixes, optimizations) to later PRs. This is a reasonable development approach that prioritizes getting the main feature working before addressing edge cases.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#103
File: .github/workflows/transport-dependency-update.yml:30-36
Timestamp: 2025-06-19T16:57:25.177Z
Learning: In the bifrost repository, Pratham-Mishra04 prefers to keep GitHub Actions workflows lean and trusts their controlled tagging process for core releases, avoiding unnecessary validation steps that they consider overkill.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#150
File: transports/bifrost-http/lib/store.go:370-466
Timestamp: 2025-07-09T04:58:08.229Z
Learning: Pratham-Mishra04 prefers not to add logging or error handling for unreachable code paths in the Bifrost project. When provider types or similar entities are predefined in the system, defensive programming like logging in default cases is considered unnecessary overhead.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#54
File: core/schemas/provider.go:148-148
Timestamp: 2025-06-04T03:57:50.981Z
Learning: Breaking changes in the Bifrost codebase are managed by first merging and tagging core schema changes, then updating dependent code references in subsequent steps after the core version is released.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#84
File: transports/bifrost-http/main.go:2-2
Timestamp: 2025-06-15T16:05:13.489Z
Learning: For the Bifrost project, HTTP transport integration routers for new providers (like Mistral and Ollama) are implemented in separate PRs from the core provider support, following a focused PR strategy.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#144
File: transports/bifrost-http/handlers/websocket.go:44-46
Timestamp: 2025-07-08T15:55:40.478Z
Learning: In the Bifrost HTTP transport WebSocket handler (transports/bifrost-http/handlers/websocket.go), the WebSocket `/ws/logs` endpoint is designed to be used by HTML served on the same port, making it a same-origin connection which reduces the security risk of allowing all origins in the CheckOrigin function.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#63
File: transports/bifrost-http/integrations/openai/router.go:0-0
Timestamp: 2025-06-09T14:03:34.227Z
Learning: In the Bifrost HTTP transport layer (transports/bifrost-http/integrations/), request validation like checking for empty messages should be handled by the provider rather than at the transport layer. The transport layer should forward requests to Bifrost core/providers for validation.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#103
File: .github/workflows/transport-dependency-update.yml:53-75
Timestamp: 2025-06-20T16:21:18.912Z
Learning: In the bifrost repository's transport dependency update workflow, when updating the core dependency to a new version using `go get`, the go.mod and go.sum files will always change in normal operation, making the safety check for changes more of a defensive programming practice rather than handling a common scenario.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#144
File: transports/bifrost-http/handlers/websocket.go:104-114
Timestamp: 2025-07-08T15:52:07.907Z
Learning: Pratham-Mishra04 considers WebSocket broadcast lock contention optimization non-critical in the Bifrost HTTP transport. They prefer to keep the simpler implementation over optimizing lock duration during network I/O operations when the performance impact is not significant.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#55
File: core/providers/anthropic.go:358-388
Timestamp: 2025-06-04T05:37:59.699Z
Learning: User Pratham-Mishra04 prefers not to extract small code duplications (around 2 lines) into helper functions, considering the overhead not worth it for such minor repetition.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#102
File: README.md:62-66
Timestamp: 2025-06-19T17:03:03.639Z
Learning: Pratham-Mishra04 prefers using the implicit 'latest' tag for the maximhq/bifrost Docker image rather than pinning to specific versions.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#143
File: core/mcp.go:155-196
Timestamp: 2025-07-08T15:33:47.698Z
Learning: Pratham-Mishra04 prefers not to add explanatory comments for obvious code patterns, such as the unlock/lock strategy around network I/O operations, considering them self-explanatory to experienced developers.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#138
File: docs/usage/go-package/mcp.md:408-412
Timestamp: 2025-07-01T12:40:08.576Z
Learning: Pratham-Mishra04 is okay with keeping bullet list formatting that uses colons after dashes in markdown documentation, even if it triggers linter warnings, preferring functionality over strict formatting rules.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#148
File: transports/bifrost-http/lib/store.go:880-910
Timestamp: 2025-07-08T17:14:21.544Z
Learning: Pratham-Mishra04 prefers resilient system design where missing environment variables for MCP connections should not cause complete system failure. The system should continue processing other MCP connections even when some fail, maintaining partial functionality rather than implementing fail-fast behavior.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#138
File: transports/README.md:26-28
Timestamp: 2025-07-01T12:45:06.906Z
Learning: Pratham-Mishra04 prefers keeping documentation examples simple and concise, trusting users to handle production-specific considerations like version pinning themselves rather than cluttering examples with additional notes.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#148
File: transports/bifrost-http/lib/store.go:1081-1098
Timestamp: 2025-07-08T17:16:50.811Z
Learning: Pratham-Mishra04 prefers practical redaction approaches over theoretical security improvements when the threat model is low-risk, such as admin-only interfaces in the Bifrost project. Fixed-length redaction is acceptable when only trusted administrators will see the redacted values.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#144
File: transports/bifrost-http/plugins/logging/utils.go:286-292
Timestamp: 2025-07-08T16:40:59.098Z
Learning: Pratham-Mishra04 prefers to keep simpler error handling patterns when errors are unlikely to occur in practice, such as safety checks in BadgerDB iterations where item.Value() is called on valid items. The user considers the overhead of explicit error handling not worth it in such scenarios.
docs/benchmarks.md (2)
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#138
File: docs/usage/go-package/mcp.md:408-412
Timestamp: 2025-07-01T12:40:08.576Z
Learning: Pratham-Mishra04 is okay with keeping bullet list formatting that uses colons after dashes in markdown documentation, even if it triggers linter warnings, preferring functionality over strict formatting rules.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#83
File: core/providers/mistral.go:168-170
Timestamp: 2025-06-15T14:24:49.882Z
Learning: In the Bifrost codebase, performance is prioritized over defensive copying for HTTP service operations. Specifically, shallow slice assignments in provider response handling are acceptable due to object pool reset patterns and JSON unmarshaling behavior that minimize practical data corruption risks.
transports/bifrost-http/main.go (2)
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#149
File: transports/bifrost-http/plugins/logging/main.go:0-0
Timestamp: 2025-07-08T18:09:32.147Z
Learning: In the Bifrost HTTP transport logging plugin (transports/bifrost-http/plugins/logging/main.go), the DatabasePath is explicitly set from main.go via a config struct pointing to appDir/logs, so the default value in the NewLoggerPlugin constructor is only used for standalone plugin usage and doesn't affect the main application flow.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#149
File: transports/bifrost-http/main.go:259-261
Timestamp: 2025-07-08T18:20:24.086Z
Learning: In transports/bifrost-http/lib/store.go, the LoadFromConfig method already handles missing config files gracefully by initializing defaults and auto-detecting providers from environment variables. It only returns errors for actual parsing/processing failures, not missing files, making log.Fatalf appropriate in main.go since real errors should terminate the program.
.github/workflows/transport-ci.yml (1)
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#103
File: .github/workflows/transport-dependency-update.yml:53-75
Timestamp: 2025-06-20T16:21:18.912Z
Learning: In the bifrost repository's transport dependency update workflow, when updating the core dependency to a new version using `go get`, the go.mod and go.sum files will always change in normal operation, making the safety check for changes more of a defensive programming practice rather than handling a common scenario.
transports/bifrost-http/handlers/logging.go (5)
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#144
File: transports/bifrost-http/handlers/websocket.go:44-46
Timestamp: 2025-07-08T15:55:40.478Z
Learning: In the Bifrost HTTP transport WebSocket handler (transports/bifrost-http/handlers/websocket.go), the WebSocket `/ws/logs` endpoint is designed to be used by HTML served on the same port, making it a same-origin connection which reduces the security risk of allowing all origins in the CheckOrigin function.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#149
File: transports/bifrost-http/plugins/logging/main.go:0-0
Timestamp: 2025-07-08T18:09:32.147Z
Learning: In the Bifrost HTTP transport logging plugin (transports/bifrost-http/plugins/logging/main.go), the DatabasePath is explicitly set from main.go via a config struct pointing to appDir/logs, so the default value in the NewLoggerPlugin constructor is only used for standalone plugin usage and doesn't affect the main application flow.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#149
File: transports/bifrost-http/main.go:259-261
Timestamp: 2025-07-08T18:20:24.086Z
Learning: In transports/bifrost-http/lib/store.go, the LoadFromConfig method already handles missing config files gracefully by initializing defaults and auto-detecting providers from environment variables. It only returns errors for actual parsing/processing failures, not missing files, making log.Fatalf appropriate in main.go since real errors should terminate the program.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#67
File: transports/bifrost-http/integrations/anthropic/router.go:26-34
Timestamp: 2025-06-10T11:19:29.604Z
Learning: The Generic router in transports/bifrost-http/integrations/utils.go already handles nil pointers from RequestConverter functions. When a RequestConverter returns a nil *schemas.BifrostRequest, the Generic router automatically returns an HTTP 400 error with "Invalid request" message, making additional nil checks in individual router implementations redundant.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#67
File: transports/bifrost-http/integrations/anthropic/router.go:26-34
Timestamp: 2025-06-10T11:19:29.604Z
Learning: The Generic router in transports/bifrost-http/integrations/utils.go already handles nil pointers from RequestConverter functions. When a RequestConverter returns a nil *schemas.BifrostRequest, the Generic router automatically returns an HTTP 400 error, making additional nil checks in individual router implementations redundant.
transports/bifrost-http/handlers/mcp.go (3)
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#100
File: core/mcp.go:489-490
Timestamp: 2025-06-19T12:38:07.544Z
Learning: In the Bifrost MCP manager (core/mcp.go), the connectToMCPClient method is called during initialization/connection setup, not frequently during runtime. Logging operations like m.logger.Info inside critical sections in this context have negligible performance impact and don't require optimization for lock contention.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#149
File: transports/bifrost-http/main.go:259-261
Timestamp: 2025-07-08T18:20:24.086Z
Learning: In transports/bifrost-http/lib/store.go, the LoadFromConfig method already handles missing config files gracefully by initializing defaults and auto-detecting providers from environment variables. It only returns errors for actual parsing/processing failures, not missing files, making log.Fatalf appropriate in main.go since real errors should terminate the program.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#131
File: transports/bifrost-http/lib/config.go:35-68
Timestamp: 2025-06-26T07:37:24.385Z
Learning: In the Bifrost project's MCP configuration handling, empty environment variables should be treated as missing/invalid rather than as valid empty values. The current implementation using `os.Getenv(envKey); envValue != ""` to check for non-empty values is the desired behavior.
transports/bifrost-http/plugins/logging/main.go (6)
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#149
File: transports/bifrost-http/plugins/logging/main.go:0-0
Timestamp: 2025-07-08T18:09:32.147Z
Learning: In the Bifrost HTTP transport logging plugin (transports/bifrost-http/plugins/logging/main.go), the DatabasePath is explicitly set from main.go via a config struct pointing to appDir/logs, so the default value in the NewLoggerPlugin constructor is only used for standalone plugin usage and doesn't affect the main application flow.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#79
File: core/bifrost.go:94-103
Timestamp: 2025-06-14T04:06:58.240Z
Learning: In core/bifrost.go, the count parameter in RunPostHooks method is intentionally kept separate from p.executedPreHooks to support circuit breaker plugins that may need to trigger PostHooks for only a subset of executed plugins when detecting failure conditions mid-execution.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#144
File: transports/bifrost-http/plugins/logging/utils.go:509-514
Timestamp: 2025-07-08T16:48:25.386Z
Learning: In the Bifrost logging system (transports/bifrost-http/plugins/logging/utils.go), the Content field in message structures is a struct value type, not a pointer, so it will never be nil and doesn't require nil checks. However, ContentStr within Content is a pointer and should be checked for nil.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#144
File: transports/bifrost-http/plugins/logging/utils.go:286-292
Timestamp: 2025-07-08T16:40:59.098Z
Learning: Pratham-Mishra04 prefers to keep simpler error handling patterns when errors are unlikely to occur in practice, such as safety checks in BadgerDB iterations where item.Value() is called on valid items. The user considers the overhead of explicit error handling not worth it in such scenarios.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#55
File: core/providers/bedrock.go:443-468
Timestamp: 2025-06-04T09:32:15.826Z
Learning: In core/providers/bedrock.go, for tool call result messages (ModelChatMessageRoleTool), the Content field represents the actual tool call output. A tool result message should only be created when msg.Content is non-nil, as there's no semantic meaning to a tool result without output content.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#55
File: core/providers/bedrock.go:750-791
Timestamp: 2025-06-04T06:09:18.600Z
Learning: In the Bedrock provider, tool result messages maintain their original tool role in the input messages. The remapping from tool role to user role only occurs during message preparation for the Bedrock API request in `prepareChatCompletionMessages`, not in the original input. The `extractToolsFromHistory` function operates on unprocessed input messages where tool results retain their tool role.
transports/bifrost-http/handlers/providers.go (6)
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#149
File: transports/bifrost-http/main.go:259-261
Timestamp: 2025-07-08T18:20:24.086Z
Learning: In transports/bifrost-http/lib/store.go, the LoadFromConfig method already handles missing config files gracefully by initializing defaults and auto-detecting providers from environment variables. It only returns errors for actual parsing/processing failures, not missing files, making log.Fatalf appropriate in main.go since real errors should terminate the program.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#85
File: core/providers/anthropic.go:150-156
Timestamp: 2025-06-15T16:07:53.140Z
Learning: In the Bifrost codebase, constructor functions are allowed to mutate input ProviderConfig objects in-place (e.g., setting default BaseURL values and trimming trailing slashes). This pattern is acceptable and doesn't need to be flagged as a code review issue.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#150
File: transports/bifrost-http/lib/store.go:370-466
Timestamp: 2025-07-09T06:55:21.997Z
Learning: In the Bifrost project's ConfigStore, different functions handle sensitive values differently based on their use cases. The `restoreMetaConfigEnvVars` function preserves actual values without redaction when writing config back to file for round-trip fidelity, while `GetProviderConfigRedacted` redacts sensitive values for external API responses for security purposes. This different handling is intentional and based on the specific context where each function is used.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#84
File: core/providers/ollama.go:59-61
Timestamp: 2025-06-15T14:34:29.401Z
Learning: The `CheckAndSetDefaults()` method on `*schemas.ProviderConfig` in Go does not return any error - it has a void return type and only sets default values on the configuration struct.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#103
File: .github/workflows/transport-dependency-update.yml:53-75
Timestamp: 2025-06-20T16:21:18.912Z
Learning: In the bifrost repository's transport dependency update workflow, when updating the core dependency to a new version using `go get`, the go.mod and go.sum files will always change in normal operation, making the safety check for changes more of a defensive programming practice rather than handling a common scenario.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#83
File: core/providers/mistral.go:168-170
Timestamp: 2025-06-15T14:24:49.882Z
Learning: In the Bifrost codebase, performance is prioritized over defensive copying for HTTP service operations. Specifically, shallow slice assignments in provider response handling are acceptable due to object pool reset patterns and JSON unmarshaling behavior that minimize practical data corruption risks.
transports/bifrost-http/ui/docs/index.txt (2)
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#54
File: core/schemas/provider.go:148-148
Timestamp: 2025-06-04T03:57:50.981Z
Learning: Breaking changes in the Bifrost codebase are managed by first merging and tagging core schema changes, then updating dependent code references in subsequent steps after the core version is released.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#103
File: .github/workflows/transport-dependency-update.yml:53-75
Timestamp: 2025-06-20T16:21:18.912Z
Learning: In the bifrost repository's transport dependency update workflow, when updating the core dependency to a new version using `go get`, the go.mod and go.sum files will always change in normal operation, making the safety check for changes more of a defensive programming practice rather than handling a common scenario.
transports/bifrost-http/lib/config.go (3)
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#94
File: core/schemas/bifrost.go:20-23
Timestamp: 2025-06-18T15:16:23.127Z
Learning: In the Bifrost project, BifrostConfig struct is never marshaled/unmarshaled, so serialization tags (json, yaml) are not needed for its fields.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#149
File: transports/bifrost-http/main.go:259-261
Timestamp: 2025-07-08T18:20:24.086Z
Learning: In transports/bifrost-http/lib/store.go, the LoadFromConfig method already handles missing config files gracefully by initializing defaults and auto-detecting providers from environment variables. It only returns errors for actual parsing/processing failures, not missing files, making log.Fatalf appropriate in main.go since real errors should terminate the program.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#144
File: transports/bifrost-http/plugins/logging/utils.go:509-514
Timestamp: 2025-07-08T16:48:25.386Z
Learning: In the Bifrost logging system (transports/bifrost-http/plugins/logging/utils.go), the Content field in message structures is a struct value type, not a pointer, so it will never be nil and doesn't require nil checks. However, ContentStr within Content is a pointer and should be checked for nil.
transports/bifrost-http/ui/index.html (2)
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#54
File: core/schemas/provider.go:148-148
Timestamp: 2025-06-04T03:57:50.981Z
Learning: Breaking changes in the Bifrost codebase are managed by first merging and tagging core schema changes, then updating dependent code references in subsequent steps after the core version is released.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#103
File: .github/workflows/transport-dependency-update.yml:53-75
Timestamp: 2025-06-20T16:21:18.912Z
Learning: In the bifrost repository's transport dependency update workflow, when updating the core dependency to a new version using `go get`, the go.mod and go.sum files will always change in normal operation, making the safety check for changes more of a defensive programming practice rather than handling a common scenario.
transports/bifrost-http/ui/config/index.txt (3)
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#103
File: .github/workflows/transport-dependency-update.yml:53-75
Timestamp: 2025-06-20T16:21:18.912Z
Learning: In the bifrost repository's transport dependency update workflow, when updating the core dependency to a new version using `go get`, the go.mod and go.sum files will always change in normal operation, making the safety check for changes more of a defensive programming practice rather than handling a common scenario.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#54
File: core/schemas/provider.go:148-148
Timestamp: 2025-06-04T03:57:50.981Z
Learning: Breaking changes in the Bifrost codebase are managed by first merging and tagging core schema changes, then updating dependent code references in subsequent steps after the core version is released.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#85
File: core/providers/anthropic.go:150-156
Timestamp: 2025-06-15T16:07:53.140Z
Learning: In the Bifrost codebase, constructor functions are allowed to mutate input ProviderConfig objects in-place (e.g., setting default BaseURL values and trimming trailing slashes). This pattern is acceptable and doesn't need to be flagged as a code review issue.
transports/bifrost-http/handlers/config.go (4)
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#67
File: transports/bifrost-http/integrations/anthropic/router.go:26-34
Timestamp: 2025-06-10T11:19:29.604Z
Learning: The Generic router in transports/bifrost-http/integrations/utils.go already handles nil pointers from RequestConverter functions. When a RequestConverter returns a nil *schemas.BifrostRequest, the Generic router automatically returns an HTTP 400 error, making additional nil checks in individual router implementations redundant.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#67
File: transports/bifrost-http/integrations/anthropic/router.go:26-34
Timestamp: 2025-06-10T11:19:29.604Z
Learning: The Generic router in transports/bifrost-http/integrations/utils.go already handles nil pointers from RequestConverter functions. When a RequestConverter returns a nil *schemas.BifrostRequest, the Generic router automatically returns an HTTP 400 error with "Invalid request" message, making additional nil checks in individual router implementations redundant.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#149
File: transports/bifrost-http/main.go:259-261
Timestamp: 2025-07-08T18:20:24.086Z
Learning: In transports/bifrost-http/lib/store.go, the LoadFromConfig method already handles missing config files gracefully by initializing defaults and auto-detecting providers from environment variables. It only returns errors for actual parsing/processing failures, not missing files, making log.Fatalf appropriate in main.go since real errors should terminate the program.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#65
File: transports/bifrost-http/integrations/anthropic/router.go:19-33
Timestamp: 2025-06-09T16:46:32.018Z
Learning: In the GenericRouter (transports/bifrost-http/integrations), ResponseFunc is not called if the BifrostResponse parameter is nil, providing built-in protection against nil response marshaling.
transports/bifrost-http/lib/store.go (16)
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#150
File: transports/bifrost-http/lib/store.go:370-466
Timestamp: 2025-07-09T04:58:08.229Z
Learning: Pratham-Mishra04 prefers not to add logging or error handling for unreachable code paths in the Bifrost project. When provider types or similar entities are predefined in the system, defensive programming like logging in default cases is considered unnecessary overhead.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#85
File: core/providers/anthropic.go:150-156
Timestamp: 2025-06-15T16:07:53.140Z
Learning: In the Bifrost codebase, constructor functions are allowed to mutate input ProviderConfig objects in-place (e.g., setting default BaseURL values and trimming trailing slashes). This pattern is acceptable and doesn't need to be flagged as a code review issue.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#103
File: .github/workflows/transport-dependency-update.yml:30-36
Timestamp: 2025-06-19T16:57:25.177Z
Learning: In the bifrost repository, Pratham-Mishra04 prefers to keep GitHub Actions workflows lean and trusts their controlled tagging process for core releases, avoiding unnecessary validation steps that they consider overkill.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#141
File: core/bifrost.go:198-272
Timestamp: 2025-07-08T18:30:08.258Z
Learning: Pratham-Mishra04 follows a pattern of implementing core functionality first and deferring non-critical improvements (like race condition fixes, optimizations) to later PRs. This is a reasonable development approach that prioritizes getting the main feature working before addressing edge cases.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#148
File: transports/bifrost-http/lib/store.go:880-910
Timestamp: 2025-07-08T17:14:21.544Z
Learning: Pratham-Mishra04 prefers resilient system design where missing environment variables for MCP connections should not cause complete system failure. The system should continue processing other MCP connections even when some fail, maintaining partial functionality rather than implementing fail-fast behavior.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#83
File: core/providers/mistral.go:168-170
Timestamp: 2025-06-15T14:24:49.882Z
Learning: In the Bifrost codebase, performance is prioritized over defensive copying for HTTP service operations. Specifically, shallow slice assignments in provider response handling are acceptable due to object pool reset patterns and JSON unmarshaling behavior that minimize practical data corruption risks.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#89
File: transports/bifrost-http/integrations/genai/types.go:151-155
Timestamp: 2025-06-16T14:45:48.563Z
Learning: In transports/bifrost-http/integrations/genai/types.go, when SystemInstruction has an empty role, the user prefers to let the downstream provider (Google GenAI) handle validation and return errors, rather than implementing validation in the bifrost layer. This represents a design preference for delegating validation to the appropriate service rather than duplicating validation logic in the proxy layer.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#63
File: transports/bifrost-http/integrations/openai/router.go:0-0
Timestamp: 2025-06-09T14:03:34.227Z
Learning: In the Bifrost HTTP transport layer (transports/bifrost-http/integrations/), request validation like checking for empty messages should be handled by the provider rather than at the transport layer. The transport layer should forward requests to Bifrost core/providers for validation.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#144
File: transports/bifrost-http/plugins/logging/utils.go:286-292
Timestamp: 2025-07-08T16:40:59.098Z
Learning: Pratham-Mishra04 prefers to keep simpler error handling patterns when errors are unlikely to occur in practice, such as safety checks in BadgerDB iterations where item.Value() is called on valid items. The user considers the overhead of explicit error handling not worth it in such scenarios.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#145
File: transports/bifrost-http/main.go:124-128
Timestamp: 2025-07-08T17:31:44.662Z
Learning: Pratham-Mishra04 prefers to keep the CORS middleware simple in the Bifrost HTTP transport (transports/bifrost-http/main.go) rather than adding port validation for localhost origins, considering the current implementation sufficient for the intended use case.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#131
File: transports/bifrost-http/lib/config.go:35-68
Timestamp: 2025-06-26T07:37:24.385Z
Learning: In the Bifrost project's MCP configuration handling, empty environment variables should be treated as missing/invalid rather than as valid empty values. The current implementation using `os.Getenv(envKey); envValue != ""` to check for non-empty values is the desired behavior.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#100
File: core/mcp.go:489-490
Timestamp: 2025-06-19T12:38:07.544Z
Learning: In the Bifrost MCP manager (core/mcp.go), the connectToMCPClient method is called during initialization/connection setup, not frequently during runtime. Logging operations like m.logger.Info inside critical sections in this context have negligible performance impact and don't require optimization for lock contention.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#149
File: transports/bifrost-http/main.go:259-261
Timestamp: 2025-07-08T18:20:24.086Z
Learning: In transports/bifrost-http/lib/store.go, the LoadFromConfig method already handles missing config files gracefully by initializing defaults and auto-detecting providers from environment variables. It only returns errors for actual parsing/processing failures, not missing files, making log.Fatalf appropriate in main.go since real errors should terminate the program.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#84
File: core/providers/ollama.go:59-61
Timestamp: 2025-06-15T14:34:29.401Z
Learning: The `CheckAndSetDefaults()` method on `*schemas.ProviderConfig` in Go does not return any error - it has a void return type and only sets default values on the configuration struct.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#149
File: transports/bifrost-http/plugins/logging/main.go:0-0
Timestamp: 2025-07-08T18:09:32.147Z
Learning: In the Bifrost HTTP transport logging plugin (transports/bifrost-http/plugins/logging/main.go), the DatabasePath is explicitly set from main.go via a config struct pointing to appDir/logs, so the default value in the NewLoggerPlugin constructor is only used for standalone plugin usage and doesn't affect the main application flow.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#150
File: transports/bifrost-http/lib/store.go:370-466
Timestamp: 2025-07-09T06:55:21.997Z
Learning: In the Bifrost project's ConfigStore, different functions handle sensitive values differently based on their use cases. The `restoreMetaConfigEnvVars` function preserves actual values without redaction when writing config back to file for round-trip fidelity, while `GetProviderConfigRedacted` redacts sensitive values for external API responses for security purposes. This different handling is intentional and based on the specific context where each function is used.
transports/bifrost-http/plugins/logging/utils.go (9)
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#149
File: transports/bifrost-http/main.go:259-261
Timestamp: 2025-07-08T18:20:24.086Z
Learning: In transports/bifrost-http/lib/store.go, the LoadFromConfig method already handles missing config files gracefully by initializing defaults and auto-detecting providers from environment variables. It only returns errors for actual parsing/processing failures, not missing files, making log.Fatalf appropriate in main.go since real errors should terminate the program.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#144
File: transports/bifrost-http/plugins/logging/utils.go:509-514
Timestamp: 2025-07-08T16:48:25.386Z
Learning: In the Bifrost logging system (transports/bifrost-http/plugins/logging/utils.go), the Content field in message structures is a struct value type, not a pointer, so it will never be nil and doesn't require nil checks. However, ContentStr within Content is a pointer and should be checked for nil.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#81
File: tests/core-providers/scenarios/complete_end_to_end.go:39-41
Timestamp: 2025-06-16T04:12:05.427Z
Learning: In the Bifrost system, error returns are of type `BifrostError` rather than the standard Go `error` interface. Therefore, use `require.Nilf(t, err, ...)` instead of `require.NoError(t, err)` when checking for errors in Bifrost function calls.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#81
File: tests/core-providers/scenarios/end_to_end_tool_calling.go:43-45
Timestamp: 2025-06-16T04:13:55.437Z
Learning: In the Bifrost codebase, errors returned from client methods like ChatCompletionRequest are of type BifrostError, not the standard error interface. For testing these errors, use require.Nilf instead of require.NoErrorf since BifrostError doesn't work with the standard error assertion methods.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#81
File: tests/core-providers/scenarios/simple_chat.go:39-41
Timestamp: 2025-06-16T04:13:42.755Z
Learning: In the Bifrost codebase, errors returned from methods like ChatCompletionRequest are of type BifrostError (a custom error type) rather than the standard Go error interface. Therefore, require.Nilf should be used for error assertions instead of require.NoErrorf.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#149
File: transports/bifrost-http/plugins/logging/main.go:0-0
Timestamp: 2025-07-08T18:09:32.147Z
Learning: In the Bifrost HTTP transport logging plugin (transports/bifrost-http/plugins/logging/main.go), the DatabasePath is explicitly set from main.go via a config struct pointing to appDir/logs, so the default value in the NewLoggerPlugin constructor is only used for standalone plugin usage and doesn't affect the main application flow.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#80
File: plugins/maxim/main.go:249-264
Timestamp: 2025-06-14T06:17:54.426Z
Learning: In the BifrostError struct, the Error field is a struct (not a pointer), so accessing bifrostErr.Error.Message, bifrostErr.Error.Code, and bifrostErr.Error.Type is safe without nil checks on the Error field itself. The Code and Type fields are of type *string.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#144
File: transports/bifrost-http/plugins/logging/utils.go:286-292
Timestamp: 2025-07-08T16:40:59.098Z
Learning: Pratham-Mishra04 prefers to keep simpler error handling patterns when errors are unlikely to occur in practice, such as safety checks in BadgerDB iterations where item.Value() is called on valid items. The user considers the overhead of explicit error handling not worth it in such scenarios.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#94
File: core/bifrost.go:823-845
Timestamp: 2025-06-18T15:15:51.323Z
Learning: In the Bifrost project, the team prioritizes maintaining consistent error handling patterns over exposing detailed error context. All errors should be wrapped in the standard `BifrostError` structure rather than creating specific error types or exposing richer error details like exit codes or stderr output.
transports/bifrost-http/ui/_next/static/chunks/app/config/page-400ac111d2c44d93.js (1)
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#85
File: core/providers/anthropic.go:150-156
Timestamp: 2025-06-15T16:07:53.140Z
Learning: In the Bifrost codebase, constructor functions are allowed to mutate input ProviderConfig objects in-place (e.g., setting default BaseURL values and trimming trailing slashes). This pattern is acceptable and doesn't need to be flagged as a code review issue.
transports/bifrost-http/ui/config/index.html (2)
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#54
File: core/schemas/provider.go:148-148
Timestamp: 2025-06-04T03:57:50.981Z
Learning: Breaking changes in the Bifrost codebase are managed by first merging and tagging core schema changes, then updating dependent code references in subsequent steps after the core version is released.
Learnt from: Pratham-Mishra04
PR: maximhq/bifrost#103
File: .github/workflows/transport-dependency-update.yml:53-75
Timestamp: 2025-06-20T16:21:18.912Z
Learning: In the bifrost repository's transport dependency update workflow, when updating the core dependency to a new version using `go get`, the go.mod and go.sum files will always change in normal operation, making the safety check for changes more of a defensive programming practice rather than handling a common scenario.
🧬 Code Graph Analysis (8)
transports/bifrost-http/main.go (1)
transports/bifrost-http/lib/config.go (1)
ClientConfig(11-16)
transports/bifrost-http/handlers/logging.go (1)
transports/bifrost-http/handlers/utils.go (1)
SendJSON(14-22)
transports/bifrost-http/handlers/mcp.go (1)
transports/bifrost-http/handlers/utils.go (1)
SendError(25-34)
transports/bifrost-http/handlers/providers.go (1)
transports/bifrost-http/handlers/utils.go (1)
SendError(25-34)
core/bifrost.go (2)
core/mcp.go (2)
MCPManager(48-54)MCPClient(57-64)core/schemas/mcp.go (1)
MCPClient(47-52)
transports/bifrost-http/handlers/config.go (2)
transports/bifrost-http/lib/config.go (1)
ClientConfig(11-16)transports/bifrost-http/handlers/utils.go (2)
SendError(25-34)SendJSON(14-22)
transports/bifrost-http/lib/store.go (6)
transports/bifrost-http/lib/config.go (1)
ClientConfig(11-16)core/schemas/mcp.go (2)
MCPConfig(6-8)MCPClientConfig(11-18)ui/lib/types/config.ts (3)
Key(7-11)MetaConfig(30-49)ModelProvider(4-4)core/schemas/meta/azure.go (1)
AzureMetaConfig(8-12)core/schemas/meta/bedrock.go (1)
BedrockMetaConfig(8-14)core/schemas/meta/vertex.go (1)
VertexMetaConfig(8-12)
transports/bifrost-http/plugins/logging/utils.go (1)
transports/bifrost-http/plugins/logging/main.go (9)
IndexPrefix(23-23)ObjectIndex(29-29)LoggerPlugin(123-134)SearchFilters(67-79)PaginationOptions(82-87)SearchResult(90-99)LogEntry(48-64)LatencyIndex(32-32)TokenIndex(33-33)
🪛 LanguageTool
docs/benchmarks.md
[typographical] ~46-~46: To join two clauses or set off examples, consider using an em dash.
Context: ... When using the UI, there is no drop in performance - only memory usage increases due to the a...
(QB_NEW_EN_DASH_RULE_EM)
[grammar] ~46-~46: Use correct spacing
Context: ...es due to the additional UI build being served. --- ## 🎯 Key Performance Highlights - **Perf...
(QB_NEW_EN_OTHER_ERROR_IDS_5)
transports/bifrost-http/ui/docs/index.txt
[misspelling] ~20-~20: Ten skrót piszemy z kropką: "P."
Context: .../css/04f1137b8e39b139.css","style"] 0:{"P":null,"b":"build","p":"","c":["","docs"...
(SKROTY_Z_KROPKA)
[misspelling] ~20-~20: Ten skrót piszemy z kropką: "p."
Context: ....css","style"] 0:{"P":null,"b":"build","p":"","c":["","docs",""],"i":false,"f":[[...
(SKROTY_Z_KROPKA)
[misspelling] ~20-~20: Ten skrót piszemy z kropką: "pt."
Context: ...x-auto flex min-h-screen w-5xl flex-col pt-24 pb-12","children":["$","$L7",null,{"...
(SKROTY_Z_KROPKA)
[misspelling] ~20-~20: Ten skrót piszemy z kropką: "p."
Context: ...hildren":[["$","div",null,{"className":"p-3 font-semibold","children":"Documentat...
(SKROTY_Z_KROPKA)
[misspelling] ~20-~20: Ten skrót piszemy z kropką: "max."
Context: ...],["$","div",null,{"className":"mx-auto max-w-7xl","children":["$","div",null,{"cla...
(SKROTY_Z_KROPKA)
[misspelling] ~20-~20: Ten skrót piszemy z kropką: "p."
Context: ...":"Power Up Your Bifrost Stack"}],["$","p",null,{"className":"text-muted-foregrou...
(SKROTY_Z_KROPKA)
[misspelling] ~20-~20: Ten skrót piszemy z kropką: "max."
Context: ...assName":"text-muted-foreground mx-auto max-w-2xl text-lg","children":"Everything y...
(SKROTY_Z_KROPKA)
[numbers] ~20-~20: Prawdopodobnie niepoprawny format liczby dziesiętnej. Czy powinno być "0,5"?
Context: ...ustify-center rounded-md border px-2 py-0.5 font-medium w-fit whitespace-nowrap shr...
(FORMAT_DZIESIETNY)
[grammar] ~20-~20: Błędna końcówka przypadku. Powinno być: "gapy"
Context: ...itespace-nowrap shrink-0 [&>svg]:size-3 gap-1 [&>svg]:pointer-events-none focus-vis...
(SKLADNIA_LICZEBNIKA)
[misspelling] ~20-~20: Ten skrót piszemy z kropką: "r."
Context: ...,"circle","1h7g24",{"cx":"18","cy":"6","r":"3"}],["$","circle","fqmcym",{"cx":"6"...
(SKROTY_Z_KROPKA)
[misspelling] ~20-~20: Ten skrót piszemy z kropką: "r."
Context: ...,"circle","fqmcym",{"cx":"6","cy":"18","r":"3"}],["$","path","n2h4wq",{"d":"M18 9...
(SKROTY_Z_KROPKA)
[numbers] ~20-~20: Prawdopodobnie niepoprawny format liczby dziesiętnej. Czy powinno być "0,5"?
Context: ...ustify-center rounded-md border px-2 py-0.5 font-medium w-fit whitespace-nowrap shr...
(FORMAT_DZIESIETNY)
[grammar] ~20-~20: Błędna końcówka przypadku. Powinno być: "gapy"
Context: ...itespace-nowrap shrink-0 [&>svg]:size-3 gap-1 [&>svg]:pointer-events-none focus-vis...
(SKLADNIA_LICZEBNIKA)
[misspelling] ~20-~20: Ten skrót piszemy z kropką: "r."
Context: ...$","circle","nufk8",{"cx":"9","cy":"7","r":"4"}],"$undefined"]}]}],"$undefined"]}...
(SKROTY_Z_KROPKA)
[misspelling] ~20-~20: Liczebniki porządkowe zapisujemy nie z końcówkami przypadków, tylko z kropką: "2.".
Context: ...",{"d":"M4 14a1 1 0 0 1-.78-1.63l9.9-10.2a.5.5 0 0 1 .86.46l-1.92 6.02A1 1 0 0 0 1...
(LICZEBNIKI)
[numbers] ~20-~20: Brak spacji po wartości liczbowej. Powinno być: "46 l".
Context: ... 0 0 1-.78-1.63l9.9-10.2a.5.5 0 0 1 .86.46l-1.92 6.02A1 1 0 0 0 13 10h7a1 1 0 0 1 ....
(JEDNOSTKA_LICZBA)
[numbers] ~20-~20: Brak spacji po wartości liczbowej. Powinno być: "63 l".
Context: ... 6.02A1 1 0 0 0 13 10h7a1 1 0 0 1 .78 1.63l-9.9 10.2a.5.5 0 0 1-.86-.46l1.92-6.02A1...
(JEDNOSTKA_LICZBA)
[misspelling] ~20-~20: Liczebniki porządkowe zapisujemy nie z końcówkami przypadków, tylko z kropką: "2.".
Context: ... 0 0 13 10h7a1 1 0 0 1 .78 1.63l-9.9 10.2a.5.5 0 0 1-.86-.46l1.92-6.02A1 1 0 0 0 1...
(LICZEBNIKI)
[misspelling] ~20-~20: Ten skrót piszemy z kropką: "pt."
Context: ..."$","div",null,{"className":"grid gap-6 pt-8 md:grid-cols-2","children":[["$","div...
(SKROTY_Z_KROPKA)
[misspelling] ~20-~20: Ten skrót piszemy z kropką: "p."
Context: ...t","className":"px-6","children":[["$","p",null,{"className":"text-muted-foregrou...
(SKROTY_Z_KROPKA)
[numbers] ~20-~20: Brak spacji po wartości liczbowej. Powinno być: "73 l".
Context: ... 2h-.44a2 2 0 0 0-2 2v.18a2 2 0 0 1-1 1.73l-.43.25a2 2 0 0 1-2 0l-.15-.08a2 2 0 0 0...
(JEDNOSTKA_LICZBA)
[numbers] ~20-~20: Brak spacji po wartości liczbowej. Powinno być: "0 l".
Context: ...18a2 2 0 0 1-1 1.73l-.43.25a2 2 0 0 1-2 0l-.15-.08a2 2 0 0 0-2.73.73l-.22.38a2 2 0...
(JEDNOSTKA_LICZBA)
[numbers] ~20-~20: Brak spacji po wartości liczbowej. Powinno być: "73 l".
Context: ...5a2 2 0 0 1-2 0l-.15-.08a2 2 0 0 0-2.73.73l-.22.38a2 2 0 0 0 .73 2.73l.15.1a2 2 0 0...
(JEDNOSTKA_LICZBA)
[numbers] ~20-~20: Brak spacji po wartości liczbowej. Powinno być: "73 l".
Context: ...2 0 0 0-2.73.73l-.22.38a2 2 0 0 0 .73 2.73l.15.1a2 2 0 0 1 1 1.72v.51a2 2 0 0 1-1 1...
(JEDNOSTKA_LICZBA)
[numbers] ~20-~20: Brak spacji po wartości liczbowej. Powinno być: "74 l".
Context: ...15.1a2 2 0 0 1 1 1.72v.51a2 2 0 0 1-1 1.74l-.15.09a2 2 0 0 0-.73 2.73l.22.38a2 2 0 ...
(JEDNOSTKA_LICZBA)
[numbers] ~20-~20: Brak spacji po wartości liczbowej. Powinno być: "73 l".
Context: ... 2 0 0 1-1 1.74l-.15.09a2 2 0 0 0-.73 2.73l.22.38a2 2 0 0 0 2.73.73l.15-.08a2 2 0 0...
(JEDNOSTKA_LICZBA)
[numbers] ~20-~20: Brak spacji po wartości liczbowej. Powinno być: "73 l".
Context: ... 2 0 0 0-.73 2.73l.22.38a2 2 0 0 0 2.73.73l.15-.08a2 2 0 0 1 2 0l.43.25a2 2 0 0 1 1...
(JEDNOSTKA_LICZBA)
[numbers] ~20-~20: Brak spacji po wartości liczbowej. Powinno być: "0 l".
Context: ...8a2 2 0 0 0 2.73.73l.15-.08a2 2 0 0 1 2 0l.43.25a2 2 0 0 1 1 1.73V20a2 2 0 0 0 2 2...
(JEDNOSTKA_LICZBA)
[numbers] ~20-~20: Brak spacji po wartości liczbowej. Powinno być: "73 l".
Context: ... 2h.44a2 2 0 0 0 2-2v-.18a2 2 0 0 1 1-1.73l.43-.25a2 2 0 0 1 2 0l.15.08a2 2 0 0 0 2...
(JEDNOSTKA_LICZBA)
[numbers] ~20-~20: Brak spacji po wartości liczbowej. Powinno być: "0 l".
Context: ...18a2 2 0 0 1 1-1.73l.43-.25a2 2 0 0 1 2 0l.15.08a2 2 0 0 0 2.73-.73l.22-.39a2 2 0 ...
(JEDNOSTKA_LICZBA)
[numbers] ~20-~20: Brak spacji po wartości liczbowej. Powinno być: "73 l".
Context: ...25a2 2 0 0 1 2 0l.15.08a2 2 0 0 0 2.73-.73l.22-.39a2 2 0 0 0-.73-2.73l-.15-.08a2 2 ...
(JEDNOSTKA_LICZBA)
[numbers] ~20-~20: Brak spacji po wartości liczbowej. Powinno być: "73 l".
Context: ... 0 0 0 2.73-.73l.22-.39a2 2 0 0 0-.73-2.73l-.15-.08a2 2 0 0 1-1-1.74v-.5a2 2 0 0 1 ...
(JEDNOSTKA_LICZBA)
[numbers] ~20-~20: Brak spacji po wartości liczbowej. Powinno być: "74 l".
Context: ...-.08a2 2 0 0 1-1-1.74v-.5a2 2 0 0 1 1-1.74l.15-.09a2 2 0 0 0 .73-2.73l-.22-.38a2 2 ...
(JEDNOSTKA_LICZBA)
[numbers] ~20-~20: Brak spacji po wartości liczbowej. Powinno być: "73 l".
Context: ... 2 0 0 1 1-1.74l.15-.09a2 2 0 0 0 .73-2.73l-.22-.38a2 2 0 0 0-2.73-.73l-.15.08a2 2 ...
(JEDNOSTKA_LICZBA)
[numbers] ~20-~20: Brak spacji po wartości liczbowej. Powinno być: "73 l".
Context: ...0 0 0 .73-2.73l-.22-.38a2 2 0 0 0-2.73-.73l-.15.08a2 2 0 0 1-2 0l-.43-.25a2 2 0 0 1...
(JEDNOSTKA_LICZBA)
[numbers] ~20-~20: Brak spacji po wartości liczbowej. Powinno być: "0 l".
Context: ...a2 2 0 0 0-2.73-.73l-.15.08a2 2 0 0 1-2 0l-.43-.25a2 2 0 0 1-1-1.73V4a2 2 0 0 0-2-...
(JEDNOSTKA_LICZBA)
[misspelling] ~20-~20: Ten skrót piszemy z kropką: "r."
Context: ..."circle","1v7zrd",{"cx":"12","cy":"12","r":"3"}],"$undefined"]}],"Configuration R...
(SKROTY_Z_KROPKA)
[misspelling] ~20-~20: Ten skrót piszemy z kropką: "p."
Context: ...t","className":"px-6","children":[["$","p",null,{"className":"text-muted-foregrou...
(SKROTY_Z_KROPKA)
[numbers] ~20-~20: Brak spacji po wartości liczbowej. Powinno być: "73 l".
Context: ... 2h-.44a2 2 0 0 0-2 2v.18a2 2 0 0 1-1 1.73l-.43.25a2 2 0 0 1-2 0l-.15-.08a2 2 0 0 0...
(JEDNOSTKA_LICZBA)
[numbers] ~20-~20: Brak spacji po wartości liczbowej. Powinno być: "0 l".
Context: ...18a2 2 0 0 1-1 1.73l-.43.25a2 2 0 0 1-2 0l-.15-.08a2 2 0 0 0-2.73.73l-.22.38a2 2 0...
(JEDNOSTKA_LICZBA)
[numbers] ~20-~20: Brak spacji po wartości liczbowej. Powinno być: "73 l".
Context: ...5a2 2 0 0 1-2 0l-.15-.08a2 2 0 0 0-2.73.73l-.22.38a2 2 0 0 0 .73 2.73l.15.1a2 2 0 0...
(JEDNOSTKA_LICZBA)
[numbers] ~20-~20: Brak spacji po wartości liczbowej. Powinno być: "73 l".
Context: ...2 0 0 0-2.73.73l-.22.38a2 2 0 0 0 .73 2.73l.15.1a2 2 0 0 1 1 1.72v.51a2 2 0 0 1-1 1...
(JEDNOSTKA_LICZBA)
[numbers] ~20-~20: Brak spacji po wartości liczbowej. Powinno być: "74 l".
Context: ...15.1a2 2 0 0 1 1 1.72v.51a2 2 0 0 1-1 1.74l-.15.09a2 2 0 0 0-.73 2.73l.22.38a2 2 0 ...
(JEDNOSTKA_LICZBA)
[numbers] ~20-~20: Brak spacji po wartości liczbowej. Powinno być: "73 l".
Context: ... 2 0 0 1-1 1.74l-.15.09a2 2 0 0 0-.73 2.73l.22.38a2 2 0 0 0 2.73.73l.15-.08a2 2 0 0...
(JEDNOSTKA_LICZBA)
[numbers] ~20-~20: Brak spacji po wartości liczbowej. Powinno być: "73 l".
Context: ... 2 0 0 0-.73 2.73l.22.38a2 2 0 0 0 2.73.73l.15-.08a2 2 0 0 1 2 0l.43.25a2 2 0 0 1 1...
(JEDNOSTKA_LICZBA)
[numbers] ~20-~20: Brak spacji po wartości liczbowej. Powinno być: "0 l".
Context: ...8a2 2 0 0 0 2.73.73l.15-.08a2 2 0 0 1 2 0l.43.25a2 2 0 0 1 1 1.73V20a2 2 0 0 0 2 2...
(JEDNOSTKA_LICZBA)
[numbers] ~20-~20: Brak spacji po wartości liczbowej. Powinno być: "73 l".
Context: ... 2h.44a2 2 0 0 0 2-2v-.18a2 2 0 0 1 1-1.73l.43-.25a2 2 0 0 1 2 0l.15.08a2 2 0 0 0 2...
(JEDNOSTKA_LICZBA)
[numbers] ~20-~20: Brak spacji po wartości liczbowej. Powinno być: "0 l".
Context: ...18a2 2 0 0 1 1-1.73l.43-.25a2 2 0 0 1 2 0l.15.08a2 2 0 0 0 2.73-.73l.22-.39a2 2 0 ...
(JEDNOSTKA_LICZBA)
[numbers] ~20-~20: Brak spacji po wartości liczbowej. Powinno być: "73 l".
Context: ...25a2 2 0 0 1 2 0l.15.08a2 2 0 0 0 2.73-.73l.22-.39a2 2 0 0 0-.73-2.73l-.15-.08a2 2 ...
(JEDNOSTKA_LICZBA)
[numbers] ~20-~20: Brak spacji po wartości liczbowej. Powinno być: "73 l".
Context: ... 0 0 0 2.73-.73l.22-.39a2 2 0 0 0-.73-2.73l-.15-.08a2 2 0 0 1-1-1.74v-.5a2 2 0 0 1 ...
(JEDNOSTKA_LICZBA)
[numbers] ~20-~20: Brak spacji po wartości liczbowej. Powinno być: "74 l".
Context: ...-.08a2 2 0 0 1-1-1.74v-.5a2 2 0 0 1 1-1.74l.15-.09a2 2 0 0 0 .73-2.73l-.22-.38a2 2 ...
(JEDNOSTKA_LICZBA)
[numbers] ~20-~20: Brak spacji po wartości liczbowej. Powinno być: "73 l".
Context: ... 2 0 0 1 1-1.74l.15-.09a2 2 0 0 0 .73-2.73l-.22-.38a2 2 0 0 0-2.73-.73l-.15.08a2 2 ...
(JEDNOSTKA_LICZBA)
[numbers] ~20-~20: Brak spacji po wartości liczbowej. Powinno być: "73 l".
Context: ...0 0 0 .73-2.73l-.22-.38a2 2 0 0 0-2.73-.73l-.15.08a2 2 0 0 1-2 0l-.43-.25a2 2 0 0 1...
(JEDNOSTKA_LICZBA)
[numbers] ~20-~20: Brak spacji po wartości liczbowej. Powinno być: "0 l".
Context: ...a2 2 0 0 0-2.73-.73l-.15.08a2 2 0 0 1-2 0l-.43-.25a2 2 0 0 1-1-1.73V4a2 2 0 0 0-2-...
(JEDNOSTKA_LICZBA)
[misspelling] ~20-~20: Ten skrót piszemy z kropką: "r."
Context: ..."circle","1v7zrd",{"cx":"12","cy":"12","r":"3"}],"$undefined"]}],"Configuration D...
(SKROTY_Z_KROPKA)
transports/bifrost-http/ui/config/index.txt
[misspelling] ~19-~19: Ten skrót piszemy z kropką: "P."
Context: .../css/04f1137b8e39b139.css","style"] 0:{"P":null,"b":"build","p":"","c":["","confi...
(SKROTY_Z_KROPKA)
[misspelling] ~19-~19: Ten skrót piszemy z kropką: "p."
Context: ....css","style"] 0:{"P":null,"b":"build","p":"","c":["","config",""],"i":false,"f":...
(SKROTY_Z_KROPKA)
[misspelling] ~19-~19: Ten skrót piszemy z kropką: "pt."
Context: ...x-auto flex min-h-screen w-5xl flex-col pt-24 pb-12","children":["$","$L7",null,{"...
(SKROTY_Z_KROPKA)
transports/bifrost-http/ui/index.txt
[misspelling] ~19-~19: Ten skrót piszemy z kropką: "P."
Context: .../css/04f1137b8e39b139.css","style"] 0:{"P":null,"b":"build","p":"","c":["",""],"i...
(SKROTY_Z_KROPKA)
[misspelling] ~19-~19: Ten skrót piszemy z kropką: "p."
Context: ....css","style"] 0:{"P":null,"b":"build","p":"","c":["",""],"i":false,"f":[[["",{"c...
(SKROTY_Z_KROPKA)
[misspelling] ~19-~19: Ten skrót piszemy z kropką: "pt."
Context: ...x-auto flex min-h-screen w-5xl flex-col pt-24 pb-12","children":["$","$L7",null,{"...
(SKROTY_Z_KROPKA)
🪛 Biome (1.9.4)
transports/bifrost-http/ui/_next/static/chunks/812-4eac91fa641b7ecf.js
[error] 1-1: Redundant use strict directive.
The entire contents of JavaScript modules are automatically in strict mode, with no statement needed to initiate it.
Safe fix: Remove the redundant use strict directive.
(lint/suspicious/noRedundantUseStrict)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Change to an optional chain.
Unsafe fix: Change to an optional chain.
(lint/complexity/useOptionalChain)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares a variable that is only assigned once.
'e' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
'e' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'e' is never reassigned.
'a' is never reassigned.
'r' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'e' is never reassigned.
'a' is never reassigned.
'r' is never reassigned.
'n' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares a variable that is only assigned once.
'e' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
'o' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares a variable that is only assigned once.
'n' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
'e' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'e' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'e' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'e' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares a variable that is only assigned once.
'e' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
'e' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'e' is never reassigned.
'a' is never reassigned.
'o' is never reassigned.
'l' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'e' is never reassigned.
'a' is never reassigned.
'n' is never reassigned.
'o' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'e' is never reassigned.
'a' is never reassigned.
'n' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'e' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'e' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
's' is never reassigned.
'r' is never reassigned.
'n' is never reassigned.
'o' is never reassigned.
'l' is never reassigned.
'i' is never reassigned.
'd' is never reassigned.
'c' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
'e' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'e' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'e' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'e' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'e' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
'e' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'e' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'e' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'e' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'e' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'e' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares a variable that is only assigned once.
'o' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'e' is never reassigned.
'a' is never reassigned.
'r' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'e' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares a variable that is only assigned once.
'e' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares a variable that is only assigned once.
'e' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
'e' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'e' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'e' is never reassigned.
'a' is never reassigned.
'l' is never reassigned.
'c' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'e' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'e' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'e' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'e' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
transports/bifrost-http/ui/_next/static/chunks/529-26467b76604e8781.js
[error] 1-1: Redundant use strict directive.
The entire contents of JavaScript modules are automatically in strict mode, with no statement needed to initiate it.
Safe fix: Remove the redundant use strict directive.
(lint/suspicious/noRedundantUseStrict)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Redundant use strict directive.
The entire contents of JavaScript modules are automatically in strict mode, with no statement needed to initiate it.
Safe fix: Remove the redundant use strict directive.
(lint/suspicious/noRedundantUseStrict)
[error] 1-1: Redundant use strict directive.
The entire contents of JavaScript modules are automatically in strict mode, with no statement needed to initiate it.
Safe fix: Remove the redundant use strict directive.
(lint/suspicious/noRedundantUseStrict)
[error] 1-1: Redundant use strict directive.
The entire contents of JavaScript modules are automatically in strict mode, with no statement needed to initiate it.
Safe fix: Remove the redundant use strict directive.
(lint/suspicious/noRedundantUseStrict)
[error] 1-1: Redundant use strict directive.
The entire contents of JavaScript modules are automatically in strict mode, with no statement needed to initiate it.
Safe fix: Remove the redundant use strict directive.
(lint/suspicious/noRedundantUseStrict)
[error] 1-1: Redundant use strict directive.
The entire contents of JavaScript modules are automatically in strict mode, with no statement needed to initiate it.
Safe fix: Remove the redundant use strict directive.
(lint/suspicious/noRedundantUseStrict)
[error] 1-1: Redundant use strict directive.
The entire contents of JavaScript modules are automatically in strict mode, with no statement needed to initiate it.
Safe fix: Remove the redundant use strict directive.
(lint/suspicious/noRedundantUseStrict)
[error] 1-1: Redundant use strict directive.
The entire contents of JavaScript modules are automatically in strict mode, with no statement needed to initiate it.
Safe fix: Remove the redundant use strict directive.
(lint/suspicious/noRedundantUseStrict)
[error] 1-1: Redundant use strict directive.
The entire contents of JavaScript modules are automatically in strict mode, with no statement needed to initiate it.
Safe fix: Remove the redundant use strict directive.
(lint/suspicious/noRedundantUseStrict)
[error] 1-1: Redundant use strict directive.
The entire contents of JavaScript modules are automatically in strict mode, with no statement needed to initiate it.
Safe fix: Remove the redundant use strict directive.
(lint/suspicious/noRedundantUseStrict)
[error] 1-1: Redundant use strict directive.
The entire contents of JavaScript modules are automatically in strict mode, with no statement needed to initiate it.
Safe fix: Remove the redundant use strict directive.
(lint/suspicious/noRedundantUseStrict)
[error] 1-1: Redundant use strict directive.
The entire contents of JavaScript modules are automatically in strict mode, with no statement needed to initiate it.
Safe fix: Remove the redundant use strict directive.
(lint/suspicious/noRedundantUseStrict)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Redundant use strict directive.
The entire contents of JavaScript modules are automatically in strict mode, with no statement needed to initiate it.
Safe fix: Remove the redundant use strict directive.
(lint/suspicious/noRedundantUseStrict)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Redundant use strict directive.
The entire contents of JavaScript modules are automatically in strict mode, with no statement needed to initiate it.
Safe fix: Remove the redundant use strict directive.
(lint/suspicious/noRedundantUseStrict)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Change to an optional chain.
Unsafe fix: Change to an optional chain.
(lint/complexity/useOptionalChain)
[error] 1-1: Change to an optional chain.
Unsafe fix: Change to an optional chain.
(lint/complexity/useOptionalChain)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Change to an optional chain.
Unsafe fix: Change to an optional chain.
(lint/complexity/useOptionalChain)
[error] 1-1: Template literals are preferred over string concatenation.
Unsafe fix: Use a template literal.
(lint/style/useTemplate)
[error] 1-1: Template literals are preferred over string concatenation.
Unsafe fix: Use a template literal.
(lint/style/useTemplate)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Template literals are preferred over string concatenation.
Unsafe fix: Use a template literal.
(lint/style/useTemplate)
[error] 1-1: Comparing to itself is potentially pointless.
(lint/suspicious/noSelfCompare)
[error] 1-1: Comparing to itself is potentially pointless.
(lint/suspicious/noSelfCompare)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Template literals are preferred over string concatenation.
Unsafe fix: Use a template literal.
(lint/style/useTemplate)
[error] 1-1: Other switch clauses can erroneously access this declaration.
Wrap the declaration in a block to restrict its access to the switch clause.
The declaration is defined in this switch clause:
Unsafe fix: Wrap the declaration in a block.
(lint/correctness/noSwitchDeclarations)
[error] 1-1: Other switch clauses can erroneously access this declaration.
Wrap the declaration in a block to restrict its access to the switch clause.
The declaration is defined in this switch clause:
Unsafe fix: Wrap the declaration in a block.
(lint/correctness/noSwitchDeclarations)
[error] 1-1: Other switch clauses can erroneously access this declaration.
Wrap the declaration in a block to restrict its access to the switch clause.
The declaration is defined in this switch clause:
Unsafe fix: Wrap the declaration in a block.
(lint/correctness/noSwitchDeclarations)
[error] 1-1: Other switch clauses can erroneously access this declaration.
Wrap the declaration in a block to restrict its access to the switch clause.
The declaration is defined in this switch clause:
Unsafe fix: Wrap the declaration in a block.
(lint/correctness/noSwitchDeclarations)
[error] 1-1: This case is falling through to the next case.
Add a break or return statement to the end of this case to prevent fallthrough.
(lint/suspicious/noFallthroughSwitchClause)
[error] 1-1: This case is falling through to the next case.
Add a break or return statement to the end of this case to prevent fallthrough.
(lint/suspicious/noFallthroughSwitchClause)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Comparing to itself is potentially pointless.
(lint/suspicious/noSelfCompare)
[error] 1-1: Comparing to itself is potentially pointless.
(lint/suspicious/noSelfCompare)
[error] 1-1: Redundant use strict directive.
The entire contents of JavaScript modules are automatically in strict mode, with no statement needed to initiate it.
Safe fix: Remove the redundant use strict directive.
(lint/suspicious/noRedundantUseStrict)
[error] 1-1: Redundant use strict directive.
The entire contents of JavaScript modules are automatically in strict mode, with no statement needed to initiate it.
Safe fix: Remove the redundant use strict directive.
(lint/suspicious/noRedundantUseStrict)
[error] 1-1: This variable is used before its declaration.
The variable is declared here:
(lint/correctness/noInvalidUseBeforeDeclaration)
[error] 1-1: This variable is used before its declaration.
The variable is declared here:
(lint/correctness/noInvalidUseBeforeDeclaration)
[error] 1-1: This variable is used before its declaration.
The variable is declared here:
(lint/correctness/noInvalidUseBeforeDeclaration)
[error] 1-1: This variable is used before its declaration.
The variable is declared here:
(lint/correctness/noInvalidUseBeforeDeclaration)
[error] 1-1: This variable is used before its declaration.
The variable is declared here:
(lint/correctness/noInvalidUseBeforeDeclaration)
[error] 1-1: This variable is used before its declaration.
The variable is declared here:
(lint/correctness/noInvalidUseBeforeDeclaration)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'let' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares a variable that is only assigned once.
'n' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
'n' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
'n' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
'n' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
'n' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
'n' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
'n' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
'n' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
'n' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
'n' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
'r' is never reassigned.
'i' is never reassigned.
'c' is never reassigned.
'u' is never reassigned.
'p' is never reassigned.
'h' is never reassigned.
'v' is never reassigned.
'b' is never reassigned.
'_' is never reassigned.
'g' is never reassigned.
'm' is never reassigned.
'A' is never reassigned.
'w' is never reassigned.
'x' is never reassigned.
'z' is never reassigned.
'M' is never reassigned.
'O' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
'r' is never reassigned.
'n' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
'r' is never reassigned.
'a' is never reassigned.
'i' is never reassigned.
's' is never reassigned.
'l' is never reassigned.
'd' is never reassigned.
'p' is never reassigned.
'h' is never reassigned.
'y' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
'e' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
'r' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'r' is never reassigned.
'n' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
'r' is never reassigned.
'n' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'r' is never reassigned.
'n' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
'r' is never reassigned.
'n' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
'r' is never reassigned.
'a' is never reassigned.
'c' is never reassigned.
'l' is never reassigned.
'f' is never reassigned.
'd' is never reassigned.
'h' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'let' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
'r' is never reassigned.
'n' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
'r' is never reassigned.
'n' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
'r' is never reassigned.
'n' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
'r' is never reassigned.
'n' is never reassigned.
'a' is never reassigned.
's' is never reassigned.
'c' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'r' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'let' instead.
(lint/style/noVar)
[error] 1-1: This let declares a variable that is only assigned once.
'n' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Reassigning a function parameter is confusing.
The parameter is declared here:
Use a local variable instead.
(lint/style/noParameterAssign)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'let' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'let' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'let' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'let' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'let' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'let' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'let' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'let' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'let' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'let' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'let' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'let' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'let' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'let' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'let' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'let' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'let' instead.
(lint/style/noVar)
[error] 1-1: Reassigning a function parameter is confusing.
The parameter is declared here:
Use a local variable instead.
(lint/style/noParameterAssign)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'let' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'let' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'let' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'let' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: Reassigning a function parameter is confusing.
The parameter is declared here:
Use a local variable instead.
(lint/style/noParameterAssign)
[error] 1-1: Reassigning a function parameter is confusing.
The parameter is declared here:
Use a local variable instead.
(lint/style/noParameterAssign)
[error] 1-1: Reassigning a function parameter is confusing.
The parameter is declared here:
Use a local variable instead.
(lint/style/noParameterAssign)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'let' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'let' instead.
(lint/style/noVar)
[error] 1-1: Reassigning a function parameter is confusing.
The parameter is declared here:
Use a local variable instead.
(lint/style/noParameterAssign)
[error] 1-1: Reassigning a function parameter is confusing.
The parameter is declared here:
Use a local variable instead.
(lint/style/noParameterAssign)
[error] 1-1: Reassigning a function parameter is confusing.
The parameter is declared here:
Use a local variable instead.
(lint/style/noParameterAssign)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'let' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'let' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'let' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'let' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'let' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares a variable that is only assigned once.
'n' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
'n' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
transports/bifrost-http/ui/_next/static/chunks/app/layout-188bea908cf68435.js
[error] 1-1: Redundant use strict directive.
The entire contents of JavaScript modules are automatically in strict mode, with no statement needed to initiate it.
Safe fix: Remove the redundant use strict directive.
(lint/suspicious/noRedundantUseStrict)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Redundant use strict directive.
The entire contents of JavaScript modules are automatically in strict mode, with no statement needed to initiate it.
Safe fix: Remove the redundant use strict directive.
(lint/suspicious/noRedundantUseStrict)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Redundant use strict directive.
The entire contents of JavaScript modules are automatically in strict mode, with no statement needed to initiate it.
Safe fix: Remove the redundant use strict directive.
(lint/suspicious/noRedundantUseStrict)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Redundant use strict directive.
The entire contents of JavaScript modules are automatically in strict mode, with no statement needed to initiate it.
Safe fix: Remove the redundant use strict directive.
(lint/suspicious/noRedundantUseStrict)
[error] 1-1: Redundant use strict directive.
The entire contents of JavaScript modules are automatically in strict mode, with no statement needed to initiate it.
Safe fix: Remove the redundant use strict directive.
(lint/suspicious/noRedundantUseStrict)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares a variable that is only assigned once.
'u' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
'e' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'a' is never reassigned.
'i' is never reassigned.
'n' is never reassigned.
'd' is never reassigned.
'l' is never reassigned.
'h' is never reassigned.
'x' is never reassigned.
'b' is never reassigned.
'f' is never reassigned.
'm' is never reassigned.
'p' is never reassigned.
'g' is never reassigned.
'v' is never reassigned.
'j' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'e' is never reassigned.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'e' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
'e' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'w' is never reassigned.
'N' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'a' is never reassigned.
'r' is never reassigned.
'i' is never reassigned.
'n' is never reassigned.
'd' is never reassigned.
'c' is never reassigned.
'u' is never reassigned.
'x' is never reassigned.
'b' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'a' is never reassigned.
'r' is never reassigned.
'n' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
'k' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'a' is never reassigned.
'o' is never reassigned.
'c' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares a variable that is only assigned once.
'i' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
'p' is never reassigned.
'g' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'e' is never reassigned.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
transports/bifrost-http/ui/_next/static/chunks/273-9756261fec6bc01b.js
[error] 1-1: Redundant use strict directive.
The entire contents of JavaScript modules are automatically in strict mode, with no statement needed to initiate it.
Safe fix: Remove the redundant use strict directive.
(lint/suspicious/noRedundantUseStrict)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Use a while loop instead of a for loop.
Prefer a while loop over a for loop without initialization and update.
Safe fix: Use a while loop.
(lint/style/useWhile)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Use a while loop instead of a for loop.
Prefer a while loop over a for loop without initialization and update.
Safe fix: Use a while loop.
(lint/style/useWhile)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: This let declares a variable that is only assigned once.
'n' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'r' is never reassigned.
'o' is never reassigned.
'l' is never reassigned.
'a' is never reassigned.
'i' is never reassigned.
's' is never reassigned.
'u' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
'e' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'r' is never reassigned.
'o' is never reassigned.
'l' is never reassigned.
'a' is never reassigned.
'i' is never reassigned.
'c' is never reassigned.
'd' is never reassigned.
'p' is never reassigned.
'f' is never reassigned.
'x' is never reassigned.
'g' is never reassigned.
'y' is never reassigned.
'b' is never reassigned.
'C' is never reassigned.
'E' is never reassigned.
'R' is never reassigned.
'j' is never reassigned.
'_' is never reassigned.
'M' is never reassigned.
'P' is never reassigned.
'D' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
'r' is never reassigned.
'a' is never reassigned.
'i' is never reassigned.
's' is never reassigned.
'c' is never reassigned.
'd' is never reassigned.
'f' is never reassigned.
'h' is never reassigned.
'x' is never reassigned.
'g' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'r' is never reassigned.
'n' is never reassigned.
'o' is never reassigned.
'l' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
'r' is never reassigned.
'n' is never reassigned.
'o' is never reassigned.
'l' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'r' is never reassigned.
'o' is never reassigned.
'a' is never reassigned.
'i' is never reassigned.
's' is never reassigned.
'u' is never reassigned.
'c' is never reassigned.
'd' is never reassigned.
'p' is never reassigned.
'f' is never reassigned.
'h' is never reassigned.
'x' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'r' is never reassigned.
'n' is never reassigned.
'o' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'r' is never reassigned.
'n' is never reassigned.
'o' is never reassigned.
'l' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
'n' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'e' is never reassigned.
'r' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
'r' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
'n' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'e' is never reassigned.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'r' is never reassigned.
'n' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'r' is never reassigned.
'n' is never reassigned.
'o' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'e' is never reassigned.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
'e' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'r' is never reassigned.
'n' is never reassigned.
'o' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'a' is never reassigned.
'i' is never reassigned.
's' is never reassigned.
'u' is never reassigned.
'c' is never reassigned.
'd' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'r' is never reassigned.
'o' is never reassigned.
'l' is never reassigned.
'a' is never reassigned.
's' is never reassigned.
'c' is never reassigned.
'd' is never reassigned.
'p' is never reassigned.
'f' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
'e' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
'r' is never reassigned.
'n' is never reassigned.
'o' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
transports/bifrost-http/ui/_next/static/css/04f1137b8e39b139.css
[error] 1-1: Unexpected nonstandard direction
You should fix the direction value to follow the syntax.
See MDN web docs for more details.
(lint/correctness/noInvalidDirectionInLinearGradient)
[error] 1-1: Duplicate font names are redundant and unnecessary: Geist
Remove duplicate font names within the property
(lint/suspicious/noDuplicateFontNames)
[error] 1-1: Generic font family missing.
Consider adding a generic font family as a fallback.
For examples and more information, see the MDN Web Docs
(lint/a11y/useGenericFontNames)
[error] 1-1: Duplicate font names are redundant and unnecessary: Geist
Remove duplicate font names within the property
(lint/suspicious/noDuplicateFontNames)
[error] 1-1: Generic font family missing.
Consider adding a generic font family as a fallback.
For examples and more information, see the MDN Web Docs
(lint/a11y/useGenericFontNames)
transports/bifrost-http/ui/_next/static/chunks/678-56244c2aeff7b5e2.js
[error] 1-1: Redundant use strict directive.
The entire contents of JavaScript modules are automatically in strict mode, with no statement needed to initiate it.
Safe fix: Remove the redundant use strict directive.
(lint/suspicious/noRedundantUseStrict)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Change to an optional chain.
Unsafe fix: Change to an optional chain.
(lint/complexity/useOptionalChain)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares a variable that is only assigned once.
'o' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
'e' is never reassigned.
'a' is never reassigned.
'r' is never reassigned.
'n' is never reassigned.
's' is never reassigned.
'd' is never reassigned.
'c' is never reassigned.
'u' is never reassigned.
'f' is never reassigned.
'p' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
'a' is never reassigned.
'o' is never reassigned.
's' is never reassigned.
'i' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
'e' is never reassigned.
'a' is never reassigned.
'r' is never reassigned.
'n' is never reassigned.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
'a' is never reassigned.
'o' is never reassigned.
'r' is never reassigned.
'n' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
'a' is never reassigned.
'o' is never reassigned.
'r' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'a' is never reassigned.
'o' is never reassigned.
'r' is never reassigned.
'n' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
'a' is never reassigned.
's' is never reassigned.
'i' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'let' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
'e' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'a' is never reassigned.
'r' is never reassigned.
'n' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'let' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'let' instead.
(lint/style/noVar)
[error] 1-1: This let declares a variable that is only assigned once.
'i' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'a' is never reassigned.
'r' is never reassigned.
's' is never reassigned.
'i' is never reassigned.
'l' is never reassigned.
'u' is never reassigned.
'f' is never reassigned.
'p' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'a' is never reassigned.
'o' is never reassigned.
'r' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
'a' is never reassigned.
'o' is never reassigned.
'r' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
'a' is never reassigned.
'o' is never reassigned.
'n' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
'e' is never reassigned.
'a' is never reassigned.
'r' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'e' is never reassigned.
'a' is never reassigned.
'r' is never reassigned.
'n' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'let' instead.
(lint/style/noVar)
[error] 1-1: This let declares a variable that is only assigned once.
'o' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
'e' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'e' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
'e' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'let' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
'a' is never reassigned.
'o' is never reassigned.
'r' is never reassigned.
'n' is never reassigned.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'a' is never reassigned.
'n' is never reassigned.
'i' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'a' is never reassigned.
'n' is never reassigned.
'i' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'a' is never reassigned.
'n' is never reassigned.
'i' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'a' is never reassigned.
'n' is never reassigned.
'i' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'h' is never reassigned.
'v' is never reassigned.
'b' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'let' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
'e' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
'x' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'let' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
'v' is never reassigned.
'b' is never reassigned.
'x' is never reassigned.
'E' is never reassigned.
'k' is never reassigned.
'N' is never reassigned.
'C' is never reassigned.
'j' is never reassigned.
'D' is never reassigned.
'R' is never reassigned.
'M' is never reassigned.
'T' is never reassigned.
'S' is never reassigned.
'B' is never reassigned.
'I' is never reassigned.
'z' is never reassigned.
'A' is never reassigned.
'P' is never reassigned.
'Y' is never reassigned.
'O' is never reassigned.
'L' is never reassigned.
'F' is never reassigned.
'_' is never reassigned.
'H' is never reassigned.
'V' is never reassigned.
'U' is never reassigned.
'X' is never reassigned.
'G' is never reassigned.
'W' is never reassigned.
'q' is never reassigned.
'K' is never reassigned.
'Z' is never reassigned.
'J' is never reassigned.
'Q' is never reassigned.
'$' is never reassigned.
'tt' is never reassigned.
'te' is never reassigned.
'ta' is never reassigned.
'to' is never reassigned.
'tr' is never reassigned.
'tn' is never reassigned.
'ts' is never reassigned.
'ti' is never reassigned.
'tl' is never reassigned.
'td' is never reassigned.
'tc' is never reassigned.
'tu' is never reassigned.
'tf' is never reassigned.
'tp' is never reassigned.
'tm' is never reassigned.
'tg' is never reassigned.
'th' is never reassigned.
'tv' is never reassigned.
'tb' is never reassigned.
'ty' is never reassigned.
'tw' is never reassigned.
'tx' is never reassigned.
'tE' is never reassigned.
'tk' is never reassigned.
'tN' is never reassigned.
'tC' is never reassigned.
'tj' is never reassigned.
'tD' is never reassigned.
'tR' is never reassigned.
'tM' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'let' instead.
(lint/style/noVar)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
'e' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'e' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
'tT' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
'tS' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'let' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
'n' is never reassigned.
's' is never reassigned.
'i' is never reassigned.
'l' is never reassigned.
'd' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'let' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
's' is never reassigned.
'i' is never reassigned.
'l' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'e' is never reassigned.
'a' is never reassigned.
'o' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'd' is never reassigned.
'c' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'let' instead.
(lint/style/noVar)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
'k' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'a' is never reassigned.
'n' is never reassigned.
's' is never reassigned.
'i' is never reassigned.
'l' is never reassigned.
'd' is never reassigned.
'c' is never reassigned.
'u' is never reassigned.
'f' is never reassigned.
'p' is never reassigned.
'm' is never reassigned.
'g' is never reassigned.
'v' is never reassigned.
'b' is never reassigned.
'y' is never reassigned.
'w' is never reassigned.
'k' is never reassigned.
'N' is never reassigned.
'C' is never reassigned.
'j' is never reassigned.
'D' is never reassigned.
'R' is never reassigned.
'M' is never reassigned.
'T' is never reassigned.
'S' is never reassigned.
'B' is never reassigned.
'I' is never reassigned.
'z' is never reassigned.
'A' is never reassigned.
'P' is never reassigned.
'Y' is never reassigned.
'O' is never reassigned.
'L' is never reassigned.
'F' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'let' instead.
(lint/style/noVar)
[error] 1-1: This let declares a variable that is only assigned once.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
'e' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
'e' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'let' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'let' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
's' is never reassigned.
'f' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'o' is never reassigned.
'r' is never reassigned.
'n' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'let' instead.
(lint/style/noVar)
transports/bifrost-http/ui/_next/static/chunks/app/page-26aa3339d9cf36ab.js
[error] 1-1: Redundant use strict directive.
The entire contents of JavaScript modules are automatically in strict mode, with no statement needed to initiate it.
Safe fix: Remove the redundant use strict directive.
(lint/suspicious/noRedundantUseStrict)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Redundant use strict directive.
The entire contents of JavaScript modules are automatically in strict mode, with no statement needed to initiate it.
Safe fix: Remove the redundant use strict directive.
(lint/suspicious/noRedundantUseStrict)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Redundant use strict directive.
The entire contents of JavaScript modules are automatically in strict mode, with no statement needed to initiate it.
Safe fix: Remove the redundant use strict directive.
(lint/suspicious/noRedundantUseStrict)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Redundant use strict directive.
The entire contents of JavaScript modules are automatically in strict mode, with no statement needed to initiate it.
Safe fix: Remove the redundant use strict directive.
(lint/suspicious/noRedundantUseStrict)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Change to an optional chain.
Unsafe fix: Change to an optional chain.
(lint/complexity/useOptionalChain)
[error] 1-1: Change to an optional chain.
Unsafe fix: Change to an optional chain.
(lint/complexity/useOptionalChain)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Change to an optional chain.
Unsafe fix: Change to an optional chain.
(lint/complexity/useOptionalChain)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Redundant use strict directive.
The entire contents of JavaScript modules are automatically in strict mode, with no statement needed to initiate it.
Safe fix: Remove the redundant use strict directive.
(lint/suspicious/noRedundantUseStrict)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Redundant use strict directive.
The entire contents of JavaScript modules are automatically in strict mode, with no statement needed to initiate it.
Safe fix: Remove the redundant use strict directive.
(lint/suspicious/noRedundantUseStrict)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Redundant use strict directive.
The entire contents of JavaScript modules are automatically in strict mode, with no statement needed to initiate it.
Safe fix: Remove the redundant use strict directive.
(lint/suspicious/noRedundantUseStrict)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
's' is never reassigned.
'o' is never reassigned.
'd' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'let' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
's' is never reassigned.
'r' is never reassigned.
'o' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
's' is never reassigned.
'a' is never reassigned.
'l' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares a variable that is only assigned once.
'L' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
's' is never reassigned.
'l' is never reassigned.
'r' is never reassigned.
'o' is never reassigned.
'i' is never reassigned.
'd' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'u' is never reassigned.
'm' is never reassigned.
'p' is never reassigned.
'f' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'a' is never reassigned.
'l' is never reassigned.
'r' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
'n' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
's' is never reassigned.
'n' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
's' is never reassigned.
'l' is never reassigned.
'h' is never reassigned.
'x' is never reassigned.
'g' is never reassigned.
'f' is never reassigned.
'v' is never reassigned.
'j' is never reassigned.
'b' is never reassigned.
'y' is never reassigned.
'N' is never reassigned.
'w' is never reassigned.
'k' is never reassigned.
'_' is never reassigned.
'S' is never reassigned.
'A' is never reassigned.
'C' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'e' is never reassigned.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares a variable that is only assigned once.
'K' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'let' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
'b' is never reassigned.
'y' is never reassigned.
'N' is never reassigned.
'w' is never reassigned.
'k' is never reassigned.
'_' is never reassigned.
'S' is never reassigned.
'A' is never reassigned.
'C' is never reassigned.
'z' is never reassigned.
'L' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'H' is never reassigned.
'T' is never reassigned.
'B' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
'e' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'let' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
'Y' is never reassigned.
'J' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'let' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
'd' is never reassigned.
'u' is never reassigned.
'm' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
'p' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
'V' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares a variable that is only assigned once.
'Z' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
'ep' is never reassigned.
'eh' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
's' is never reassigned.
'a' is never reassigned.
'l' is never reassigned.
'r' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
'eg' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
's' is never reassigned.
'l' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
'e' is never reassigned.
't' is never reassigned.
's' is never reassigned.
'r' is never reassigned.
'o' is never reassigned.
'i' is never reassigned.
'c' is never reassigned.
'd' is never reassigned.
'u' is never reassigned.
'm' is never reassigned.
'p' is never reassigned.
'h' is never reassigned.
'x' is never reassigned.
'g' is never reassigned.
'f' is never reassigned.
'v' is never reassigned.
'j' is never reassigned.
'b' is never reassigned.
'y' is never reassigned.
'N' is never reassigned.
'w' is never reassigned.
'k' is never reassigned.
'_' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
's' is never reassigned.
'n' is never reassigned.
'l' is never reassigned.
'r' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'e' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'let' instead.
(lint/style/noVar)
[error] 1-1: This let declares a variable that is only assigned once.
'o' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
'n' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'e' is never reassigned.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'S' is never reassigned.
'A' is never reassigned.
'C' is never reassigned.
'z' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'let' instead.
(lint/style/noVar)
[error] 1-1: This let declares a variable that is only assigned once.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares a variable that is only assigned once.
'i' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
's' is never reassigned.
'a' is never reassigned.
'l' is never reassigned.
'r' is never reassigned.
'i' is never reassigned.
'c' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
's' is never reassigned.
'l' is never reassigned.
'o' is never reassigned.
'c' is never reassigned.
'd' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares a variable that is only assigned once.
'o' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
's' is never reassigned.
'l' is never reassigned.
'i' is never reassigned.
'c' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares a variable that is only assigned once.
'r' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
's' is never reassigned.
'a' is never reassigned.
'r' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
transports/bifrost-http/ui/_next/static/chunks/app/config/page-400ac111d2c44d93.js
[error] 1-1: Redundant use strict directive.
The entire contents of JavaScript modules are automatically in strict mode, with no statement needed to initiate it.
Safe fix: Remove the redundant use strict directive.
(lint/suspicious/noRedundantUseStrict)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Using this in a static context can be confusing.
this refers to the class.
Unsafe fix: Use the class name instead.
(lint/complexity/noThisInStatic)
[error] 1-1: Using this in a static context can be confusing.
this refers to the class.
Unsafe fix: Use the class name instead.
(lint/complexity/noThisInStatic)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Template literals are preferred over string concatenation.
Unsafe fix: Use a template literal.
(lint/style/useTemplate)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Declare variables separately
Unsafe fix: Break out into multiple declarations
(lint/style/useSingleVarDeclarator)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
's' is never reassigned.
't' is never reassigned.
'n' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares a variable that is only assigned once.
'j' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
's' is never reassigned.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'C' is never reassigned.
'w' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'e' is never reassigned.
's' is never reassigned.
't' is never reassigned.
'r' is never reassigned.
'i' is never reassigned.
'l' is never reassigned.
'c' is never reassigned.
'o' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'e' is never reassigned.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'd' is never reassigned.
'm' is never reassigned.
'p' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'e' is never reassigned.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'let' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
'g' is never reassigned.
'w' is never reassigned.
'A' is never reassigned.
'k' is never reassigned.
'S' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
'r' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares a variable that is only assigned once.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
's' is never reassigned.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
's' is never reassigned.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
's' is never reassigned.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
's' is never reassigned.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
's' is never reassigned.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
's' is never reassigned.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
's' is never reassigned.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
's' is never reassigned.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares a variable that is only assigned once.
'G' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'r' is never reassigned.
'i' is never reassigned.
'c' is never reassigned.
'o' is never reassigned.
'd' is never reassigned.
'u' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
'ea' is never reassigned.
'er' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
's' is never reassigned.
't' is never reassigned.
'a' is never reassigned.
'r' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
'i' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
'e' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
'ec' is never reassigned.
'eo' is never reassigned.
'ed' is never reassigned.
'eu' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'n' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
's' is never reassigned.
't' is never reassigned.
'r' is never reassigned.
'i' is never reassigned.
'l' is never reassigned.
'c' is never reassigned.
'd' is never reassigned.
'm' is never reassigned.
'p' is never reassigned.
'j' is never reassigned.
'f' is never reassigned.
'y' is never reassigned.
'_' is never reassigned.
'C' is never reassigned.
'w' is never reassigned.
'A' is never reassigned.
'S' is never reassigned.
'q' is never reassigned.
'T' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'R' is never reassigned.
'I' is never reassigned.
'V' is never reassigned.
'M' is never reassigned.
'B' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'n' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'n' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
'e' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'L' is never reassigned.
'D' is never reassigned.
'O' is never reassigned.
'Z' is never reassigned.
'$' is never reassigned.
'K' is never reassigned.
'U' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
'e' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
'e' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'n' is never reassigned.
'a' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use Number.parseFloat instead of the equivalent global.
ES2015 moved some globals into the Number namespace for consistency.
Safe fix: Use Number.parseFloat instead.
(lint/style/useNumberNamespace)
[error] 1-1: Use Number.parseInt instead of the equivalent global.
ES2015 moved some globals into the Number namespace for consistency.
Safe fix: Use Number.parseInt instead.
(lint/style/useNumberNamespace)
[error] 1-1: Use Number.parseInt instead of the equivalent global.
ES2015 moved some globals into the Number namespace for consistency.
Safe fix: Use Number.parseInt instead.
(lint/style/useNumberNamespace)
[error] 1-1: Use Number.parseInt instead of the equivalent global.
ES2015 moved some globals into the Number namespace for consistency.
Safe fix: Use Number.parseInt instead.
(lint/style/useNumberNamespace)
[error] 1-1: Use Number.parseInt instead of the equivalent global.
ES2015 moved some globals into the Number namespace for consistency.
Safe fix: Use Number.parseInt instead.
(lint/style/useNumberNamespace)
[error] 1-1: This let declares some variables that are only assigned once.
's' is never reassigned.
't' is never reassigned.
'r' is never reassigned.
'i' is never reassigned.
'c' is never reassigned.
'o' is never reassigned.
'd' is never reassigned.
'm' is never reassigned.
'p' is never reassigned.
'g' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'let' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
's' is never reassigned.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'eg' is never reassigned.
'ej' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'let' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
'o' is never reassigned.
'd' is never reassigned.
'u' is never reassigned.
'h' is never reassigned.
'p' is never reassigned.
'g' is never reassigned.
'j' is never reassigned.
'f' is never reassigned.
'y' is never reassigned.
'A' is never reassigned.
'S' is never reassigned.
'z' is never reassigned.
'P' is never reassigned.
'q' is never reassigned.
'T' is never reassigned.
'E' is never reassigned.
'R' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'let' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
'I' is never reassigned.
'V' is never reassigned.
'M' is never reassigned.
'B' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
't' is never reassigned.
'n' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
'e' is never reassigned.
's' is never reassigned.
't' is never reassigned.
'r' is never reassigned.
'i' is never reassigned.
'c' is never reassigned.
'o' is never reassigned.
'd' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'e' is never reassigned.
't' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'u' is never reassigned.
'p' is never reassigned.
'g' is never reassigned.
'j' is never reassigned.
'f' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares a variable that is only assigned once.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'let' instead.
(lint/style/noVar)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
[error] 1-1: This let declares some variables that are only assigned once.
'e' is never reassigned.
's' is never reassigned.
't' is never reassigned.
'u' is never reassigned.
'h' is never reassigned.
'p' is never reassigned.
'g' is never reassigned.
'j' is never reassigned.
'f' is never reassigned.
'v' is never reassigned.
'y' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'b' is never reassigned.
'N' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'e' is never reassigned.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: This let declares some variables that are only assigned once.
'e' is never reassigned.
's' is never reassigned.
Safe fix: Use const instead.
(lint/style/useConst)
[error] 1-1: Use let or const instead of var.
A variable declared with var is accessible in the whole body of the function. Thus, the variable can be accessed before its initialization and outside the block where it is declared.
See MDN web docs for more details.
Unsafe fix: Use 'const' instead.
(lint/style/noVar)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)
- GitHub Check: Graphite / mergeability_check
- GitHub Check: Graphite / mergeability_check
🔇 Additional comments (49)
ui/app/plugins/page.tsx (2)
107-107: LGTM - Consistent layout cleanupRemoving padding from the container aligns with the broader UI layout standardization mentioned in the AI summary. This change is consistent with similar padding adjustments made across other UI pages.
357-357: LGTM - Gradient color updateThe change from blue to green gradient (
to-blue-600/5→to-green-600/5) in the Community & Resources section appears to be part of a design update. The change is safe and maintains the same gradient opacity.ui/app/layout.tsx (1)
35-35: LGTM - Consistent bottom padding additionAdding
pb-12to the main element provides consistent bottom spacing across the application. This change aligns with the broader UI layout standardization mentioned in the PR context.ui/lib/types/config.ts (1)
120-120: LGTM - Well-defined configuration propertyThe addition of
log_queue_size?: number;to theCoreConfiginterface properly supports the new configurable logging queue size feature. The optional nature ensures backward compatibility, and the number type is appropriate for queue size configuration..github/workflows/transport-ci.yml (1)
226-226: LGTM - Improved git staging scopeChanging from
git add .togit add transports/uiis a good improvement that makes the workflow more precise and prevents accidental commits of unrelated changes. This aligns with the job's specific purpose of updating transport UI files.ui/components/config/providers-list.tsx (1)
100-100: LGTM - Correct table column spanUpdating
colSpanfrom 5 to 6 correctly matches the number of columns in the table header (Provider, Concurrency, Buffer Size, Max Retries, API Keys, Actions). This ensures the "No providers found" message spans the entire table width properly.ui/app/docs/page.tsx (1)
60-60: LGTM - Consistent styling update.The padding removal aligns with the broader UI styling updates across multiple pages in this PR.
transports/bifrost-http/main.go (1)
299-299: LGTM - Proper implementation of configurable log queue size.This change correctly replaces the hardcoded value with a configurable parameter from the client configuration, enabling dynamic adjustment of the logging queue size.
transports/bifrost-http/handlers/mcp.go (1)
155-159: LGTM - Proper configuration persistence implementation.The consistent pattern of saving configuration immediately after each MCP client operation ensures data persistence and provides appropriate error handling. This prevents scenarios where operations appear successful but aren't actually persisted.
Also applies to: 189-193, 214-218
transports/bifrost-http/handlers/providers.go (3)
203-207: LGTM! Immediate configuration persistence after provider addition.The addition of
SaveConfig()with proper error handling ensures that provider additions are persisted immediately, preventing configuration loss in case of unexpected shutdowns.
349-353: LGTM! Consistent configuration persistence after provider updates.The implementation follows the same pattern as the AddProvider handler, ensuring configuration changes are saved immediately after updates.
390-394: LGTM! Configuration persistence after provider deletion.The SaveConfig() call ensures that provider deletions are persisted immediately, maintaining consistency with the other provider operations.
core/bifrost.go (1)
571-577: LGTM! Lazy initialization enables dynamic MCP client management.The lazy initialization approach allows MCP clients to be added even when the MCP manager wasn't configured at startup. The manager is initialized with the same structure as in the constructor, maintaining consistency.
ui/app/config/page.tsx (1)
7-7: LGTM! UI simplification aligns with automatic configuration persistence.The removal of the save button and handler is consistent with the backend changes where configuration is now automatically saved after each operation. This improves the user experience by eliminating manual save steps.
Also applies to: 71-74
ui/lib/api.ts (1)
96-103: LGTM! New API method for monitoring dropped log requests.The
getDroppedRequestsmethod follows the established pattern for API methods and provides valuable monitoring capabilities for tracking dropped log requests. The implementation is consistent with other service methods.transports/bifrost-http/ui/docs/index.txt (1)
19-19: Confirm stylesheet path and verify fallback behavior
- The file
transports/bifrost-http/ui/_next/static/css/04f1137b8e39b139.cssis present in the build output.- Review your HTTP-transport code (e.g. Express/static middleware or Next.js custom server in
transports/bifrost-http/ui) to ensure requests to/_next/static/css/*.cssare routed to that directory and that a missing-hash request either falls back gracefully or is handled without breaking the page.- If no wildcard/static catch-all is configured, add one or implement dynamic lookup to avoid a 404 on hash mismatch.
transports/bifrost-http/ui/index.txt (1)
18-20: Width utilityw-5xllooks customTailwind CSS ships with
max-w-5xl, notw-5xl.
If you really need a fixed width, ensure it’s defined intailwind.config.js; otherwise the class will be purged and the element will collapse towidth: auto.transports/bifrost-http/ui/404.html (1)
2-66: Same BProgress duplication caveatSee previous comment – the inline progress-bar styles are duplicated here as well.
[suggest_duplicate_comment]transports/bifrost-http/plugins/logging/main.go (8)
10-10: LGTM - Atomic import added for thread-safe counter.The
sync/atomicimport is correctly added to support the thread-safedroppedRequestscounter.
29-29: LGTM - Object index constant added.The
ObjectIndexconstant is properly defined for indexing log entries by object type.
134-134: LGTM - Thread-safe atomic counter for dropped requests.The
atomic.Int64provides thread-safe access to the dropped requests counter, which is essential given the concurrent nature of the logging plugin.
157-157: LGTM - Dynamic queue size configuration.The logging queue now uses the configurable
LogQueueSizefrom the config instead of a hardcoded value, providing better flexibility for different deployment scenarios.
283-287: LGTM - Improved ID generation logic.The logic now guarantees a unique ID is always generated upfront, then conditionally overwrites it with the result ID if available. This ensures no log entries have empty IDs while preserving the original ID when present.
315-328: LGTM - Enhanced object field handling.The code correctly sets the Object field from the result first, then falls back to the context value if needed. This provides proper object type tracking for log entries.
362-368: LGTM - Proper nil check for context.The nil check for context before extracting chat history prevents potential panics and ensures robust error handling.
385-385: LGTM - Atomic increment for dropped requests.The atomic increment correctly tracks dropped requests when the queue is full, providing valuable metrics for monitoring system performance.
transports/bifrost-http/lib/config.go (1)
12-16: LGTM - Well-documented configuration fields.The comments clearly explain the purpose of each field, including the new
LogQueueSizefield. The explanation that additional requests will be dropped when the queue is full provides important context for operators.transports/bifrost-http/ui/config/index.html (1)
1-122: LGTM - Standard asset references update.The HTML file has been updated with new CSS and JavaScript chunk references, which is typical after rebuilding the UI bundles. The asset hashes ensure proper cache invalidation.
transports/bifrost-http/ui/_next/static/chunks/812-4eac91fa641b7ecf.js (1)
1-1: LGTM - Standard minified JavaScript bundle.This is a webpack-generated minified JavaScript bundle containing the ThemeToggle component and API client code. The static analysis hints about style issues (use strict directive, var vs let/const, etc.) are typical for minified code and don't affect functionality.
transports/bifrost-http/handlers/config.go (2)
76-78: LGTM: Proper handling of LogQueueSize configuration.The LogQueueSize field is correctly handled following the same pattern as other configuration fields. The implementation properly checks for changes and updates the configuration accordingly.
Note: Unlike
DropExcessRequestswhich has a runtime method call (h.client.UpdateDropExcessRequests), the LogQueueSize change appears to be persisted but may require an application restart to take effect. Consider whether runtime application is needed for this setting.</comment_end -->
89-92: LGTM: Improved response message clarity.The response message has been appropriately updated to be more generic and informative, moving from a potentially action-specific message to a clear "Configuration updated successfully" message.
</comment_end -->
transports/bifrost-http/ui/config/index.txt (1)
1-30: LGTM!The chunk reference updates and layout adjustments are appropriate for the new UI build.
transports/bifrost-http/ui/_next/static/chunks/273-9756261fec6bc01b.js (1)
1-1: LGTM!This minified chunk correctly implements the Tooltip UI component system with proper accessibility and state management.
transports/bifrost-http/ui/_next/static/chunks/529-26467b76604e8781.js (1)
1-1: LGTM!This minified chunk properly implements UI components with accessibility features and standard patterns.
ui/components/config/core-settings-list.tsx (2)
34-44: LGTM!The useEffect properly fetches dropped requests on mount with appropriate error handling.
217-235: LGTM!The Log Queue Size configuration section is well-implemented with proper accessibility attributes and informative user feedback showing the dropped requests count.
transports/bifrost-http/plugins/logging/utils.go (6)
63-69: LGTM! Object indexing follows the established pattern.The implementation correctly indexes the Object field using the same format as other fields, enabling efficient filtering by object type.
104-202: Excellent refactoring of SearchLogs for better concurrency and statistics!The changes improve the method significantly:
- Using
RLockinstead ofLockallows concurrent searches- Collecting all results before sorting ensures consistent pagination
- The deduplication mechanism prevents duplicate entries
- Statistics calculation provides valuable insights for the UI
246-254: Object filtering correctly integrated.The implementation follows the established pattern for filter integration, properly handling the intersection logic when multiple filters are applied.
431-459: searchByObjects implementation looks good.The method correctly follows the established pattern for index-based searching, with proper deduplication and iterator management.
822-828: Good interface extension for dropped requests.The addition of
GetDroppedRequests()to the LogManager interface cleanly exposes the dropped request metric as intended by the PR.
838-840: Thread-safe implementation of GetDroppedRequests.The method correctly uses the atomic Load operation to safely return the dropped requests count.
transports/bifrost-http/lib/store.go (3)
52-57: Good refactoring: Centralized default configuration.Moving default values to a centralized
DefaultClientConfigvariable improves maintainability and ensures consistency across the codebase.
93-96: Consistent use of centralized defaults.The changes properly use the new
DefaultClientConfigvariable in both initialization paths, ensuring consistent default values throughout the application.Also applies to: 128-128
247-330: Excellent security enhancement for config persistence.The refactored
writeConfigToFilemethod now properly preserves environment variable references (e.g.,env.API_KEY) when saving configuration, preventing sensitive values from being written to disk. This is a significant security improvement.The intentional design choice to keep actual values when env vars are not found (rather than redacting) ensures round-trip fidelity when loading and saving configurations.
transports/bifrost-http/ui/_next/static/chunks/app/page-26aa3339d9cf36ab.js (1)
1-1091: Skip review of minified code.This is a compiled/minified JavaScript file generated by the build process. The static analysis warnings about code style (use strict directives, variable declarations, etc.) are not actionable since this is generated code, not source code. The actual source files should be reviewed instead.
transports/bifrost-http/ui/_next/static/chunks/app/config/page-400ac111d2c44d93.js (1)
1-1: Skip review of minified build artifactThis is a minified JavaScript build output file generated by Next.js. Build artifacts should not be reviewed for code quality. Consider reviewing the source files instead if changes to the configuration UI module need to be validated.
transports/bifrost-http/ui/_next/static/chunks/app/layout-188bea908cf68435.js (1)
1-1: Minified bundle file - no review needed.This is a minified/bundled JavaScript file generated by the build process. The static analysis warnings about code style are expected in minified code and not actionable.
transports/bifrost-http/ui/_next/static/chunks/678-56244c2aeff7b5e2.js (1)
1-1: Minified bundle file - no review needed.This is a minified/bundled JavaScript file (appears to be the Sonner toast library) generated by the build process. The static analysis warnings are expected in minified code and not actionable.
Pratham-Mishra04
force-pushed
the
07-09-fix_onsave_keys_redact_logging_and_added_configurable_logging_queue_size
branch
2 times, most recently
from
457bfe5 to
723d817
Compare
Pratham-Mishra04
force-pushed
the
07-09-fix_onsave_keys_redact_logging_and_added_configurable_logging_queue_size
branch
from
723d817 to
f4f365f
Compare
Merge activity
|
akshaydeo
changed the base branch from
07-07-feat_transport_flags_simplified_and_logs_updated
to
graphite-base/150
akshaydeo
deleted the
07-09-fix_onsave_keys_redact_logging_and_added_configurable_logging_queue_size
branch
2 participants
No description provided.