Fix lovable plugin source path to use explicit relative path - #3
Open
justhamade wants to merge 1 commit into
Open
Fix lovable plugin source path to use explicit relative path#3justhamade wants to merge 1 commit into
justhamade wants to merge 1 commit into
Conversation
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
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
Updates the source path for the lovable plugin in .claude-plugin/marketplace.json from "plugins/lovable/" to "./plugins/lovable/" to use an explicit relative path reference.
What Changed
File: .claude-plugin/marketplace.json
The source field for the lovable plugin entry was updated:
Before:
"source": "plugins/lovable/"After:
"source": "./plugins/lovable/"Why
The addition of ./ makes the path explicitly relative to the current directory, rather than relying on implicit resolution. This is a more conventional and reliable way to reference relative paths, as some path resolution logic may interpret a bare path like plugins/lovable/ differently depending on the working directory or runtime context. Using ./ removes this ambiguity and ensures the plugin is always resolved relative to the location of the config file.
Impact
No functional changes to the plugin itself
No changes to plugin behavior, version, or metadata
Minimal risk — this is a config-only, one-line change