lion/packages/ui/components/validate-messages/src/per-entrypoint
2024-02-13 11:58:37 +01:00
..
loadComboboxMessagesNoSideEffects.js feat: split up validate-messages per entrypoint for smarter bundling 2024-02-13 11:58:37 +01:00
loadFormCoreMessagesNoSideEffects.js feat: split up validate-messages per entrypoint for smarter bundling 2024-02-13 11:58:37 +01:00
loadInputTelMessagesNoSideEffects.js feat: split up validate-messages per entrypoint for smarter bundling 2024-02-13 11:58:37 +01:00
README.md feat: split up validate-messages per entrypoint for smarter bundling 2024-02-13 11:58:37 +01:00

For optimized bundling, it's reccommended to load feedback messages per entrypoint. For instance, when you only use form-core in your app:

import { LionInputTel } from '@lion/ui/input-tel.js';
import { getLocalizeManager } from '@lion/ui/localize-no-side-effects.js';
import { loadInputTelMessagesNoSideEffects } from '@lion/ui/validate-messages-no-side-effects.js';

export class MyInputTel extends LionInputTel {
  constructor() {
    super();
    loadInputTelMessagesNoSideEffects({ localize: getLocalizeManager() });
  }
}

This prevents you from loading unused entrypoints like input-tel (which loads a full phone validation library) etc.