[andrewperry]

Refs eclipsesource#1557, following the discussion there.

Stacked on eclipsesource#2644, eclipsesource#2645 and eclipsesource#2648 (and eclipsesource#2643, which eclipsesource#2645 includes). Until those are merged this PR shows their commits too; only the last three commits are new here:

• feat(core): add @jsonforms/core/core-only entry point that never loads Ajv
• test(vue-vuetify): update snapshots now that clearAllIds resets the ids in use
• test(vue-vuetify): unmount mounted forms after each test

I'll rebase onto master once the stack lands, and mark this ready for review then.

What changed

• New entry point @jsonforms/core/core-only. It exports everything @jsonforms/core does except createAjv, createAjvValidator and validate, and never loads ajv or ajv-formats.
• @jsonforms/core is unchanged: same exports, Ajv still the default. The bindings and renderer sets are untouched.
• Ajv lives in one module. util/validator.ts now also holds createAjvValidator (moved from util/formValidator.ts). It is the only module importing Ajv at runtime, and when loaded it registers itself as the default through the new util/ajvDefault.ts. The reducer asks createDefaultAjv() instead of importing createAjv. The util barrel no longer re-exports validator.ts; the main entry point does.
• Without Ajv, init / updateCore need a validator, an ajv instance or validationMode: 'NoValidation', and otherwise throw an error naming those options.
• Build. Rollup builds both entry points with a shared chunk (lib/jsonforms-core-shared.{esm,cjs}.js), so importing both doesn't duplicate core. The main / module / typings paths are unchanged and no exports map is added, so deep imports keep working. The subpath resolves through core-only/package.json, which is added to files.
• Docs. The core README has a "Using JSON Forms without Ajv" section.

Vue Vuetify test changes

Snapshots (ID numbers only). 20 snapshots now show # where they showed #6 / #8. Under Vitest, core's CommonJS build was evaluated twice (by the module runner and by Node's require), so clearAllIds() in the specs reset a different copy of the ID state from the one the renderers used. With the shared chunk, both copies of the small entry file require the same chunk, so clearAllIds() works as the specs intend. The diff is 96 lines each way, identical once #<n> is replaced by #.

Unmount after each test. mountJsonForms() attaches to document.body and nothing unmounted the forms. The duplicate core copy had hidden this by keeping IDs unique; now the next form reused the same IDs while the previous one was still in the document. tests/setup.ts enables Vue Test Utils' enableAutoUnmount(afterEach). In the Time spec, 0 to 6 leftover forms were in the document before each test without it, and 0 with it. Snapshots are unchanged.

Tests

• test/coreOnly.test.ts makes requiring ajv / ajv-formats throw, then loads the entry point. It covers:

  • the Ajv helpers being absent;
  • validating through a Form Validator with no Ajv instance;
  • using an ajv instance passed in the options;
  • NoValidation;
  • init without a validator throwing;
  • schema-based rules evaluating.

  If the entry point imports validator.ts, all six fail with 'ajv' was loaded by @jsonforms/core/core-only.

• test/defaultAjv.test.ts: @jsonforms/core still creates and uses a default Ajv instance and exports the Ajv helpers.

• Core: 538 passing, plus the existing known failure. Lint and Prettier are clean, and all packages build.

• Other packages, all passing: React, Vanilla, Material (465), Vue, Vue Vanilla (93), Vue Vuetify (111), Angular and Angular Material.

Bundle size

An app using core directly with a Form Validator (@cfworker/json-schema) and its own Lit renderers, measured with esbuild, minified, gzip -9:

Import	min	gzip
@jsonforms/core	566.2 kB	136.0 kB
@jsonforms/core/core-only	436.3 kB	96.4 kB

The core-only bundle contains no ajv or ajv-formats modules. It also runs under a CSP without 'unsafe-eval' with no violations.

Open question

With no validator configured, the core-only entry point throws rather than silently skipping validation, so forms relying on required checks can't lose them unnoticed. Happy to change that if you'd prefer otherwise.