Let the plugin launch the Axe MCP Server with Docker so the image tag follows plugin releases
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 57/100
Research direction
Start by reading the plugin’s user configuration options and bundled MCP config, the two affected contracts named in the issue. Trace how the npm server command and its pinned version are selected, then see how a Docker distribution could follow plugin releases while keeping npm as the default. Done means users can select Docker without hand-writing MCP config, the Docker image pin updates with plugin releases, and npm users see no change.
Written by the indexing model from the issue text.
Description
Problem
The plugin's bundled MCP config only launches the server with npm, so its pinned version moves with each plugin release. Docker users have to write their own config, which keeps whatever image tag they copied until they edit it. Docker users therefore drift from the release the plugin's guidance is written against, while npm users don't.
Acceptance criteria
- A user can choose Docker as the distribution through the plugin's own configuration, without writing an MCP config by hand.
- A Docker user who installs a plugin release that moves the pin runs the newly pinned image without editing anything.
- npm remains the default, and existing npm users see no change.
Non-goals
- Changing which server release is pinned.
- Removing the hand-written Docker configs from the setup docs.
Affected contracts
The plugin's user configuration options and bundled MCP config.
- 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 3/5 1-2 days Newbie friendliness 66/100
-
Difficulty 4/5 3-5 days Newbie friendliness 48/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