Keeps overwriting package.json with file://

[Araxeus]

Type: Bug

Unclear exactly, but everytime i save my package.json - a field gets added to dependencies, with the following value:

{
  "dependencies": {
    "package.name": "file:",
  }
}

(package.name is the value of "name" in the package.json)

My only solution seems to be disabling the extension completly

Extension version: 0.9.5
VS Code version: Code 1.92.0 (b1c0a14de1414fcdaa400695b4db1c0799bc3124, 2024-07-31T23:26:45.634Z)
OS version: Windows_NT x64 10.0.19045
Modes:

System Info

Item	Value
CPUs	11th Gen Intel(R) Core(TM) i5-11600K @ 3.90GHz (12 x 3912)
GPU Status	2d_canvas: enabled canvas_oop_rasterization: enabled_on direct_rendering_display_compositor: disabled_off_ok gpu_compositing: enabled multiple_raster_threads: enabled_on opengl: enabled_on rasterization: enabled raw_draw: disabled_off_ok skia_graphite: disabled_off video_decode: enabled video_encode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled webgpu: enabled webnn: disabled_off
Load (avg)	undefined
Memory (System)	31.80GB (14.99GB free)
Process Argv	--folder-uri file:///c%3A/Git/opl-whatsapp-server --crash-reporter-id bd096ca7-6e86-457b-90dd-59c5388e99a1
Screen Reader	no
VM	0%

[pappnase99]

Experienced the same thing, disabling the Extension solved the weird behavior as well for me. Using Windows 10 here.

[wecomgroup]

俺也一樣

[khairizalkhalid]

I was about to go crazy and disable extension one by one until I found out.

Can confirm that it happens in Windows 11.
I have this extension in MacOS Sonoma, it does not happen.

Edit: In mac, while it did not write "file://" in the package.json itself, it does auto generate package-lock.json even though the project already have yarn.lock

[brachya]

i have the same thing and i disabled it.

[Frank3354]

I work with Node projects that are sometimes shared with a zip file instead of source control.

Every time I open project files with VS Code, my package.json keeps getting modified with a new "dependency" such as "app": "file:"

Deleting this modification will kick off a "RHDA Analysis in progress" and will re-add this "dependency"

The current fix is to disable the extension. I uninstalled it.