
Security News
The Changelog Podcast: Practical Steps to Stay Safe on npm
Learn the essential steps every developer should take to stay secure on npm and reduce exposure to supply chain attacks.
affected-files
Advanced tools
Returns a list of js/ts(x) files, which affected in current branch compared to mergeBase (origin/master by default).
$ npm run afiles
// or
$ yarn afiles
Affected files: (modified, **affected only**)
**__tests__/common.spec.ts**
affected-files.config.js
bin/cli.js
src/index.ts
src/options.ts
src/types.ts
total: 6
Done in 0.82s.
Lets say you have a repo with files
a.js
dependent-from-a.js
dependent-from--dependent-from-a.js
not-dependent-from-a.js
If a.js was modified in your merge request, files dependent-from-a.js and dependent-from--dependent-from-a.js also affected. So, affected-files will return
[ 'a.js', 'dependent-from-a.js', 'dependent-from--dependent-from-a.js' ]
.js, .jsx, .ts, .tsx are supported. Other extensions – not yet.
import getAffected from 'affected-files'
// import { getAffectedSync } from 'affected-files'
const affected = await getAffected(options)
All options are optional.
| Option | default | description |
|---|---|---|
mergeBase | origin/master | Branch or revision which will be used to take a git diff. |
cwd | process.cwd() | Absolute path of cwd folder, where to find files. |
missing | [] | An array of strings, which should not be resolved. For example, in most cases there is no need to resolve react. Used for perfprmance optimization. Also, it could be used in tuple form filename.js ≥≥≥ ../dependency, which disables ../dependency resolving only in filename.js. |
pattern | **/* | Glob pattern of your source files. |
modified | git diff ... | An array of modified files paths. By default it is evaluated from git ls-files relative to mergeBase, but you could define custom modified array. |
usink | [] | An array of glob patterns of files, which considered as universal sink in dependency graph. That means, every tracked file in your repo is dependent from every usink file. For example, you need to build full storybook every time you have affected something in ./.storybook. Then just use getAffected(pattern, { usink: '.storybook/*' }). Note: every usink must match pattern |
tracked | git ls-tree ... | An array of files, which would be used for dependency tree building. E.g. files in node_modules are not participating in dependency traversing. Note: by default untracked but non-ignored files are included. |
absolute | false | If true, returns absolute paths of affected files, relative to options.cwd otherwise. |
dot | false | If true, includes folders and files, starts with dot. |
Place this file in the project root folder (cwd), and export your options.
yarn afiles src/options.ts
custom modified: src/options.ts
affected files (modified, **affected only**):
**__tests__/common.spec.ts**
src/index.ts
src/options.ts
total: 3
affected-files uses git, so, be sure, git is available in docker imageaffected-files uses origin/master revision to compare, so, be sure a) origin/master is exists on runner b) origin/master is up to date.git fetch && git rev-parse origin/master – that cmd resolves all problems, or fail otherwise. Use it before using affected-files.
If git is not available only on some docker images, you could save affected list to file and use it everywhere in CI via artifacts.
FAQs
Retrieves all files which affected in current git branch
The npm package affected-files receives a total of 0 weekly downloads. As such, affected-files popularity was classified as not popular.
We found that affected-files demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Security News
Learn the essential steps every developer should take to stay secure on npm and reduce exposure to supply chain attacks.

Security News
Experts push back on new claims about AI-driven ransomware, warning that hype and sponsored research are distorting how the threat is understood.

Security News
Ruby's creator Matz assumes control of RubyGems and Bundler repositories while former maintainers agree to step back and transfer all rights to end the dispute.