Add support for local parcel plugins #8925
Merged
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
Benchmark ResultsKitchen Sink ✅
Timings
Cold Bundles
Cached Bundles
React HackerNews ✅
Timings
Cold BundlesNo bundle changes detected. Cached BundlesNo bundle changes detected. AtlasKit Editor ✅
Timings
Cold Bundles
Cached BundlesNo bundle changes detected. Three.js ✅
Timings
Cold BundlesNo bundle changes detected. Cached BundlesNo bundle changes detected. |
mischnic
approved these changes
Apr 24, 2023
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.
Closes #4321.
This adds support for referencing local Parcel plugins in
.parcelrcconfigs using relative paths. This has been raised a few times before (e.g. #3397 and #4321) as a pain point when developing plugins that you want to test in a local project. It is already possible to load local plugins that aren't published to npm by using npm/yarn workspaces or thelink:protocol in yarn, but if you aren't already using these systems it is a bit to set up. With this PR, you can reference a plugin using a relative path instead.While local plugins are supported in apps, config packages (e.g.
parcel-config-foo) cannot reference local plugins. This is so that published plugins can always be used independently of any config packages, which are simply shortcuts for using multiple plugins. This is important so plugins can be used separately or reordered as needed by the user, rather than stuck in the order the config defined them.