@hasindu---7/ff-link-extract
v2.0.7
Published
Extract direct fuckingfast download links from page URLs
Maintainers
Readme
ff-link-extract
Extract direct download links from fuckingfast pages, store each run in a timestamped folder, and optionally auto-open links in the browser.
NPM Commands Reference
| Command | What It Does |
| --- | --- |
| npm install | Install project dependencies in this folder. |
| npm audit | Check dependencies for known security issues. |
| npm outdated | Show packages that can be updated. |
| npm update | Update dependencies within allowed version ranges. |
| npm pkg get version | Show current project version from package.json. |
| npm view @hasindu---7/ff-link-extract version | Check latest published version on npm. |
Local Folder Workflow (Recommended)
This guide is local-first. No global install required.
1) Open project folder
cd /path/to/your/project2) Install dependencies in this folder
npm installIf you installed this package locally in another project with npm install @hasindu---7/ff-link-extract@latest, run commands using npm exec:
npm exec ff-link-extract-init (IMPORTANT - This creates the urls.txt file where you enter the download files location)
npm exec ff-link-extract
npm exec ff-link-extract-autorun3) Create starter files in this folder
npm exec ff-link-extract-initThis creates:
urls.txtautorun.config.json
4) Put links into urls.txt
Supported input:
- One URL per line
- Raw HTML anchor blocks
- Mixed text containing links
- PrivateBin paste URL with hash key
5) Extract direct links
npm exec ff-link-extract6) Run autorun (optional)
node bin/ff_extract_links_autorun.js -c autorun.config.jsonDry-run mode (no browser open):
npm exec ff-link-extract-autorunCommands (Local)
Extractor
node bin/ff_extract_links.js -i urls.txt -o all-direct-linksUsing local package install (npm exec):
npm exec ff-link-extract -- -i urls.txt -o all-direct-links--help
node bin/ff_extract_links.js --help--version
node bin/ff_extract_links.js --versionAutorun
node bin/ff_extract_links_autorun.js -c autorun.config.jsonUsing local package install (npm exec):
npm exec ff-link-extract-autorun -- -c autorun.config.jsonOptions:
--interval-ms--start-delay-ms--max-links--dry-run
Init
node bin/ff_extract_links_init.jsUsing local package install (npm exec):
npm exec ff-link-extract-init --Options:
--force--help
Output Structure
Each extractor run creates:
links/YYYY-MM-DD_HH-mm-ss/all-direct-links.txtlinks/YYYY-MM-DD_HH-mm-ss/all-direct-links.htmllinks/YYYY-MM-DD_HH-mm-ss/all-direct-links.json
So every run is saved separately and easy to compare.
Autorun behavior:
- If configured input file is not found in current folder, autorun automatically checks the latest folder inside
links.
Common Checks
Extractor version
node bin/ff_extract_links.js --versionIf extraction fails for some links
- Check the generated JSON report for per-link errors.
- Retry after a short delay.
npx Method (Optional)
If you prefer running without cloning this folder:
npx -y @hasindu---7/ff-link-extract -i urls.txt -o all-direct-links