but is referring to its sub-dependency with a different path
An example is certain plugins based on jqueryUI, which used to be part of a jquery bundle with exports named like "jquery.ui.widget", but because we're modern and use NPM modules now, that module dependency would now be "jquery-ui/ui/widget". The "map" config option in Steal may experience a race condition where it misunderstands that these two module references should be normalized together.
To fix this, we introduce "importRewrites", a package-namespaced mapping that directly translates the import name a module requires into a different import name.
and then steal will behave as if any module in some-old-jquery-ui-widget's source tree imported "jquery-ui/ui/widget" if that module imports "jquery.ui.widget".
This is a special case for when:
An example is certain plugins based on jqueryUI, which used to be part of a jquery bundle with exports named like "jquery.ui.widget", but because we're modern and use NPM modules now, that module dependency would now be "jquery-ui/ui/widget". The "map" config option in Steal may experience a race condition where it misunderstands that these two module references should be normalized together.
To fix this, we introduce "importRewrites", a package-namespaced mapping that directly translates the import name a module requires into a different import name.
In package.json this looks like:
and then steal will behave as if any module in some-old-jquery-ui-widget's source tree imported "jquery-ui/ui/widget" if that module imports "jquery.ui.widget".