-
Notifications
You must be signed in to change notification settings - Fork 39
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
Move away from ecstatic for serving the built folder #59
Comments
@bahmutov Hey there, when do you think this issue would be resolved? Just so I can organise our project that's using the plug-in. |
Hey there @bahmutov, any update or ETA on this please? |
No update, would love a PR but especially with support for redirects
…Sent from my iPhone
On Jun 25, 2020, at 19:28, KunAtCertik ***@***.***> wrote:
Hey there @bahmutov, any update on this please?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Thanks! That should be enough to resolve #57 (comment) |
Yeah I think a static serve we could spin with option to redirect stray pages to index file would be enough
…Sent from my iPhone
On Jun 25, 2020, at 19:58, KunAtCertik ***@***.***> wrote:
No update, would love a PR but especially with support for redirects
…
Sent from my iPhone
On Jun 25, 2020, at 19:28, KunAtCertik @.***> wrote: Hey there @bahmutov, any update on this please? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.
Thanks! That should be enough to resolve #57 (comment)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
done, released in 1.4.0 |
In https://github.com/cypress-io/netlify-plugin-cypress/blob/master/src/index.js#L9
The
ecstatic
server is deprecated jfhbrook/node-ecstatic#259It would also be nice if the server had an option to redirect unknown URLs to
/
to have an option to handle client-side routing as a fallback (#57, #51)The text was updated successfully, but these errors were encountered: