aleph dev startup fail on windows
See original GitHub issueHello, on the latest version of Aleph, after running aleph init
, i.e. when I then want to run aleph dev
I get uncaught DomException Error telling me that Aleph is unable to set the location
.
Issue Analytics
- State:
- Created 3 years ago
- Comments:24 (17 by maintainers)
Top Results From Across the Web
GUI client crashes in Task Manager - Batch Log - Restart PC ...
You get an error 'Failed to read reply'. Click OK and a Windows message pops up declaring the program has stopped working.
Read more >Aleph hiring Senior Frontend Developer in United States
Aleph is searching for an experienced front-end engineer to join our eight-person team (2 founders + 4 engineers + 1 product designer +...
Read more >Twitter Buys Minority Stake In Aleph - Devstyler.io
Flutter 2.10 will provide Stable Windows Support and more Performance ... Here is how Amazon failed to Secure customer personal data ...
Read more >Israeli Startup Aleph Farms Raises $11.65 Million To ... - Forbes
The injection of capital will allow Aleph Farms to accelerate product development of its slaughter-free meat and to transform Alephs prototype ( ...
Read more >Installing Aleph
This section describes how to set up Aleph for software development. ... operate in debug mode and give more verbose error messages when...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@ije This is from @swork1 on the discord and I can confirm it is the same
I think figured out where part of the problem is coming from. A couple places in
app.ts
we are appendingfile://
at the start of the names of modules which is causing the browser to look inC:\
or something where it won’t be able to find anything because it’s not there. It should be using the whole path so that the browser knows where to look, but @ije why aren’t we instead importing straight from the dev server? I think pointing browsers to look through the file system is a privacy thing that many people don’t want to risk.