Jump to root require if module is not found from the local map#9
Merged
1 commit merged intobrowserify:masterfrom Mar 24, 2013
Merged
Jump to root require if module is not found from the local map#91 commit merged intobrowserify:masterfrom
1 commit merged intobrowserify:masterfrom
Conversation
With this it shouldn't matter in which order multiple bundles are added to the dom. If local require fails to find the module from its map it jumps the to current root require in the global scope and works its way back down from there. Should fix browserify/browserify#341
Contributor
Author
|
I've updated the pull request. It's now simpler and all tests pass on browser-pack and browserify modules. |
|
With this patch head.js can natively load browserify bundles? If so that is really impressive. |
Contributor
Author
|
Yes :) or with any script loader |
ghost
merged commit 
This pull request was closed.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Ok, another take on browserify/browserify#341
With this it shouldn't matter in which order multiple bundles are added
to the dom. If local require fails to find the module from its map it
jumps the to current root require in the global scope and works its way
back down from there.
Example usage https://github.com/epeli/lazy-browserify/blob/master/both.js