#81 ed534d7 Thanks @acao! - export handleRefresh

#83 efd54f0 Thanks @acao! - fix undefined position bug with json-schema-library upgrade

#64 0aaf308 Thanks @acao! - Breaking Change: replaces backticks with <code> blocks in hover and completion! This just seemed to make more sense.

• upgrade json-schema-library to the latest 8.x with patch fixes, remove "forked" pointer step logic
• after autocompleting a property, when there is empty value, provide full autocomplete options
• as noted in the breaking change notice, all psuedo-markdown backtick ``delimiters are replaced with<code>

#63 a73c517 Thanks @acao!

breaking change: only impacts those following the "custom usage" approach, it does not effect users using the high level, "bundled" jsonSchema() or json5Schema() modes.

Previously, we ask you to pass schema to each of the linter, completion and hover extensions.

Now, we ask you to use these new exports to instantiate your schema like this, with stateExtensions(schema) as a new extension, and the only one that you pass schema to, like so:

import type { JSONSchema7 } from "json-schema";
import { json, jsonLanguage, jsonParseLinter } from "@codemirror/lang-json";
import { hoverTooltip } from "@codemirror/view";
import { linter } from "@codemirror/lint";

import {
  jsonCompletion,
  handleRefresh,
  jsonSchemaLinter,
  jsonSchemaHover,
  stateExtensions,
} from "codemirror-json-schema";

import schema from "./myschema.json";

// ...
extensions: [
  json(),
  linter(jsonParseLinter()),
  linter(jsonSchemaLinter(), {
    needsRefresh: handleRefresh,
  }),
  jsonLanguage.data.of({
    autocomplete: jsonCompletion(),
  }),
  hoverTooltip(jsonSchemaHover()),
  // this is where we pass the schema!
  // very important!!!!
  stateExtensions(schema),
];

upgrade to use full .js import paths for NodeNext compatibility, however not all of our dependencies are compatible with this mode, thus we continue using the legacy nodeResolution strategy.