VS code problems loading package.json schema

Whenever I open a pacakage.json file I get this error.
I am not running any proxy and I haven tried turning it off like the few answers on internet suggested but that didn't fix it.
I have tried disabling and uninstalling what 5 extensions I use.
I have also tried putting this

"json.schemas": [
    {
      "fileMatch": ["/package.json"],
      "url": "https://json.schemastore.org/package",
      "schema": true
    }
  ]

"json.schemas": [
    {
      "fileMatch": ["/package.json"],
      "url": "https://json.schemastore.org/package",
      "schema": true
    }
  ]

in my settings.json and that makes the warning go away but I don't get any tooltip when hovering over properties in the package json so I don't think it's working.

I'll appreciate any help

GaneshOP•2/27/25, 3:49 PM

btw this is from settings.json but vscode schemas are probably local so maybe it itsn't fetching anything

Ἔ

ἔρως•2/27/25, 3:53 PM

try adding to the url

GaneshOP•2/27/25, 3:54 PM

hmm the error returned

Ἔ

ἔρως•2/27/25, 4:14 PM

same file or a different one?

GaneshOP•2/27/25, 4:14 PM

same

Ἔ

ἔρως•2/27/25, 4:15 PM

restart vscode

Ἔ

ἔρως•2/27/25, 4:16 PM

if it doesnt work, go to "settings", search for json schema download and enable it

GaneshOP•2/27/25, 4:19 PM

no dice

GaneshOP•2/27/25, 4:20 PM

A couple days ago I was having trouble when fetching in node due to it's implementaion of happy path algorithm. Do you think that can be the problem here? I forgot if electron bundled node with it or just browser environment

GaneshOP•2/27/25, 4:25 PM

ok it appears to bundle both. Tho I'm not sure how to test this theory in vs code.
for node i could just pass not sure how to achieve that in vs code

Ἔ

ἔρως•2/27/25, 4:27 PM

no, thats a vscode thing, not node thing

Ἔ

ἔρως•2/27/25, 4:27 PM

check if there is an update available

GaneshOP•2/27/25, 4:27 PM

already did on the latest version

Ἔ

ἔρως•2/27/25, 4:28 PM

im out of ideas then

Ἔ

ἔρως•2/27/25, 4:28 PM

disable the schema downloading then, so it doesnt bug you

GaneshOP•2/27/25, 4:31 PM

I'll let it stay on it was mostly cause i was curious about the error.
Maybe i'll create a js script that downloads the package schema and adds it locally in the project

GaneshOP•2/27/25, 4:31 PM

you can do that right?

GaneshOP•2/27/25, 4:34 PM

actually wtf

GaneshOP•2/27/25, 4:34 PM

I removed the json.schema snippet from the settings json and it suddenly started working

GaneshOP•2/27/25, 4:36 PM

whatever we'll see if it breaks with next npm init

GaneshOP•2/27/25, 4:36 PM

thanks for helping btw ἔρως

Ἔ

ἔρως•2/27/25, 4:40 PM

you're welcome

Ἔ

ἔρως•2/27/25, 4:41 PM

didnt think about removing that, to be honest

GaneshOP•2/27/25, 4:42 PM

It shouldn't work technically since I didn't have it when i first got error

GaneshOP•2/27/25, 4:42 PM

it's probably some spagetti code

Ἔ

ἔρως•2/27/25, 5:03 PM

probably some tool being overly helpful to you