Inconsistent deno fmt result between 1.41.3 and 1.42.0

[jeiea]

Steps to reproduce

1. Environment
   • deno: 1.42.0 (release, x86_64-pc-windows-msvc)
   • vscode_deno: v3.36.0
   • vscode: 1.87.2 (system setup)
2. Clone the repository and be careful with branch fmt-ignored.
   git clone https://github.com/jeiea/deno_report.git -b fmt-ignored
3. Open cloned directory with vscode and vscode_deno.
4. Press Ctrl+s on main.ts.

Expected behavior

The file should remain unchanged compared to when it was run with Deno version 1.41.3 or when the command deno fmt was executed.

Actual behavior

Code_240331212316-317.mp4

[nayeemrmn]

Do you have deno.documentPreloadLimit: 0 set in your vscode user settings? If so this will be fixed by denoland/deno#23123.

[jeiea]

Do you have deno.documentPreloadLimit: 0 set in your vscode user settings?

No, I haven't seen that. And I can reproduce this just by changing deno binary.

[nayeemrmn]

Ah, okay your deno.enablePaths must include deno.json now. This is an intentional change in behaviour from 1.41.3, it makes sense. Closing for now but comment here if it's not fixed.

[jeiea]

It's fixed, just I think this should be documented because it's hard to expect and silent breaking change.