Ship only the plugin's own files to users, not the repo's development tooling
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
Research direction
Start by inspecting the repository layout and how the self-hosted marketplace and plugin directory package the plugin. Identify the checks and tests that validate an installed plugin, then run them against the reduced install contents. Done means a fresh install from both sources contains the listed runtime files, and all checks and tests still pass against that package.
Written by the indexing model from the issue text.
Description
Problem
The plugin's source is the whole repository, so every install copies the development tooling along with the plugin: package.json, the lockfile, test and CI scripts, GitHub workflows, and contributor docs. None of it is used at runtime. It enlarges every install, and it puts files in front of directory reviewers and security scanners that have nothing to do with what the plugin does on a user's machine.
Acceptance criteria
- A fresh install of the plugin contains only what it uses at runtime: the manifest, skills, MCP config, launch script, icon, README, and license.
- Every check and test still runs against the plugin as users receive it.
- Installs from the self-hosted marketplace and the plugin directory both receive the reduced set.
Non-goals
- Changing what the plugin does at runtime.
- Changing how releases are cut.
Affected contracts
What a plugin install contains.
- Dominant language
- Shell
- Stars
- 3
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from dequelabs/axe-accessibility
-
Difficulty 2/5 1-3 hours Newbie friendliness 69/100
-
Difficulty 1/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
dequelabs/axe-accessibility#9 · 2 comments · 1 reaction · 1 assignee ·
-
Difficulty 4/5 3-5 days Newbie friendliness 57/100
-
Difficulty 3/5 1-2 days Newbie friendliness 66/100
All issues in dequelabs/axe-accessibility
Similar issues
-
bug report-to-upstream
Difficulty 1/5 1-3 hours Newbie friendliness 78/100
flatpark/flatpark#1424 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
[bug] Docker Compose version check in auto-install.sh fails on non-Debian systems (dpkg not found)Possibly taken @shaneintentionboi06 claimed this today. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
openwisp/docker-openwisp#771 ·
Maintainers usually reply within 1 day
-
needs-you
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
catalystneuro/encore#860 ·
Maintainers usually reply within 1 day
-
Update crush to 0.102.0Possibly taken @zen0bit claimed this today. Openpackage-update
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
oSoWoSo/oco#1251 · 1 comment ·
Maintainers usually reply within 1 day