Why after waitiing, the 'click' is undefined

描述

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))

贡献者指南

技术栈

typescriptjavascriptnodejs

领域

testing

议题类型

bug

难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。

3

预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。

under 1 hour

活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。

stale

清晰度议题是否清楚说明期望改动、验收标准和下一步。

clear

前置要求

JavaScriptasync/awaitChromeless basics

新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。

40

研究方向

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.