component-driven / component-driven/cypress-axe
Warnings with Webpack 5
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 641
- Forks
- 90
- Avg merge
- 6h 8m
- Merged PRs (30d)
- 1
Description
WARNING in ./node_modules/cypress-axe/dist/index.js 16:47-54
Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
@ ./cypress/support/index.js 3:0-21
@ ./node_modules/@cypress/webpack-dev-server/dist/loader.js!./node_modules/@cypress/webpack-dev-server/dist/browser.js 2:30-69
@ ./node_modules/@cypress/webpack-dev-server/dist/browser.js 3:4-41
WARNING in ./node_modules/cypress-axe/dist/index.js 16:77-84
Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
@ ./cypress/support/index.js 3:0-21
@ ./node_modules/@cypress/webpack-dev-server/dist/loader.js!./node_modules/@cypress/webpack-dev-server/dist/browser.js 2:30-69
@ ./node_modules/@cypress/webpack-dev-server/dist/browser.js 3:4-41
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the Webpack 5 warnings from the cypress/support/index.js import of cypress-axe, then inspect the referenced cypress-axe/dist/index.js dependency. Done means the reported critical-dependency warnings no longer appear during the Cypress Webpack build.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cypress, typescript, webpack
- Domain
- build-system, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100