Why after waitiing, the 'click' is undefined

Descrizione

const { Chromeless } = require('chromeless')
async function run() {
  const chromeless = new Chromeless()

  const screenshot = await chromeless
    .goto('https://www.google.com')
    .wait('div[data-type="planName"]')
    .click('div[data-type="planName"]') //after wait(), 'click' is undefined
    .screenshot()

  console.log(screenshot) 
  await chromeless.end()
}

run().catch(console.error.bind(console))

Guida contributor

Tech stack

typescriptjavascriptnodejs

Dominio

testing

Tipo issue

bug

DifficoltàQuanto dovrebbe essere impegnativa per un nuovo contributor.

3

Tempo stimatoTempo stimato per completare e verificare uno scope piccolo.

under 1 hour

Stato attivitàQuanto è probabile che la issue sia ancora attiva e reviewable.

stale

ChiarezzaQuanto chiaramente la issue descrive problema, scope e risultato atteso.

clear

Prerequisiti

JavaScriptasync/awaitChromeless basics

Adatta ai principiantiQuanto la issue è adatta a contributor alla prima esperienza.

40

Direzione di ricerca

The issue reports that after calling `.wait()`, the subsequent `.click()` method is undefined. This suggests a potential chaining issue in the Chromeless API. First, review the Chromeless documentation and source code (e.g., the class definition in `src/`) to verify whether `wait()` returns a Chainable instance or a Promise that resolves to a different type. Check the existing issue comments for any maintainer responses or user workarounds. Also, look at related issues or PRs that might address method chaining. The goal is to determine whether this is a user error or a library bug, and if the library handles promise chaining correctly.