Is typescript-eslint open to include a config option like {from: "package", name: "Foo", package: "data:text/javascript, export class Foo {};"}, or with the other specifiers(like file:), in the eslint config file ?

Definitely not, no.
First of all there's already the ability to select specific files via the file type. So why would we allow file:// specifiers in the package type?

Please see the rule docs.
https://typescript-eslint.io/rules/prefer-readonly-parameter-types/#options

As for data:text/JavaScript - what does that even mean? That you would just execute random JS? It's honestly non-sensical when the option is looking for an npm package name.

Thanks for the quick answer, so its only node: which will be supported in the package option ?

This isn't an enhancement - it's a bug.

We don't handle the node special scoped packages in this function
https://github.com/typescript-eslint/typescript-eslint/blob/main/packages%2Ftype-utils%2Fsrc%2FTypeOrValueSpecifier.ts#L155-L172

Which means we're looking for @types/node:events.
I'd guess a lot of the node internal packages might fail that lookup given that events maps to @types/node?

We don't handle the node special scoped packages in this function

Yes, I also tried to solve it here in a rough way.

So, the only URL scheme which is allowed, is node: right ?

What about bun: prefixed packages? https://bun.sh/docs/runtime/bun-apis

Whilst technically they are URL schemes I don't think we should be thinking about then like that.

Instead we should just be treating them as a special namespace case. Eg node:foo maps to @types/node because we see the colon, split it, and take the first part as the namespace to use.

As for data:text/JavaScript - what does that even mean? That you would just execute random JS? It's honestly non-sensical when the option is looking for an npm package name.

Off-topic but here's a trivia:

import { Foo } from "data:text/javascript, export class Foo {};"

console.log(new Foo());

This is valid code :)