Update to use fully resolved paths for babel plugins #209
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.
Babel will resolve plugins relative to the cwd (this may be a slight simplification). This usually works as expected, however, I have stumbled on an edge case when using a monorepo structure with abstracted build configuration.
In this case, babel is unable to resolve the plugins which live within the
node_modules
directory of the symlinked package,shared-build
.While slightly more verbose, we can bypass this problem by utilizing the full paths to the plugins that are installed relative to this package.