Common NovaModuleTools problems and how to get unstuck

nova init some/path does not work

Path input is explicit. Use:

nova init -Path ~/Work

or, for the full working example:

nova init -Example -Path ~/Work

nova bump says the repository has no commits yet

nova bump chooses the version label from Git history. If the repository exists but has no commits yet, create the first commit and run the command again.

git add .
git commit -m "feat: initial project scaffold"
nova bump -WhatIf

The module does not seem to reload after I rebuild

PowerShell may still have the previous version loaded in memory. Remove the module first, then rebuild and import again:

$project = Get-NovaProjectInfo
Remove-Module $project.ProjectName -ErrorAction SilentlyContinue
nova build
Import-Module $project.OutputModuleDir -Force

Tests fail but I cannot see where the results went

The normal Nova test workflow writes XML results to:

artifacts/TestResults.xml

If you run Pester directly instead of through nova test / Test-NovaBuild, you may get different output behavior.

Build errors point at the generated .psm1 file

Enable or keep SetSourcePath in project.json. NovaModuleTools will add # Source: markers to the generated module so you can map errors back to the original files under src/.

I want the normal command flow after fixing an issue

Go back to Core Workflows for the standard build, test, bump, and release sequence, or use Working with Modules if you need import and reload steps.