@naugtur can you please take a look at this? :)

Hi, sorry I missed this.

I need to fold this repository back into the original project. It was made separate because I was hoping to donate this part to NPM itself.

For this to be a fix, we'd need a way to ship those schemas somehow.
Do you know of any other packages that export their schemas? ow do they do that?

No need to apologize.

I need to fold this repository back into the original project. It was made separate because I was hoping to donate this part to NPM itself.

Too bad it's not part of npm - the features are essential. You could port them back together in one repository with something like npm workspaces or you throw them directly together ;)

For this to be a fix, we'd need a way to ship those schemas somehow.
Do you know of any other packages that export their schemas? ow do they do that?

The only one I know is nx. The have a project.json file that references their schema like this:

{
  "name": "awesome-app",
  "$schema": "../../node_modules/nx/schemas/project-schema.json",
  "projectType": "application",
   ...
}

Alternatively it could be referenced as URL

{
  "$schema": "https://unpkg.com/somepackage@someversion/schema.json",
}

I was thinking about that unpkg or jsdelivr option, if I folded this into the main repo, it could be somewhat intuitive.

I wonder if setting the json files as exports in package.json would be any helpful for referencing them too. Gonna ask GPT tomorrow and see if it has any reasonable examples of this in training sets :D

There doesn't seem to be a way to use anything other than a fully qualified url in "$schema"
So relative paths, not to mention resolving form a package, won't work. jsdelivr approach is the only one left.
Let's look into merging the repo back in, as it's necessary anyway.