Issues

• nf publish gives no warning for invalid contents entries or a package with no contents

  command:publishenhancement
  NanoForge-dev/CLI#262 · Filter by author Exeloo opened on Nov 8, 2026

• nf publish reads the whole package into memory and checks its size only on the server

  bugcommand:publish
  NanoForge-dev/CLI#261 · Filter by author Exeloo opened on Nov 8, 2026

• nf publish does not read .gitignore or .nfignore

  command:publishenhancement
  NanoForge-dev/CLI#260 · Filter by author Exeloo opened on Nov 8, 2026

• nf install does not install the npm and engine library dependencies of a package

  command:installenhancement
  NanoForge-dev/CLI#259 · Filter by author Exeloo opened on Nov 8, 2026

• nf install with no names skips packages listed but not locked

  command:installenhancement
  NanoForge-dev/CLI#258 · Filter by author Exeloo opened on Nov 8, 2026

• nf publish rejects v2 registry manifests

  bugcommand:publish
  NanoForge-dev/CLI#254 · Filter by author Exeloo opened on Nov 7, 2026

• Change README link to CLI doc to the real doc

  documentationgood first issue
  NanoForge-dev/CLI#228 · Filter by author Tchips46 opened on Sep 24, 2026

• Paths are badly handled on Windows

  bugcommand:new
  NanoForge-dev/CLI#123 · Filter by author Exeloo opened on Apr 17, 2026
  

• Make the editor optional

  command:editorenhancement
  Feature

  NanoForge-dev/CLI#117 · Filter by author Exeloo opened on Apr 14, 2026

• Use self nf path to run sub commands

  command:devenhancement
  Feature

  NanoForge-dev/CLI#100 · Filter by author Exeloo opened on Mar 15, 2026
  1