Repository navigation
require function is used in a way in which dependencies cannot be statically extracted #345
Description
Hi there, I have a Next.js project with "replicate": "^1.0.1", and this code:
import Replicate from 'replicate'
export const replicate = new Replicate({
auth: process.env.REPLICATE_API_KEY
})
I'm seeing this warning during local development:
- warn ../../node_modules/replicate/lib/util.js
Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
Import trace for requested module:
../../node_modules/replicate/lib/util.js
../../node_modules/replicate/index.js
./src/lib/replicate.ts
./src/app/api/cloud/image/route.ts
from const ApiError = require("./error"); in node_modules/replicate/lib/util.js.
Any suggestions on preventing this?
Metadata
Metadata
Assignees
Labels
No labels
Activity
ntgussoni commentedon May 23, 2025
I'm having the same issues as well, let me know if you guys need help testing it
EDIT: v1.1.0-0
This one removes the warning
gianpaj commentedon Jul 2, 2025
when is this being released? we're in July 🙃
saifookhan commentedon Aug 18, 2025
Pls take out time for this. :)