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
Only needs request(), given a bar import ("x") (and a relative file?), it will check /modules/timestamps[x]/x...
If the algorithm is check loader, if failed (404), fall back to next, then we simply have to put our loader at the end of the list.
It will first check node_modules/x (and possibly correctly find it in the case of bundled dependencies, or even resolved dependencies), and keep going upwards. Again, it's "base" path will already be in a timestamp path if it is a dependency, and if it is top level, it will immediately fail since there is nothing in node_modules.
So, an import from the top level, immediately fails on the normal loader, then it falls into our loader, which redirects to the timestamped path, at which point it uses the normal node absolute path file loader.
The text was updated successfully, but these errors were encountered:
So, an import from the top level, immediately fails on the normal loader, then it falls into our loader, which redirects to the timestamped path, at which point it uses the normal node absolute path file loader.
The text was updated successfully, but these errors were encountered: