New user, cannot run raisely start

[skyeinthecloud]

After downgrading node to v18 from 22 and installing the 2.0.0 version of the CLI, after logging in, attempts to run raisely start result in this:

file:///Users/skye/.nvm/versions/node/v18.20.8/lib/node_modules/@raisely/cli/src/helpers.js:91
	if (!organisation.private || !organisation.private.localDevelopment) {
	                  ^

TypeError: Cannot read properties of undefined (reading 'private')
    at informLocalDev (file:///Users/skye/.nvm/versions/node/v18.20.8/lib/node_modules/@raisely/cli/src/helpers.js:91:20)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async start (file:///Users/skye/.nvm/versions/node/v18.20.8/lib/node_modules/@raisely/cli/src/start.js:191:8)
    at async Command.runtime (file:///Users/skye/.nvm/versions/node/v18.20.8/lib/node_modules/@raisely/cli/src/cli.js:18:4)

Node.js v18.20.8

Node v22.17.1 produces the same results.

[alistairfairweather]

The Node version is probably a red herring here. It looks like the CLI is unable to find or resolve an ID for your Raisely organisation. You should check your .raisely.json file. There should be an organisationUuid defined in there - if there isn't then you should run raisely init in your project folder and that should recreate it. (You should also log out and log in again first - try turning it off and on again and it might just fix itself 🤪 )

EDIT: all of the above assumes you are on Raisely V3 - if it's a very old project it might be V2 and I have no idea about how that would behave.