Skip to main content

File system ingestion

Normally, jxscout captures JavaScript and HTML files as they flow through its proxy. But sometimes you already have files on disk that you'd like to analyze — for example, JS files downloaded from the Wayback Machine, files collected by other tools, or bundles from a source code repository.

The fs-ingest command lets you recursively import a local folder into a jxscout project without proxying any traffic. Once ingested, the files go through the same pipeline as proxy-captured ones: beautification, analysis, and match detection.

Usage​

Make sure jxscout is running with the target project selected before running the command:

$ jxscout-pro-v2 -c fs-ingest --project-name <your_project> --folder /path/to/files

jxscout will scan the folder recursively and ingest all files.

Options​

  • --target-folder-name — custom name for the target folder. If omitted, it's auto-generated from the input folder name and prefixed with fs-.
  • --include-hidden — include dotfiles and dot-directories (default: false).
  • --max-file-size — skip files larger than this size in bytes. No limit by default.
  • --port — override the running jxscout instance's HTTP port. By default it's read from the project lock file.

Re-running fs-ingest on the same folder is safe — jxscout uses content hashing to skip files that haven't changed.

note

Source maps and chunk discovery are not available for fs-ingested files, since there are no real URLs to resolve against.