Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WiP PR: Preparing to land multiContext Unified customResolver Support modules #8006

Closed
2 of 3 tasks
Tracked by #2
lemanschik opened this issue Nov 29, 2022 · 0 comments
Closed
2 of 3 tasks
Tracked by #2

Comments

@lemanschik
Copy link

Issue Type

  • Bug Report

  • Feature Implementation

  • Successfully reproduced against the latest version of NW.js?

Please use our mailing list or Gitter chatroom to ask questions. The issue tracker is only for bugs and feature requests, in English only. Please note that issues without a repro or code snippet are less likely to be resolved.

Current/Missing Behavior

This adds the missing shared resolve algos between ESM CJS and also in indipendent Contexts so you can use
the same specifiers and always resolve them with a consistent method this is part of a big engineering effort

timeline till production ready next 6 month but starting experimenting and integration so it is ready.

Expected/Proposed Behavior

This implements a shared resolve worker like a service worker that indeed can be used also for your service worker and is even designed for that.

Additional Info

  • Operating System: all
  • NW.js Version: all includes backports node 18
  • Repro Link:
  • Code snippet:
  • Crash report:
@lemanschik lemanschik changed the title WiP PR: Preparing to land customResolver Support modules WiP PR: Preparing to land multiContext Unified customResolver Support modules Nov 29, 2022
@ayushmanchhabra ayushmanchhabra closed this as not planned Won't fix, can't repro, duplicate, stale Mar 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants