Share cache object between require function created with the alias method #36
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
In the current implementation the "requireFrom" method creates a new private cache object. It leads to loading of multiple versions of the same library.
Example
Example of method declarations in UMD files:
Usage of these libraries:
Problem: the same library "counter.js" was loaded twice even if it was resolved to the same final URL.
A real use case of this problem:
There is a main application and some modules are loaded separately to extend functionality of the main app. All of them use the same shared d3 require function to load UMD libraries. To resolve paths to a specific library the main application as well as extensions use the "require.alias". It leads to exceptions because each of them create a separate instance of the same module. (like react, react-dom etc)
Solution
Use the cache object as an additional parameter in the requireFrom method.