Skip to content

require function is used in a way in which dependencies cannot be statically extracted #345

@jparismorgan

Description

@jparismorgan

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
No labels

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions