You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
The text was updated successfully, but these errors were encountered:
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
Issue Type
Bug Report
Feature Implementation
Successfully reproduced against the latest version of NW.js?
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
The text was updated successfully, but these errors were encountered: