⌁runtimereadySTATIC COMPATIBILITY INTELLIGENCE
SAVED COMPATIBILITY REPORT

slick@1.12.2
on Cloudflare Workers

Analyzed · Static analysis only

A saved snapshot, not a live compatibility guarantee. Opening this page does not run a scan.

Analyze a package ↗Methodology and limitations

What compatibility issues were found on Cloudflare Workers?

The saved analysis assesses slick@1.12.2 as potential issue for Cloudflare Workers. Review the findings and coverage below; this is not a runtime execution test.

Potential issue

91/100 · medium confidence

No detected blocker within scan limits does not mean verified execution. Scores are heuristics, not probabilities.

Assessment assumptions
  • Broad runtime profile; no exact runtime version, platform, or deployment configuration was selected.
  • Package declares Node.js *. This constraint has not been checked against a selected version and does not declare Bun or Deno support.
  • Node API support depends on Workers compatibility settings and the specific operation. Native Node addons and runtime eval are unavailable in this profile.
import
Potential issue
execute
Likely compatible
APIs
Likely compatible
SSR
Likely compatible

1 packages and 3 files scanned. Coverage describes the inspected scope, not every possible code path.

FILE AND DEPENDENCY EVIDENCE

1 finding 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
  1. Check the package's documented exports for a supported ESM or browser entry. Import public exported paths rather than guessing internal file paths.
  2. 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.
  3. Check your Workers compatibility date and Node API support before making changes. This analyzer uses a coarse profile and does not model every compatibility flag or API implementation.

Rebuild and exercise the affected import and operation in your exact runtime, version, and deployment configuration. These suggestions are not a tested fix.

File
index.js
Dependency path
slick@1.12.2
Entry points
index.js
Dimension
import
Reachability
selected entry
Confidence
medium · static

How to use this report

This report preserves the findings as of September 30, 2026 at 6:24 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.

Read all limitations ↗