docs: Update resource-fallback plugin entry with GitHub link#8274
Open
ben-lau wants to merge 2 commits into
Open
docs: Update resource-fallback plugin entry with GitHub link#8274ben-lau wants to merge 2 commits into
ben-lau wants to merge 2 commits into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
Summary
Follow-up to #8267 — added the missing author GitHub link for
@resource-fallback/webpack-plugin.The plugin entry was added in the previous PR but the author link was omitted. This PR adds it to keep consistent with other entries in the list.
docs — adding a third-party plugin entry to the plugins list.
Did you add tests for your changes?
N/A — documentation-only change (one line added to the plugin list).
Does this PR introduce a breaking change?
No.
If relevant, what needs to be documented once your changes are merged or what have you already documented?
No further documentation needed. The plugin has its own documentation site.
Use of AI
No. This PR was written manually by the plugin author.