pahen/madge

[Question] How to ignore the entrypoint using orphans

Open

#249 opened on Jun 25, 2020

View on GitHub
 (1 comment) (2 reactions) (0 assignees)JavaScript (8,058 stars) (322 forks)batch import
enhancementgood first issueviz

Description

As you can see here the entrypoint server.ts is reported as ophan:

https://gitlab.com/Lepardo/simplewebspider-nodejs/-/jobs/612057537

So it must be an orphan, because it's the entrypoint. But is there away to ignore that one, so it's not reported as ophane?

Excluding it make no sence, then all others are ophans.

Contributor guide

Tech stack
javascriptnodejs
Domain
toolingcli
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Familiarity with madge command line toolKnowledge of JavaScript module systems
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70
Research direction
Investigate the madge configuration and orphan detection logic. Look for existing options to exclude files, possibly in the CLI parser or in the Madge class. Consider adding a new option like ' ignore entrypoint' or extending the existing ' exclude' option to handle entrypoints automatically. Check if the entrypoint is determined from the command line argument and can be filtered out in the orphan report.