If I understand correctly, to use the SchemaValidator, one needs to expose some method capable of making HTTP requests to setupSchemaValidator, or alternatively in a scenario where making requests is undesired or impossible, to download and store the meta-schemas in their code/database and fetch them from there, or provide them through a prebuilt cache. I think it would be easier for consumers of the library if the meta-schemas were available in the npm package, in order to:
a) allow importing them directly for use with other validators
b) make them available to the SchemaValidator by default, and make setupSchemaValidator call fetch only when unrecognized refs to third-party schemas are present.
If I understand correctly, to use the SchemaValidator, one needs to expose some method capable of making HTTP requests to
setupSchemaValidator, or alternatively in a scenario where making requests is undesired or impossible, to download and store the meta-schemas in their code/database and fetch them from there, or provide them through a prebuilt cache. I think it would be easier for consumers of the library if the meta-schemas were available in the npm package, in order to: a) allow importing them directly for use with other validators b) make them available to the SchemaValidator by default, and makesetupSchemaValidatorcallfetchonly when unrecognized refs to third-party schemas are present.