Allow the resolver to have a relative path so it can be project specific #312
Conversation
This file contains 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
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.
I've been trying to use the webpack plugin but I have too many complexities
We have 4 builds, with 4 slightly different webpack configurations - files are spread between the configurations with different aliases for each. We use NormalModuleReplacementPlugin to do some aliasing on the fly (btw I am not proud of this, I inherited it).
Its been alot easier to write a custom resolver for our project - moving code from the webpack config to a common place and referencing it from the webpack config and our resolver.
Would you accept this change? I can add documentation if needed & accepted.