Make disk- blob transferable

[jimmywarting]

What is the problem this feature will solve?

I notice that Blob's transfered over workers aren't readable at all.

• it only applies to blobs coming from fs.openAsBlob
• in-memory constructed blobs works fine.

Right now they throw an error when trying to send them over.

mini repro:

import { Worker } from 'worker_threads'
const worker = new Worker('./worker.js')
worker.once('message', blob => {
  // Should be fine to do this as well
  blob.text()
})

// worker.js
import { parentPort } from 'node:worker_threads'
import { openAsBlob } from 'node:fs'

const blob = await openAsBlob(new URL(import.meta.url))
parentPort.postMessage(blob)

If a blob originates from a worker thread and is being sent to the main thread over postMessage, then it should still work OK to read the blob even if the worker is terminated.

originally posted by @jimmywarting in #45258 (comment)

What is the feature you are proposing to solve the problem?

Spec issue

What alternatives have you considered?

No response

[aduh95]

const blob = await openAsBlob(import.meta.url.slice(7)) // file:// doesn't work

I think you have to do const blob = await openAsBlob(new URL(import.meta.url)), using slice is a bad idea.

[jimmywarting]

Good suggestion, gona refactor my own code. 👍

[github-actions]

There has been no activity on this feature request for 5 months and it is unlikely to be implemented. It will be closed 6 months after the last non-automated comment.

For more information on how the project manages feature requests, please consult the feature request management document.

[jimmywarting]

still an issue...

[github-actions]

There has been no activity on this feature request for 5 months. To help maintain relevant open issues, please add the never-stale Mark issue so that it is never considered stale label or close this issue if it should be closed. If not, the issue will be automatically closed 6 months after the last non-automated comment.
For more information on how the project manages feature requests, please consult the feature request management document.

[github-actions]

There has been no activity on this feature request and it is being closed. If you feel closing this issue is not the right thing to do, please leave a comment.

For more information on how the project manages feature requests, please consult the feature request management document.