Feature: Confine trace, or exclude paths

Open
#30 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript, node.js
Domain
cli, tooling

Research direction

Start at the trace-deps CLI entry point and inspect how dependency paths are traced. Compare the proposed --scope and --exclude options, then define the behavior with tests that confirm files under excluded or out-of-scope paths are not reported.

Written by the indexing model from the issue text.

Description

enhancement

(Use case: find project files to build)

I'd like to be able to trace project files only, excluding dependencies in e.g. node_modules.

I imagine either setting a directory scope that confines the dependency trace, e.g. "trace-deps --scope ./src", or else setting a set of paths for exclusion, e.g. "trace-deps --exclude ./node_modules" would be useful here.

Dominant language
JavaScript
Stars
6
Forks
0
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from FormidableLabs/tracing

All issues in FormidableLabs/tracing

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.