-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
TypeError when launching cypress open-ct
#17373
Comments
I don't believe you need to |
I've removed the config bit and verified I'm still seeing the same error.
|
I've upgraded cypress to v8.0.0, @cypress/vite-dev-server to v2.0.2, and vite to v2.4.4. I've removed all config for svelte, vite, postcss, and cypress, so all are using default settings. I'm still getting the error. |
Hello @ewagoner I am investigating the issue, Can you share your It seems like you are using SvelteJs which cypress does not support officially yet (though we plan to). |
I'd love to help, @elevatebart ! I had no idea svelte was not supported by Cypress. I've used in on a number of svelte projects (though not the new component testing, obvs.) and there are countless blog posts and tutorials out there about using cypress with svelte. I get this error even with a completely blank
And here is my
|
I misspoke, and I apologize. Svelte is absolutely supported with the e2e runner. And yo u are right to make it clearer. What is unsupported is the svelte component testing part. It is not official and we are working towards making it so. Sorry for the confusion. Regarding the bug you are seeing it seems to be in the scanning that vite does for dependencies. |
When there is no values, in the optimization array, supportFile can be a boolean. the final optimized entry passed to fast-glog is then `[false]` whic crashes cypress. This protects against the no-spec issue closes #17373
…pecs found (#17624) * fix: no supportfile + no specs, vite don't crash When there is no values, in the optimization array, supportFile can be a boolean. the final optimized entry passed to fast-glog is then `[false]` whic crashes cypress. This protects against the no-spec issue closes #17373 * fix: protect startServer from undefined specs
The code for this is done in cypress-io/cypress#17624, but has yet to be released. |
…pecs found (#17624) * fix: no supportfile + no specs, vite don't crash When there is no values, in the optimization array, supportFile can be a boolean. the final optimized entry passed to fast-glog is then `[false]` whic crashes cypress. This protects against the no-spec issue closes #17373 * fix: protect startServer from undefined specs
#17641) * fix: prevent vite from crashing where there are no support files or specs found (#17624) * fix: no supportfile + no specs, vite don't crash When there is no values, in the optimization array, supportFile can be a boolean. the final optimized entry passed to fast-glog is then `[false]` whic crashes cypress. This protects against the no-spec issue closes #17373 * fix: protect startServer from undefined specs * fix: when there are specs but the supportFile is undefined
Current behavior
I'm trying to launch the UI in component test mode, using @cypress/vite-dev-server. It crashes before it can start with this error:
Desired behavior
I'm just trying to start the UI in Component Testing mode
Test code to reproduce
My plugins
index.ts
is very bare-bones:Cypress Version
7.7.0
Other
No response
The text was updated successfully, but these errors were encountered: