Loosen "patternProperties" in package.json schema

[G-Rath]

schematoreupdate uses json-schema-to-typescript to generate type definitions for the schemas provided by schemastore, which are published to npm.

However, the definition generated for the schema for package.json currently has type errors, due to patternProperties.

This was raised on schematoreupdate here, and raised (separately) on json-schema-to-typescript here.

@bcherny provided a detailed explanation of the problem, along w/ a suggested fix that IMO sounds reasonable:

I think the best fix here is to replace the patternProperties section with a more lenient one:

  "patternProperties": {
    "^_": {
      "description": "Any property starting with _ is valid.",
      "type": "any"
    }
  },

This is a more correct definition, since _-prefixed package.json properties don't have to be objects.

If that's not an acceptable change to the schema, I'd like to get a discussion going to see if a middleground can be reached (here & w/ json-schema-to-typescript) that means we can have our schemas & type them too 😉

[G-Rath]

I've just realised the proposed solution uses an invalid type (any) - I've made a comment on the original issue.

As I said:

I'd like to get a discussion going to see if a middleground can be reached