Replies: 3 comments
-
|
Try this: 1. Clean out old dependenciesrm -rf node_modules 2. Install with yarn (not npm!)yarn install 3. Run with yarnyarn start or more more developer yumminess: Also, master got messy when people were branching from master and PR-ing to master - there was a mix of stuff that should have been in 8.1 and stuff that would have needed to wait for 9.0. That made it so we couldn't build a 8.1, because there was incompatible stuff mixed in. To avoid that in the future, we'll be using maintenance-9.x for compatible stuff, maintenance-10.x for things that break compatibility. master isn't really useful for anything. Because when it was used, there was confusion about what it should be used for. |
Beta Was this translation helpful? Give feedback.
-
|
OK Yarn seemed to install better this time albeit with errors. Last time it got stuck on the packages bit then decided the internet wasn't working (it was) then gave up. However: Electron-forge was part of the |
Beta Was this translation helpful? Give feedback.
-
|
After much faffing trying to fix some issue with libc and node being stuck on 10.19.0 ignoring attempts to change it using nvm (both fixed although I'm not sure how exactly) ... it still won't run with error: Out of interest which node.js version is required ? I'm using 22.18.0 with WSL Ubuntu. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Been trying to get Configurator to run after updating from the master having not updated for a while. Seems Yarn is now being used but after following the current instructions I'm having no luck getting it to run. The following is the current error:
Doesn't
npm installneed to be run to update things ?Are the build and run instructions missing something simple ?
Beta Was this translation helpful? Give feedback.
All reactions