Avoid to append ./ automatically#32
Open
0cv wants to merge 1 commit intoTheLarkInn:masterfrom
0cv:master
Open
Conversation
Currently, due to `./` being appended automatically to any file, it's not possible to resolve node_modules for example.
Owner
|
See #31 (comment) This needs to be approached in a creative manner that still stands true to the intentional design of the loader. |
Author
|
eventually it should check whether the file exists in the current path, and if not resolve the node_modules... But it's error prone if 2 files / modules come with the same name. |
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
2 participants
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.
Currently, due to
./being appended automatically to any file, it's not possible to resolve node_modules for example.Will solve #31
Could break other projects which are not appending
./for resolving local files.