Don't ask to update project if version is unknown

[mihaiblaga89]

Description

• rnv assumes it's a devDep in projects, will trigger a weird update message if it's in dependencies.

[ warn ] [project configure] You are running $rnv v1.0.0-rc.11 against project built with rnv vunknown. This might result in unexpected behaviour!
It is recommended that you run your rnv command with npx prefix: $ npx npx rnv hooks run -x generateDocs . or manually update your devDependencies.rnv version in your package.json.
? What to do next? (Use arrow keys)
❯ Continue and skip updating package.json
  Continue and update package.json
  Upgrade project to 1.0.0-rc.11

Related issues

• GH issues

Npm releases

n/a

[pavjacko]

@mihaiblaga89 this workaround looks weird. we're already checking c.runtime.rnvVersionProject which in this case is present. and it get's it from c.files.project?.package?.devDependencies?.rnv

adding c.runtime.rnvVersionRunner !== 'unknown' seems like a ducktape of symptom rather than tackling actual culprit.

we need to understand why is c.files.rnv.package not populated at this point instead
first check should be c.paths.rnv.dir value and what's going on in createRnvContext

can you provide repro case hod did you arrived at this stage

[pavjacko]

@mihaiblaga89 also add link to related GH issue this PR is meant to solve/fix

[mihaiblaga89]

@pavjacko that's correct, rnvVersionProject should have been checked for unknown. The problem was that the project I was using this in was not a renative project and had rnv as a dep, not devDep. Added dep possibility and removed the unknown check