webdriverio/webdriverio

Problem with Integration percy/webdriverio in project "Error: ReferenceError: require is not defined in ES module scope, you can use import instead"

Open

#14,192 创建于 2024年12月24日

在 GitHub 查看
 (13 评论) (0 反应) (0 负责人)JavaScript (6,029 star) (1,793 fork)batch import
Bug 🐛help wantedwdio-browserstack-service

描述

Environment (please complete the following information):

  • Node.js version: v 20.11.1
  • NPM version: 10.8.1
  • Platform: Android
  • Platform version: 13.0
  • Emulator/Simulator/Real Device: Emulator from Browserstack
  • TypeScript: 5.4.5

Describe the bug

  1. npm install --save-dev @percy/cli @percy/webdriverio
  2. Added require and await percySnapshot (see screen) in test
  3. Run test

Actual result: I get failed with error "Error: ReferenceError: require is not defined in ES module scope, you can use import instead". (check Logs when I use require.txt) Logs when I use require.txt My test with require

  1. Replaced const percySnapshot = require('@percy/webdriverio'); to import percySnapshot from '@percy/webdriverio';

Actual result: I get failed (check Logs when I use import.txt) Logs when I use import.txt

My test with import - error From Percy: 37950736_cli.json

FYI: I opened @percy/webdriverio and saw @percy/core The current file is a CommonJS module whose imports will produce 'require' calls; however, the referenced file is an ECMAScript module and cannot be imported with 'require'. Consider writing a dynamic 'import("@percy/core")' call instead. Percy-Core

Additional context Settings: packagejson tsconfig

Could you give me advice how to fix my problem?

贡献者指南

技术栈
javascripttypescriptnodejs
领域
testing
议题类型
bug
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
1-3 hours
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
active
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
Node.js module systemES modules vs CommonJSwebdriverio test setup
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
60
研究方向
Investigate the @percy/webdriverio package's module type and exports (check if it uses 'type': 'module' or has a 'main' vs 'exports' field). Review the user's tsconfig.json and package.json settings for module resolution (e.g., 'module' and 'moduleResolution'). Look at how webdriverio's test runner loads test files (e.g., using @wdio/types). Consider adding a dynamic import fallback in the integration or updating documentation to guide users on using import syntax. Check existing comments for similar issues or solutions.