Skip to content

Fix lovable plugin source path to use explicit relative path - #3

Open
justhamade wants to merge 1 commit into
10K-Digital:mainfrom
justhamade:main
Open

Fix lovable plugin source path to use explicit relative path#3
justhamade wants to merge 1 commit into
10K-Digital:mainfrom
justhamade:main

Conversation

@justhamade

Copy link
Copy Markdown

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.

  ⎿  Error: Failed to parse marketplace file at ~/.claude/plugins/marketplaces/10K-Digital-lovable-claude-code/.claude-plugin/marketplace.json: Invalid schema:
     ~/.claude/plugins/marketplaces/10K-Digital-lovable-claude-code/.claude-plugin/marketplace.json plugins.0.source: Invalid input

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant