-
Notifications
You must be signed in to change notification settings - Fork 159
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
Add back windows support? #2074
Comments
@Borwe I don't have Windows, and I guess it was not a conscious action that caused this regression. We are open for PRs! |
I have a fork working for pure windows, but it fails at npm install of |
@Borwe Sounds list a reasonable workaround to me, but can you dig and report the root cause for the issue? |
Here is the root cause, seems it's a sandbox problem. |
For context, sandbox cannot be supported on windows due to nearcore not being compilable/supported on windows. There's a potential way to get it working on windows, but all tests would have to be pointed to |
I see, well, I don't expect anyone to put their effort into making nearcore to operate on Windows, but I also don't see near-workspaces-js in the dependency tree of |
Unfortunately I am back on a Windows machine lol. @frol here is the location where near-workspaces is used. And now that there is rust for itnergration tests here it is too I tried compiling the rust version to track where exactly it is failing, it all boils down to this line |
we took some time to study this on depth and apparently it would not be possible since multiple packages are not compatible with windows (the most important ones being Because of this we will not be able to bring back windows support. To mitigate problems, we decided to write a guide on how to use |
@gagdiez Does Can |
@frol I changed the message to point towards the blogpost 2 weeks ago: create-near-app/src/messages.ts Line 127 in 9c482fd
I'll check now if our frontend works on windows |
I just noticed that the new version doesn't support windows, but old one I had on my system used to.
I now can't use this since WSL2 won't run on my Windows install due to low RAM.
Was wondering if PRs are open to add it back? Or why was it removed?
The text was updated successfully, but these errors were encountered: