What compatibility issues were found on Vercel Edge?
The saved analysis assesses redis@6.3.0 as potential issue for Vercel Edge. Review the findings and coverage below; this is not a runtime execution test.
Potential issue
Not scored · low confidence
No detected blocker within scan limits does not mean verified execution. Scores are heuristics, not probabilities.
Score withheld: inspection is incomplete or runtime support is unresolved.
Assessment assumptions
Broad runtime profile; no exact runtime version, platform, or deployment configuration was selected.
Package declares Node.js >= 20.0.0. This constraint has not been checked against a selected version and does not declare Bun or Deno support.
Vercel Edge is distinct from Vercel Node.js Functions; Node native addons and runtime eval are unavailable.
import
Potential issue
execute
Unknown
APIs
Unknown
SSR
Unknown
6 packages and 202 files scanned. At least one file scan was incomplete. Coverage describes the inspected scope, not every possible code path.
FILE AND DEPENDENCY EVIDENCE
6 findings to review
1. CommonJS entry
Potential issue
Selected entry appears to use CommonJS; this runtime may need bundler interop
Source excerpt
No source excerpt was saved for this finding. Older reports, manifest or binary signals, and inspection failures may not have a source location.
Suggested next steps
Review the package's module entry points
Check the package's documented exports for a supported ESM or browser entry. Import public exported paths rather than guessing internal file paths.
If only CommonJS is available, test your build tool's CommonJS conversion and interop behavior. Changing your own package to type: module does not convert a dependency's CommonJS source.
Rebuild and exercise the affected import and operation in your exact runtime, version, and deployment configuration. These suggestions are not a tested fix.
Selected entry appears to use CommonJS; this runtime may need bundler interop
Source excerpt
No source excerpt was saved for this finding. Older reports, manifest or binary signals, and inspection failures may not have a source location.
Suggested next steps
Review the package's module entry points
First trace whether this file is reachable from the entry point your application uses. The finding may be outside the executed code path.
Check the package's documented exports for a supported ESM or browser entry. Import public exported paths rather than guessing internal file paths.
If only CommonJS is available, test your build tool's CommonJS conversion and interop behavior. Changing your own package to type: module does not convert a dependency's CommonJS source.
This finding is in a transitive dependency. Prefer upgrading/configuring its parent package or proposing an upstream fix over editing installed node_modules.
Rebuild and exercise the affected import and operation in your exact runtime, version, and deployment configuration. These suggestions are not a tested fix.
Selected entry appears to use CommonJS; this runtime may need bundler interop
Source excerpt
No source excerpt was saved for this finding. Older reports, manifest or binary signals, and inspection failures may not have a source location.
Suggested next steps
Review the package's module entry points
First trace whether this file is reachable from the entry point your application uses. The finding may be outside the executed code path.
Check the package's documented exports for a supported ESM or browser entry. Import public exported paths rather than guessing internal file paths.
If only CommonJS is available, test your build tool's CommonJS conversion and interop behavior. Changing your own package to type: module does not convert a dependency's CommonJS source.
This finding is in a transitive dependency. Prefer upgrading/configuring its parent package or proposing an upstream fix over editing installed node_modules.
Rebuild and exercise the affected import and operation in your exact runtime, version, and deployment configuration. These suggestions are not a tested fix.
Selected entry appears to use CommonJS; this runtime may need bundler interop
Source excerpt
No source excerpt was saved for this finding. Older reports, manifest or binary signals, and inspection failures may not have a source location.
Suggested next steps
Review the package's module entry points
First trace whether this file is reachable from the entry point your application uses. The finding may be outside the executed code path.
Check the package's documented exports for a supported ESM or browser entry. Import public exported paths rather than guessing internal file paths.
If only CommonJS is available, test your build tool's CommonJS conversion and interop behavior. Changing your own package to type: module does not convert a dependency's CommonJS source.
This finding is in a transitive dependency. Prefer upgrading/configuring its parent package or proposing an upstream fix over editing installed node_modules.
Rebuild and exercise the affected import and operation in your exact runtime, version, and deployment configuration. These suggestions are not a tested fix.
Selected entry appears to use CommonJS; this runtime may need bundler interop
Source excerpt
No source excerpt was saved for this finding. Older reports, manifest or binary signals, and inspection failures may not have a source location.
Suggested next steps
Review the package's module entry points
First trace whether this file is reachable from the entry point your application uses. The finding may be outside the executed code path.
Check the package's documented exports for a supported ESM or browser entry. Import public exported paths rather than guessing internal file paths.
If only CommonJS is available, test your build tool's CommonJS conversion and interop behavior. Changing your own package to type: module does not convert a dependency's CommonJS source.
This finding is in a transitive dependency. Prefer upgrading/configuring its parent package or proposing an upstream fix over editing installed node_modules.
Rebuild and exercise the affected import and operation in your exact runtime, version, and deployment configuration. These suggestions are not a tested fix.
Selected entry appears to use CommonJS; this runtime may need bundler interop
Source excerpt
No source excerpt was saved for this finding. Older reports, manifest or binary signals, and inspection failures may not have a source location.
Suggested next steps
Review the package's module entry points
First trace whether this file is reachable from the entry point your application uses. The finding may be outside the executed code path.
Check the package's documented exports for a supported ESM or browser entry. Import public exported paths rather than guessing internal file paths.
If only CommonJS is available, test your build tool's CommonJS conversion and interop behavior. Changing your own package to type: module does not convert a dependency's CommonJS source.
This finding is in a transitive dependency. Prefer upgrading/configuring its parent package or proposing an upstream fix over editing installed node_modules.
Rebuild and exercise the affected import and operation in your exact runtime, version, and deployment configuration. These suggestions are not a tested fix.
This report preserves the findings as of October 12, 2026 at 9:42 AM UTC. It may use older analysis rules (analysis version 4). Package code was not executed. Runtime versions, flags, bundlers, and operating systems can change actual compatibility.
Reachability is approximate. Optional dependencies, generated code, dynamic imports, and incomplete scans can cause false positives or missed issues. A green assessment means no blocker was found within the inspected scope. The score is a heuristic, not a probability.