-
-
Notifications
You must be signed in to change notification settings - Fork 38
Forked version, bugfixes and 32-bits R support #432
Comments
I encountered the same issue. I am waiting for the solution and will be grateful for any useful suggestions. |
I encountered the same platform issue brought up in issue #429. When I use this forked repo ^ I encounter a new error: "Error in eval(parse(text = text, keep.source = FALSE), envir) : |
@blschum Have you specified |
Thanks for sharing this! The forked repo solved both the platform and --display=none issues for me. However, I get a new error beginning:
From here this should be solved by upgrading nodejs to v14+. However, in R/install_nodejs.R of the fork, it looks like it's set to install v15. Any advice appreciated. Edit: I think the above had to do with having two versions of electricShine installed at once. electrify actually contains an argument to specify the nodejs version, so that's easy enough. My new issue is:
Edit: This was a me issue. I had recently upgraded my version of R and needed to re-install Rtools. Current error is I am trying to figure out how to resolve is:
|
I'm using this with node v14.17.4. I haven't touched R/install_nodejs.R (afair) and recommend manually installing node instead of letting electricShine do it. I've had some issues with more recent versions but I'm experienced in R, not node, so have difficulty debugging this. If anyone feels like fixing it + making a pull request, I'm very much open to it. |
Actually, just setting nodejs_version = "v14.17.4" resolved the above issues. Thanks! I now get a .exe in dist, and the infinite loading screen issue I had when working off the main branch is resolved as well. Now, the installed app is not actually running, but I suspect that has to do more with how I've set up my app with golem, so that's a separate issue... |
Ah, I'm all too familiar with that. You can open a command window, navigate to the folder the project is in (not the dist folder, the one containing package.json), and use |
I got it to work! Thanks so much for the help. For future users, here is exactly what I did: Ran erikvona's fork of electricShine with the following parameters: A .exe was created, but did not run properly (gray transparency over the app and nothing happened when action buttons clicked). With node.js downloaded (directly/manually, not just via electrify), on the command line (Windows PowerShell) I navigated to the build path and ran |
I really needed this package to work, but encountered numerous bugs.
Bugs I encountered:
{golem}
do)I also needed two new features:
I addressed all this in a fork (erikvona/electricShine). Since I was adding features before addressing some of these bugs, isolating the fixes and submitting pull requests for them is a bit of work for me. If you're still working on this and want help, I'll do what I can.
The text was updated successfully, but these errors were encountered: