# javascriptjobs-extractor

Pulls remote listings from [javascript.jobs](https://javascript.jobs) (the
board formerly promoted under the `jsremotely.com` alias — that domain now
301s straight here). JS/TS-focused: React, Vue, Node, Angular, TypeScript.

- No authentication, no public API/RSS — this is a server-rendered HTML
  scrape of `/remote`, which supports a `keyword` query param for server-side
  term filtering (`?keyword=react&page=2`), so pipeline search terms are
  iterated as separate paginated fetches rather than filtered client-side.
- Listing cards give title/employer/job-type badge/salary text/logo. Detail
  pages (`/job/<slug>`) additionally embed a `JobPosting` (schema.org)
  `<script type="application/ld+json">` block with description, exact
  `datePosted`, `employmentType`, and structured `baseSalary`.
- That embedded block is **not valid JSON** (unescaped newlines inside
  `description`, and at least one observed missing comma between sibling
  keys), so we extract fields with targeted regexes instead of
  `JSON.parse`. If a detail fetch fails or a field is missing, we fall back
  to the listing-card values.
- `baseSalary` in that block is unreliable on the source side: postings
  with no salary entered still emit `minValue`/`maxValue: 0` (we treat 0 as
  "not specified"), and at least one observed posting had `minValue` equal
  to `maxValue` (both set to the range's upper bound) despite the
  human-readable listing-card text showing a real range. We keep the raw
  listing-card salary string in `salary` as a trustworthy fallback alongside
  the (possibly wrong) structured `salaryMinAmount`/`salaryMaxAmount`.
- Caps via `javascriptjobsMaxJobsPerTerm` (default 50) and
  `javascriptjobsMaxPages` (default 3, pages per term).
- Every matched job triggers one extra HTTP GET (detail page) for
  enrichment — keep the caps conservative given this is a low-volume niche
  board.