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
Goldpage does not work on windows #21
Comments
That's possible. I don't have a windows box right now but I'll have a look at it later. |
Goldpage doesn't support Windows for now. Comment this ticket if you want windows support. |
I'm doing a bit of research and discovered Goldpage, love its focus on do-one-thing-do-it-well! Knowing my team works primarily on Windows (I'm on MacOS), we might give Goldpage a spin with WSL but this would be a non-starter for us. Assuming this issue may one day be closed as "Won't Fix", it'd be great if there was a note in the README with platform support.
This tickles my curiosity but I'm not on Windows. I wonder if |
Hi @littleninja ! I will have another look and tentatively write a patch. |
I'll write a patch tentivally next week. In the meantime, WSL should work. |
@littleninja Still interested? I've capacity today to write the patch. |
Sorry for the delay, I hope my comment didn't come across in a way that shifted priorities. There's no urgency on my part. 😔 |
No worries.
You may wanna wait on #24 then. It's going to be lovely. If you don't mind me asking; what exactly are your plans with Goldpage? We can discuss in depth about whether Goldpage is/will be a good fit for you, and it's insightful for me to talk about my users' use cases. |
@littleninja https://github.com/brillout/vite-plugin-ssr is pretty much done and I published a beta. I'd be curious to know what you think. |
When running goldpage build (or goldpage dev) on windows, an internal error occurs (unfortunately I don't have a windows box to try on now, but the error is very terse anyway). It seems related to the assumption that paths are separated by forward slashes, which is not the case on windows.
The text was updated successfully, but these errors were encountered: