Skip to content

Conversation

@NotNite
Copy link
Member

@NotNite NotNite commented Nov 25, 2025

The primary motivation for this is loading libdiscoreWasmFetch along with web, as well as cleaning up Webpack patching code in general. We have to support multiple requires existing, so the main require in web gets marked with a special field. There's also multiple modules, some with conflicting IDs(!!!), so I'm not sure how that behaves. I do not know if patching modules in the other scripts works.

I haven't tested this very well, so feedback is appreciated! Browser support isn't done yet, and noTrack will also need to be updated for the libdiscore launch signature now that it's actually being evaluated.

The primary motivation for this is loading libdiscoreWasmFetch along
with web, as well as cleaning up Webpack patching code in general. We
have to support *multiple requires* existing, so the main require in
web gets marked with a special field. There's also multiple modules,
some with conflicting IDs(!!!), so I'm not sure how that behaves. I do
not know if patching modules in the other scripts works.

I haven't tested this very well, so feedback is appreciated! Browser
support isn't done yet, and noTrack will also need to be updated for
the libdiscore launch signature now that it's actually being evaluated.
@NotNite NotNite added enhancement New feature or request core This issue is related to moonlight's core labels Nov 25, 2025
@NotNite NotNite requested a review from Cynosphere November 25, 2025 20:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

core This issue is related to moonlight's core enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants