-
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
Cuypress can't managed to load the support file when using cypress as custom module #26710
Comments
@emilyrohrbough @nagash77 Thanks a lot! 🙏 |
The support file doesn't work if it is in node_modules (see #23616), and that really is annoying... there should be a way to run it from there if the path of the support file points to node_modules |
Any news regarding this issue guys? |
@idanElitzur Looking at this issue now. |
@idanElitzur After consideration, this isn’t a feature we are looking to develop at this time. If we decide that this is something we want to pursue in the future we will comment back on this ticket. For the time being we are going to close this issue. |
:( |
Current behavior
Hey, i've packed and bundled Cypress with some extras and custom abilities to be scalable in multiple projects in my organization.
Now Cypress packed as isolated module inside the structure below -
but the support file can't managed to load but actually everything works ok when I'm turning the flag for support file to "false".
But i really need the support file for some handlers like catching console errors during the test execution and for the html reporter configuration.
The I got regarding the support file when i running cypress is below -
Desired behavior
No response
Test code to reproduce
Technical info:
cypress.config.file -
tsconfig.json inside the packed cypress (scalable_cy) -
webpack.config.js -
package.json inside the packed cypress (scalable_cy) -
package.json inside the main project root (only the script that run the packed cypress) -
Cypress Version
12.11.0
Node version
14.19.1
Operating System
13.0.1 M1
Debug Logs
The text was updated successfully, but these errors were encountered: