Add note for dev mode on windows

[olaservo]

Motivation and Context

See: #134

How Has This Been Tested?

This workaround has been tested on a Windows 10 machine.

Breaking Changes

None

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update

Checklist

• I have read the MCP Documentation
• My code follows the repository's style guidelines
• New and existing tests pass locally
• I have added appropriate error handling
• I have added or updated documentation as needed

Additional context

There are proposed fixes for TSX, but it appears this would introduce a breaking change for TSX, and there is no known timeline for the next major version: privatenumber/tsx#639 (comment)

[jspahrsummers]

Thanks for the suggestion!

Perhaps we should turn this into a package.json script of its own? e.g., npm run dev:windows (or something like that) might be easier and less error-prone than asking users to do it themselves.

[olaservo]

@jspahrsummers yes that is a better idea! I made this change.

[jspahrsummers]

Great, thank you!