Release notes generated directly from the repository changelog.
On this page
1.1.0 — 2026-10-11
Preserve managed storage across npm dependency commands with configuration
values before the command, native aliases and option shorthands. Respect explicit
false values and npm global/local precedence when selecting local conversion.
Add read-only --info reports with runtime, project/workspace context, manager
selection, configuration origins, dependency layout and ownership status.
Add --why as a configuration explanation flag, preserving native info,
why, clean, and completion commands and later native arguments.
Add doctor --json with a versioned diagnostic schema, issue codes and repair
plans, including JSON errors for invalid configuration or project manifests.
Add optional --size inspection of unique regular-file bytes, deduplicating
hardlinks and skipping child symlinks and unverified dependency storage.
Generate contextual Bash, Zsh, Fish and PowerShell completions with
--completion, without loading project configuration or installing files.
Preserve the complete 1.0.1 documentation before updating current guides.
Add automatic external storage with storagePath: 'auto' and
initialize --external, using separate deterministic destinations per project.
Record verified storage in a local inventory; add --storage list with optional
JSON/size output and --storage register for existing tracked installations.
Unavailable projects remain recorded and are never treated as unused storage.
Add --relocate with preview, filesystem/link checks and a persistent recovery
journal. Retain the chosen destination without overwriting JavaScript config;
support explicit recovery, doctor repairs, restoration and preference reset.
Verify automatic external storage and retained relocation destinations against
all five native managers and the installed npm package artifact.
1.0.1 — 2026-10-04
Publish the documentation website link in npm package metadata and the README,
making the guides available from the npm Homepage link and npm docs fnspm.
Include the issue tracker URL in package metadata. CLI behavior and runtime
dependencies are unchanged from 1.0.0.
1.0.0 — 2026-10-04
Hold operation locks across restoration, the native command, and conversion;
coordinate workspace roots and sections, including untracked shared storage.
Recognize common native options before dependency commands, including npm
workspace selections, pnpm filters/recursive installs, and Yarn workspace adds.
Add config --show with per-setting origins, manager selection reasons,
project/dependency roots, and optional machine-readable JSON.
Add doctor --fix --dry-run and explicit doctor --fix for identity-checked
link recovery, interrupted restoration cleanup, and missing ignore rules.
Verify all five native managers and workspace layouts, including Yarn PnP and
cache-only Deno, using local fixtures rather than public registry dependencies.
Expand Windows short paths and resolve directory aliases before launching Bun,
avoiding workspace link failures without changing native arguments or configs.
Normalize repository line endings and run the full manager suite on Windows,
Linux, and macOS with Node.js 22 and 24.
Compatibility contract for 1.0
Preserve 0.3 configuration file formats, settings, closest-config resolution,
native argument forwarding, exit codes, and local automatic conversion.
config get, config set, and other native config commands remain forwarded;
only the config --show inspection form belongs to FNSPM.
Concurrent or nested FNSPM operations targeting the same dependency scope fail
promptly before starting another native command. External package managers and
cloud clients do not participate in FNSPM locking.
Recovery never removes unknown locks, adopts foreign links, or overwrites
conflicting dependency directories.
0.3.0 — 2026-10-01
Require Node.js 22 or newer; use a single npm development lockfile.
Preserve native arguments, live terminal output, child exit status and interrupts.
Load CJS/ESM configurations with strict validation and partial defaults.
Implement documented initialization flags without overwriting existing config.
Detect manifest package managers and workspace roots; reject ambiguous locks.
Replace destructive relocation with collision checks, ownership state, rollback,
operation locking, and explicit migrate / restore commands with dry runs.
Add doctor and dedicated external dependency storage with link safety checks.
Preserve automatic conversion after native commands, including workspace
sections; only convert local dependencies in the invocation directory.
Keep per-section initialization/configuration independent; inherit the nearest
parent config without losing it when local migration state/lockfiles appear.
Safely adopt matching legacy project-local nosync links without moving their
dependency files, and handle repeat clean installs.
Restore and refresh already tracked shared workspace storage when installs
run from a section, preserving the workspace root's own configuration.
Build before packaging, ship complete declarations, and avoid CLI side effects
when importing the package.
Correct cloud-provider support claims and align license documentation with GPL.
Compatibility notes
Unknown config settings/options are now rejected rather than silently ignored.
Multiple lockfile managers require a declaration or explicit override.
--no-sync-folder now disables automatic migration.
Migration refuses existing destinations instead of deleting them.
restore needs recorded ownership; matching project-local legacy links can be
adopted using migrate, including automatic adoption before clean installs.
TypeScript is a build dependency, not a peer requirement for CLI users.