[ERROR] Could not resolve "fs/promises"

What version of Remix are you using?

Remix - Cloudflare workers @ latest

Steps to Reproduce

Hello, i’m trying to learn react and remix altogheter, I came across an error, trying to pass a multipart form from frontend to backend via form and action. As i try to import unstable_createMemoryUploadHandler it throws an error related to FS/Promises

17 │ var promises = require('fs/promises'); 

The package "fs/promises" wasn't found on the file system but is built into node. 
Are you trying to bundle for node? 
You can use "platform: 'node'" to do that, which will remove this error.


Build failed with 1 error:
node_modules/@remix-run/node/upload/fileUploadHandler.js:17:23: ERROR: Could not resolve "fs/promises"

So basically I don’t understand if I’m doing something wrong. As I could understand on cloudflare workers I have to rely on their services, and so no storage and so no fileUpload, i’m trying to use the stream to get the file posted with the request to pass it to supabase via service role key.

Any idea what am I missing?

Expected Behavior

Should create a uploaderHandle to pass to

export const action: ActionFunction = async ({
  request,
}) => {
  const uploadHandler = unstable_createMemoryUploadHandler({
    maxFileSize: 500_000,
  });
  const formData = await unstable_parseMultipartFormData(
    request,
    uploadHandler
  );

  const file = formData.get("avatar");

  // file is a "File" (https://mdn.io/File) polyfilled for node
  // ... etc

Actual Behavior

17 │ var promises = require('fs/promises'); 

The package "fs/promises" wasn't found on the file system but is built into node. 
Are you trying to bundle for node? 
You can use "platform: 'node'" to do that, which will remove this error.


Build failed with 1 error:
node_modules/@remix-run/node/upload/fileUploadHandler.js:17:23: ERROR: Could not resolve "fs/promises"

[mxp-qk]

Same issu for me, in my case this is due to importing anything (redirect, json) from @remix-run/node in a yarn PNP monorepo. I didn’t find a way around it but to use new Response (...)

[mcmxcdev]

Works for me with the adjustments I mentioned above @mcmxcdev +1

Thank you Tim, but we already use the new imports rather than the deprecated ones. We also don’t use fs-extra, so no clue where to start.

One way to solve this would be to patch away the line failing the CI run with https://www.npmjs.com/package/patch-package I guess.