-
-
Notifications
You must be signed in to change notification settings - Fork 56
Gibberish main window #70
Comments
Could you try deleting the package-lock.json and reinstalling the dependencies and seeing whether it improves things? Basically I can’t explain the issue so I can only conclude that NodeGUI itself (which Svelte NodeGUI depends upon) has changed since I was last working on this. |
@shirakaba , with all respects to your efforts with this project, I already explained the same problem about rendering in #68 and said that it started with @nodegui/[email protected]. |
On my end, I never saw such problems in versions following 0.0.4, so I don’t have much to go on. Can you try pinning your npm install --save --save-exact @nodegui/[email protected] |
[Sorry for the slow response; I fell quite ill and basically dropped out of normal life for a couple days.] Hmm. If I use that version of nodegui (0.30.2) I get the error I'll paste below when I do
|
0.1.2 is the latest version of
No idea. Doesn't happen on my side, and I've looked into it in other issue threads without any luck. My working setup:
As the issue doesn't reproduce on my setup, I'm afraid I must rely on other users to get to the bottom of it!
Current versions of It could also be that the starter template is not quite right. You could try cloning the main |
Sorry about the version number confusion... as I mentioned above I was quite ill for a couple days and am still not fully recovered or up to my normal level of thinking! I just wanted to try svelte-nodegui out, but couldn't because of the errors mentioned above. I'm not sure I'll be able to spend more time investigating it, although I'd like to. I'll post here if I do. |
Closed in favour of #72. |
The first time I do
npm start
, the attached screenshot is the window I see. This is on MacOS 11.6.I did have some other problems getting it running at all for the first time. I was able to get past them, but I am mentioning them here in case they're related. The first is described at this link, which was resolved by following the "Try the following" comment at the bottom of the linked page. The other was resolved by doing
export NODE_OPTIONS=--openssl-legacy-provider
.I'm no longer concerned about those earlier problems, but obviously, the screenshot shows a serious current problem.
The text was updated successfully, but these errors were encountered: