Update documentation to direct users to the recursive file strategy

[nathanpovo]

Updates the documentation in the README to direct users to use the "recursive" version file strategy rather than keeping it set to the default (which is the "local" file strategy).

The advantage of setting up the shell to use the "recursive" file strategy is that fnm can search recursively for a Node version rather than just the current directory.

Updating the README makes it easier for first-time users to set up their shell without running into issues with the Node version not getting resolved if it is defined in a parent directory.

Note that I have only tested this with PowerShell.

Fixes #1094

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
fnm	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jan 2, 2025 9:59am

[changeset-bot]

⚠️ No Changeset found

Latest commit: 390a71d

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR