Skip to content

Auto-infer dependencies from mod configuration files during version upload #5780

@Runteryaa

Description

@Runteryaa

Please confirm the following.

  • I checked the existing issues for duplicate feature requests
  • I have checked that this feature request is not on our roadmap

What parts of Modrinth is your feature request related too?

Modrinth.com website

Is your suggested feature related to a problem? Please describe.

Currently, when uploading a new version, the version creation modal successfully reads files like fabric.mod.json, quilt.mod.json, and mods.toml to automatically infer game_versions and loaders.

However, it completely ignores project dependencies. If a mod relies on fabric-api or an optional dependency like respackopts, the "Dependencies" section remains completely empty. This forces developers to manually search for and add every single dependency for every version they upload, which is a repetitive and tedious process.

Describe the solution you'd like

I suggest updating the loader-parsers.ts helper to extract dependencies from mod metadata files. Once extracted, the UI could handle these in two ways (depending on what you prefer):

  1. Auto-populated: Add the dependencies directly to the draftVersion.dependencies list.
  2. Suggested: Add them to the "Suggested Dependencies" list, allowing the user to review and confirm them before they are added.

I believe even just providing them as "suggestions" would be a massive improvement over the current manual search process.

Describe alternatives you've considered

The primary alternative is keeping the current manual process, which is prone to human error (e.g., forgetting to link an optional dependency) and tedious for creators who upload frequently.

Another alternative I considered was adding a manual "Scan for Dependencies" button to the UI. However, automatically fetching and suggesting them during the file upload step feels much more seamless and perfectly matches the existing behavior for game_versions and loaders.

Additional context

I actually tried to implement this locally but i couldn't get it working. the fork is available in my profile.

I hope this feature can be considered, as it would save a lot of time for modpack and resource pack creators! Thank you for your time.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions