Cannot find module 'node_modules/replicate/lib/errors.js'

[zeke]

Seeing this error in the server logs from replicate/scribble-diffusion#46

I thought this was maybe a files thing in package.json, but the file is there: https://unpkg.com/browse/replicate@0.5.0/lib/

2023-03-13T19:06:25.472Z  2023-03-13T19:06:26.632Z	4c7e6aa0-c7c4-4f91-b02c-e0f56b9f7e38	ERROR	Error [ERR_MODULE_NOT_FOUND]: Cannot find module '/var/task/node_modules/replicate/lib/errors.js' imported from /var/task/node_modules/replicate/lib/ReplicateClient.js
2023-03-13T19:06:25.472Z      at new NodeError (node:internal/errors:400:5)
2023-03-13T19:06:25.472Z      at finalizeResolution (node:internal/modules/esm/resolve:331:11)
2023-03-13T19:06:25.472Z      at moduleResolve (node:internal/modules/esm/resolve:994:10)
2023-03-13T19:06:25.472Z      at moduleResolveWithNodePath (node:internal/modules/esm/resolve:938:12)
2023-03-13T19:06:25.472Z      at defaultResolve (node:internal/modules/esm/resolve:1202:79)
2023-03-13T19:06:25.472Z      at nextResolve (node:internal/modules/esm/loader:163:28)
2023-03-13T19:06:25.472Z      at ESMLoader.resolve (node:internal/modules/esm/loader:842:30)
2023-03-13T19:06:25.472Z      at ESMLoader.getModuleJob (node:internal/modules/esm/loader:424:18)
2023-03-13T19:06:25.472Z      at ModuleWrap.<anonymous> (node:internal/modules/esm/module_job:77:40)
2023-03-13T19:06:25.472Z      at link (node:internal/modules/esm/module_job:76:36) {
2023-03-13T19:06:25.472Z    code: 'ERR_MODULE_NOT_FOUND'
2023-03-13T19:06:25.472Z  }

[zeke]

cc @erbridge any idea what's up here?

[zeke]

Is there any chance it's a caching issue where some filenames have changed case?

[erbridge]

Is there any chance it's a caching issue where some filenames have changed case?

I doubt it for two reasons: errors.js was always lowercase, and Vercel is almost certainly running a case-sensitive filesystem.

[erbridge]

I'm not sure what's going on here. The fact that it's loaded ReplicateClient.js implies that the import syntax is fine and it's loading ESM ok, so it feels like this is a case of the file being missing maybe, but I'm not sure why it would be missing.

[gr2m]

How can I replicate the above error?

[zeke]

1. Clone this PR: Use replicate npm package scribble-diffusion#46
2. Run npx vercel to push your own copy

[zeke]

Or do something like this from scratch:

npx create-next-app my-app
cd my app
npm install replicate
// write some code
vercel

[gr2m]

Can you reproduce the problem with just npm run build? I'm not able to reproduce, not locally, not when deployed to production. Maybe let's pair on it?

[zeke]

Paired on this with @gr2m for a bit but didn't get anywhere.

Opened an issue upstream here: vercel/next.js#47380

[zeke]

Resolved by #25 (comment)

[gr2m]

Resolved by #25 (comment)

can you elaborate on what the problem was / how it was resolved?

[zeke]

Apparently it was the import assertion, as you suspected: vercel/next.js#47380 (comment) -- you and I tried removing that but we must not have tested it properly.

Anyway that code path doesn't exist any more since the client code was completely rewritten in #25