BuilderIO / BuilderIO/gpt-crawler

Mac systems have error with npm start

Open
#87 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
22.4k
Forks
2.4k
PR merge metrics
No merged PRs in 30d

Description

@builder.io/gpt-crawler@1.0.0 start
npm run start:dev

@builder.io/gpt-crawler@1.0.0 start:dev
cross-env NODE_ENV=development npm run build && node dist/src/main.js

@builder.io/gpt-crawler@1.0.0 build
tsc

src/core.ts:56:30 - error TS2339: Property 'request' does not exist on type 'PlaywrightCrawlingContext'.

56 async requestHandler({ request, page, enqueueLinks, log, pushData }) {
~~~~~~~

src/core.ts:56:45 - error TS2339: Property 'enqueueLinks' does not exist on type 'PlaywrightCrawlingContext'.

56 async requestHandler({ request, page, enqueueLinks, log, pushData }) {
~~~~~~~~~~~~

src/core.ts:56:59 - error TS2339: Property 'log' does not exist on type 'PlaywrightCrawlingContext'.

56 async requestHandler({ request, page, enqueueLinks, log, pushData }) {
~~~

src/core.ts:56:64 - error TS2339: Property 'pushData' does not exist on type 'PlaywrightCrawlingContext'.

56 async requestHandler({ request, page, enqueueLinks, log, pushData }) {
~~~~~~~~

src/core.ts:110:24 - error TS2339: Property 'log' does not exist on type 'PlaywrightCrawlingContext'.

110 async ({ page, log }) => {
~~~

Found 5 errors in the same file, starting at: src/core.ts:56

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with src/core.ts at lines 56 and 110, then run npm run build to reproduce the TypeScript errors shown in the issue. Check the Playwright crawling context types used by the request handlers. Done means the project builds without these errors and npm start can launch successfully.

Written by the indexing model from the issue text.

Assessment

Tech stack
node.js, playwright, typescript
Domain
backend, build-system
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.