[json] Override/disable json-schema for package.json

[Forlini91]

I would like to override the default json-schema used by VSCode on some files with my own json-schema (example: VSCode use a json-schema for the Node's "package.json", but I want to be able to override it), like when configuring any other json-schema in settings.json:

//settings.json - currently this doesn't work and VSCode keep applying the Node's package.json json-schema
"json.schemas": [{
	"fileMatch": ["*/package.json"],
	"url": "./schemas/package.json"
}]

Reason is: I'm working on a project where there's a file called "package.json" which is not related to Node: it's something completely different and internal to the project, and it's not even in the root directory, but I can't rename it and VSCode wrongly use the Node's json-schema and everything become an error.

[snayam]

+1

I want to override json schema for package.json to resolve an incorrect type for "bundleDependencies" property, issue /schemastore/issues/876.

To do that i try to use a local schema with custom definition for bundledDependency :

"json.schemas": [{
	"fileMatch": ["/package.json"],
	"url": "./schema/package.json"
}]

My local file is correctly mapped but it doesn't override the default schema, both are loaded, which causes a conflict. Indeed, i can see the package.json try to resolve the rules of my custom schema and those of the default schema.

Default schema in vscode is mapped in ./extensions/npm/package.json :

"jsonValidation": [{
      "fileMatch": "package.json",
      "url": "https://schemastore.azurewebsites.net/schemas/json/package.json"
    }, 

If i delete this (or replace it by my custom file path) and i refresh vscode cache, it works .... But i'm waiting a better solution.

Thanks.

[wayneashleyberry]

I just ran into this same situation, but when adding a custom schema for values.yaml which the Kubernetes extension seems to have already claimed. So my custom schema doesn't seem to be applying to files with that name at all, or they're being merged.

[feryardiant]

I am not sure is my situation related with this issue, but I can get any files under .github/workflows directory validated correctly if it have the same name with another tool's config file. E.g deploy.yml (deployer), build.yml (hammerkit), etc

I've tried to add this to my settings.json, but no luck

{
  "json.schemas": [
    {
      "fileMatch": [
        ".github/workflows/*.yml"
      ],
      "url": "https://json.schemastore.org/github-workflow.json"
    }
  ]
}

[man90es]

I just ran into the same problem as @feryardiant and managed to solve it by editing the yaml.schemas option (not json.schemas). And the correct syntax for it is as follows:

{
    "yaml.schemas": {
        "https://json.schemastore.org/github-workflow.json": ".github/workflows/**.yml"
    }
}

[feryardiant]

Awesome! Thank you @octoman90, I didn't realize that we could use that such format. Anyway,

I can confirm that your suggestion is working perfectly for per-project settings, but I can't get its working as global (workspace) settings.

[laverdet]

I'm also running into this. It's lousy that an extension which is installed by default cannot be disabled or overridden.

[lobsterkatie]

Bumping this - just ran into it today, same as @feryardiant, where my build.yml GitHub workflow file was convinced it had something to do with hammerkit, and therefore kept throwing errors. My experience with the workaround matches his, as well - I have to add it to the project settings for it to work.

(I am using version 1.65.1 on a Mac running Monterey 12.2.1)