S.R.InteropServices.JavaScript is part of the shared framework but doesn't have a ref assembly

[ViktorHofer]

System.Runtime.InteropServices.JavaScript is currently declared as part of the shared framework but doesn't have a reference assembly. As the project isn't OOB either, there is currently no way for a customer to reference the library besides directly referencing the implementation one from the shared framework directory.

Is the omission of a reference assembly intentional?

cc @kjpou1 @marek-safar @ericstj

Tagging subscribers to this area: @safern, @ViktorHofer
Notify danmosemsft if you want to be subscribed.

[jkotas]

This is internal library, for internal consumption only for now.

See #35573 (comment)

[safern]

So then we should close the issue as by design?

[ericstj]

Do we want to change the name to System.Private to indicate it is internal only? We've done so elsewhere (CoreLib, URI, XML).

[marek-safar]

Do we want to change the name to System.Private to indicate it is internal only?

Is it worth it? We'll probably make the library public in the future (e.g. .NET7).

[stephentoub]

Is it worth it? We'll probably make the library public in the future (e.g. .NET7).

I would think so. That's two releases away, including an LTS.

[ericstj]

Do we think its worth the risk to change the name at this point in the release? What could break if we change this name? cc @steveisok @akoeplinger

[lewing]

Nothing external should break at this point, the name is already different than the 3.2 counterpart. The name is referenced in a couple of places by the js internally, and at least one test helper.

[steveisok]

I think this is pretty low risk and we should be able to change it.