npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@hasindu---7/ff-link-extract

v2.0.7

Published

Extract direct fuckingfast download links from page URLs

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/project

2) Install dependencies in this folder

npm install

If 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-autorun

3) Create starter files in this folder

npm exec ff-link-extract-init

This creates:

  • urls.txt
  • autorun.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-extract

6) Run autorun (optional)

node bin/ff_extract_links_autorun.js -c autorun.config.json

Dry-run mode (no browser open):

npm exec ff-link-extract-autorun

Commands (Local)

Extractor

node bin/ff_extract_links.js -i urls.txt -o all-direct-links

Using 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 --version

Autorun

node bin/ff_extract_links_autorun.js -c autorun.config.json

Using local package install (npm exec):

npm exec ff-link-extract-autorun -- -c autorun.config.json

Options:

  • --interval-ms
  • --start-delay-ms
  • --max-links
  • --dry-run

Init

node bin/ff_extract_links_init.js

Using 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.txt
  • links/YYYY-MM-DD_HH-mm-ss/all-direct-links.html
  • links/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 --version

If 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