-
Notifications
You must be signed in to change notification settings - Fork 3.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error in absolute file path of component-index.html #27750
Comments
@lmiller1990 sorry for the ping, but since you solved the original issue you might find this relevant. |
Thanks for filing this issue. I'm not working on Cypress any more, so I'm not sure I'll be able to look at this one in the immediate future. It should be a reasonably easy fix though, take a look at the previous PR and see if we can check if it's absolute path, and handle that correctly. |
Is this working with Cypress 12.17.3? We have a very similar issue, where we define the indexHtmlFile like: |
After further analysis, the fix from #26400 actually introduced this bug. |
I have the same issues. Upgraded from v10 to v13.5. indexHtmlFile throws error indexHtmlFile: path.join(__dirname, 'cypress/index.html'), supportFile works in the same way supportFile: path.join(__dirname, 'cypress/support.js'), |
I created a very simple fix for it in the PR: #28324 but I could not yet test it. |
Released in This comment thread has been locked. If you are still experiencing this issue after upgrading to |
Current behavior
This issue tried to solve the resolution of component-index.html:
#26400
However the problem is still present. When setting:
You get an error along the lines of:
The problem is resolved if instead you use a relative path to the component-index.html:
The issue is bad because nx uses an absolute path, so no component testing is working via nx
Desired behavior
No response
Test code to reproduce
Repro:
https://github.com/wiegell/cypress-bug
Run:
yarn nx run my-standalone-lib:component-test
This repro has been made with:
Cypress Version
13.1.0, also tried 12.17.4, same problem.
Node version
v18.17.1
Operating System
macos 13.4.1
Debug Logs
gist
Other
No response
The text was updated successfully, but these errors were encountered: