@lion/ui 0.22.0 → 0.23.0

package/docs/guides/how-to/create-a-custom-field.md

@@ -87,9 +87,9 @@ if (!customElements.get('dummy-slider')) {
 }
 ```
 
-Custom Fields can be created in just a few steps. All you need is an interaction element (like for instance a slider, a listbox or a combobox) and connect it to the [LionField](https://github.com/ing-bank/lion/blob/1e44a873eb492168e7e3d2f5c120371d950b9e03/docs/components/input/overview.md).
+Custom Fields can be created in just a few steps. All you need is an interaction element (like for instance a slider, a listbox or a combobox) and connect it to the [LionField](https://github.com/ing-bank/lion/blob/4649554021224763994601dd8d202c511d35013e/docs/components/input/overview.md).
 
-> In case you want to extend a native element, follow [Extend a native Input](https://github.com/ing-bank/lion/blob/1e44a873eb492168e7e3d2f5c120371d950b9e03/docs/guides/how-to/extend-a-native-input.md).
+> In case you want to extend a native element, follow [Extend a native Input](https://github.com/ing-bank/lion/blob/4649554021224763994601dd8d202c511d35013e/docs/guides/how-to/extend-a-native-input.md).
 
 ## A) an interaction element
 
@@ -138,7 +138,7 @@ export const createAnInteractiveElement = () => {
 ## B) your LionField extension
 
 Now we want to integrate the slider in our form system to enrich the user interface, get
-validation support and all other [benefits of LionField](https://github.com/ing-bank/lion/blob/1e44a873eb492168e7e3d2f5c120371d950b9e03/docs/components/input/overview.md).
+validation support and all other [benefits of LionField](https://github.com/ing-bank/lion/blob/4649554021224763994601dd8d202c511d35013e/docs/components/input/overview.md).
 We start by creating a component `<slider-field>` that extends from `LionField`.
 Then we follow the steps below:
 
@@ -151,7 +151,7 @@ Then we follow the steps below:
 
   The `user-input-changed` event is listened to by the FormatMixin: it should be regarded as the
   equivalent of the `input` event of the platform, but for custom built interaction elements.
-  You now synchronized [modelValue](https://github.com/ing-bank/lion/blob/1e44a873eb492168e7e3d2f5c120371d950b9e03/docs/fundamentals/systems/form/model-value.md), which can be regarded as
+  You now synchronized [modelValue](https://github.com/ing-bank/lion/blob/4649554021224763994601dd8d202c511d35013e/docs/fundamentals/systems/form/model-value.md), which can be regarded as
   the glue to integrate all other functionality like parsing/formatting/serializing, validating,
   tracking interaction states etc.
 
@@ -159,7 +159,7 @@ Then we follow the steps below:
 > because those properties will lose their reactivity (they won't be considered anymore in the
 > update loop of LitElement).
 > Whenever a .modelValue/.formattedValue/.serializedValue needs to be computed, use
-> [parser/formatter/serializer](https://github.com/ing-bank/lion/blob/1e44a873eb492168e7e3d2f5c120371d950b9e03/docs/fundamentals/systems/form/formatting-and-parsing.md)
+> [parser/formatter/serializer](https://github.com/ing-bank/lion/blob/4649554021224763994601dd8d202c511d35013e/docs/fundamentals/systems/form/formatting-and-parsing.md)
 
 Implement with the following code:
 

package/docs/guides/how-to/create-a-form.md

@@ -39,7 +39,7 @@ Large or complex forms might need to be split up into multiple files. This compo
 
 In the latter case: make sure that your components don't have a shadow root. This can be achieved by rendering into Light DOM. The form registration mechanism relies on light dom by design: as soon as you do start to use shadow roots, you will notice that your form components won't register themselves anymore to their parents.
 
-> Today, rendering to light dom is the only way to [stay accessible](https://github.com/ing-bank/lion/blob/1e44a873eb492168e7e3d2f5c120371d950b9e03/docs/fundamentals/rationales/accessibility.md#shadow-roots-and-accessibility).
+> Today, rendering to light dom is the only way to [stay accessible](https://github.com/ing-bank/lion/blob/4649554021224763994601dd8d202c511d35013e/docs/fundamentals/rationales/accessibility.md#shadow-roots-and-accessibility).
 
 ### Example of a component that renders into Light DOM
 
@@ -86,7 +86,7 @@ Extending form components is not recommended for Application Developers: it shou
 This team will add the styling and default configuration needed to make it fit the particular Design System.
 
 With the toolbox provided by the team that creates your Design System, you should be able to build all your forms. Only if you have a really good reason, look into
-[exceptional cases](https://github.com/ing-bank/lion/blob/1e44a873eb492168e7e3d2f5c120371d950b9e03/docs/guides/how-to/#exceptional-cases) below.
+[exceptional cases](https://github.com/ing-bank/lion/blob/4649554021224763994601dd8d202c511d35013e/docs/guides/how-to/#exceptional-cases) below.
 
 ### Exceptional cases
 
@@ -94,8 +94,8 @@ If the form component you need is still missing, you have two options:
 
 - is it a generic primitive that should be part of Lion? Request it in [Lion discussions](https://github.com/ing-bank/lion/discussions)
 - is it a non generic component that is unique to your app?
-  - follow [create a custom field](https://github.com/ing-bank/lion/blob/1e44a873eb492168e7e3d2f5c120371d950b9e03/docs/guides/how-to/create-a-custom-field.md)
-  - follow [extend a native input](https://github.com/ing-bank/lion/blob/1e44a873eb492168e7e3d2f5c120371d950b9e03/docs/guides/how-to/extend-a-native-input.md)
+  - follow [create a custom field](https://github.com/ing-bank/lion/blob/4649554021224763994601dd8d202c511d35013e/docs/guides/how-to/create-a-custom-field.md)
+  - follow [extend a native input](https://github.com/ing-bank/lion/blob/4649554021224763994601dd8d202c511d35013e/docs/guides/how-to/extend-a-native-input.md)
 
 It's also possible to extend other components, like LionListbox or LionCombobox. You need to be aware that you're building on top of protected apis.
 Changing/overriding functionality is only recommended if the source code in `form-core` is fully understood.

package/docs/guides/how-to/extend-a-native-input.md

@@ -23,9 +23,9 @@ import '../../fundamentals/systems/form/assets/h-output.js';
 loadDefaultFeedbackMessages();
 ```
 
-Input fields can be created by extending [LionInput](https://github.com/ing-bank/lion/blob/1e44a873eb492168e7e3d2f5c120371d950b9e03/docs/components/input/overview.md).
+Input fields can be created by extending [LionInput](https://github.com/ing-bank/lion/blob/4649554021224763994601dd8d202c511d35013e/docs/components/input/overview.md).
 
-> In case you want to wrap a custom form element, follow [Create a custom Field](https://github.com/ing-bank/lion/blob/1e44a873eb492168e7e3d2f5c120371d950b9e03/docs/guides/how-to/create-a-custom-field.md).
+> In case you want to wrap a custom form element, follow [Create a custom Field](https://github.com/ing-bank/lion/blob/4649554021224763994601dd8d202c511d35013e/docs/guides/how-to/create-a-custom-field.md).
 
 For this tutorial, we create an input that wraps native `input[type=datetime-local]`.
 This is as simple as adding a type:

package/docs/guides/how-to/index.md

@@ -22,4 +22,4 @@ Whether you're just getting started with Lion, building your first form, extendi
 - Build custom form fields tailored to your needs
 - Follow proven patterns and best practices used by the Lion community
 
-If you can't find what you're looking for, check out our [Fundamentals](../../fundamentals/) section for deeper conceptual knowledge, or visit our [Components](https://github.com/ing-bank/lion/blob/1e44a873eb492168e7e3d2f5c120371d950b9e03/docs/components) documentation for detailed API references.
+If you can't find what you're looking for, check out our [Fundamentals](../../fundamentals/) section for deeper conceptual knowledge, or visit our [Components](https://github.com/ing-bank/lion/blob/4649554021224763994601dd8d202c511d35013e/docs/components) documentation for detailed API references.

package/docs/guides/index.md

@@ -22,9 +22,9 @@ Developers consuming our web components inside an application (not extending the
 `Application Developers` are only allowed to interact with `public` properties and methods.
 Can be abbreviated as `AD`. Sometimes also called `Consuming Developer`.
 
-- [Definitions and Terms](https://github.com/ing-bank/lion/blob/1e44a873eb492168e7e3d2f5c120371d950b9e03/docs/guides/principles/definitions-and-terms.md)
-- [Styling](https://github.com/ing-bank/lion/blob/1e44a873eb492168e7e3d2f5c120371d950b9e03/docs/guides/principles/styling.md)
-- [Scoped Elements](https://github.com/ing-bank/lion/blob/1e44a873eb492168e7e3d2f5c120371d950b9e03/docs/guides/principles/scoped-elements.md)
+- [Definitions and Terms](https://github.com/ing-bank/lion/blob/4649554021224763994601dd8d202c511d35013e/docs/guides/principles/definitions-and-terms.md)
+- [Styling](https://github.com/ing-bank/lion/blob/4649554021224763994601dd8d202c511d35013e/docs/guides/principles/styling.md)
+- [Scoped Elements](https://github.com/ing-bank/lion/blob/4649554021224763994601dd8d202c511d35013e/docs/guides/principles/scoped-elements.md)
 
 ## Extending Developer
 
@@ -32,13 +32,13 @@ Developers extending our web components, for instance: `class MaterialInput exte
 
 Especially for subclassers we have some extra documentation:
 
-- [Subclasser APIs](https://github.com/ing-bank/lion/blob/1e44a873eb492168e7e3d2f5c120371d950b9e03/docs/guides/principles/subclasser-apis.md)
-- [Extend documentation](https://github.com/ing-bank/lion/blob/1e44a873eb492168e7e3d2f5c120371d950b9e03/docs/blog/extending-documentation.md)
+- [Subclasser APIs](https://github.com/ing-bank/lion/blob/4649554021224763994601dd8d202c511d35013e/docs/guides/principles/subclasser-apis.md)
+- [Extend documentation](https://github.com/ing-bank/lion/blob/4649554021224763994601dd8d202c511d35013e/docs/blog/extending-documentation.md)
 
 ## How To
 
 Next to that we have some specific "How To" documentations.
 
-- [Get started](https://github.com/ing-bank/lion/blob/1e44a873eb492168e7e3d2f5c120371d950b9e03/docs/guides/how-to/get-started.md)
-- [Create a custom field](https://github.com/ing-bank/lion/blob/1e44a873eb492168e7e3d2f5c120371d950b9e03/docs/guides/how-to/create-a-custom-field.md)
-- [Extend a native input](https://github.com/ing-bank/lion/blob/1e44a873eb492168e7e3d2f5c120371d950b9e03/docs/guides/how-to/extend-a-native-input.md)
+- [Get started](https://github.com/ing-bank/lion/blob/4649554021224763994601dd8d202c511d35013e/docs/guides/how-to/get-started.md)
+- [Create a custom field](https://github.com/ing-bank/lion/blob/4649554021224763994601dd8d202c511d35013e/docs/guides/how-to/create-a-custom-field.md)
+- [Extend a native input](https://github.com/ing-bank/lion/blob/4649554021224763994601dd8d202c511d35013e/docs/guides/how-to/extend-a-native-input.md)

package/docs/guides/principles/index.md

@@ -22,9 +22,9 @@ Developers consuming our web components inside an application (not extending the
 `Application Developers` are only allowed to interact with `public` properties and methods.
 Can be abbreviated as `AD`. Sometimes also called `Consuming Developer`.
 
-- [Definitions and Terms](https://github.com/ing-bank/lion/blob/1e44a873eb492168e7e3d2f5c120371d950b9e03/docs/guides/principles/definitions-and-terms.md)
-- [Styling](https://github.com/ing-bank/lion/blob/1e44a873eb492168e7e3d2f5c120371d950b9e03/docs/guides/principles/styling.md)
-- [Scoped Elements](https://github.com/ing-bank/lion/blob/1e44a873eb492168e7e3d2f5c120371d950b9e03/docs/guides/principles/scoped-elements.md)
+- [Definitions and Terms](https://github.com/ing-bank/lion/blob/4649554021224763994601dd8d202c511d35013e/docs/guides/principles/definitions-and-terms.md)
+- [Styling](https://github.com/ing-bank/lion/blob/4649554021224763994601dd8d202c511d35013e/docs/guides/principles/styling.md)
+- [Scoped Elements](https://github.com/ing-bank/lion/blob/4649554021224763994601dd8d202c511d35013e/docs/guides/principles/scoped-elements.md)
 
 ## Extending Developer
 
@@ -32,5 +32,5 @@ Developers extending our web components, for instance: `class MaterialInput exte
 
 Especially for subclassers we have some extra documentation:
 
-- [Subclasser APIs](https://github.com/ing-bank/lion/blob/1e44a873eb492168e7e3d2f5c120371d950b9e03/docs/guides/principles/subclasser-apis.md)
-- [Extend documentation](https://github.com/ing-bank/lion/blob/1e44a873eb492168e7e3d2f5c120371d950b9e03/docs/blog/extending-documentation.md)
+- [Subclasser APIs](https://github.com/ing-bank/lion/blob/4649554021224763994601dd8d202c511d35013e/docs/guides/principles/subclasser-apis.md)
+- [Extend documentation](https://github.com/ing-bank/lion/blob/4649554021224763994601dd8d202c511d35013e/docs/blog/extending-documentation.md)

package/docs/guides/principles/styling.md

@@ -30,7 +30,7 @@ Examples for both categories can be found below:
 - Accessibility examples:
   - Content (for instance a caption in a table) can be `visually hidden`: it will be
     readable by screen readers, but invisible for end users.
-  - When an html table is used, we allow [subclassers](https://github.com/ing-bank/lion/blob/1e44a873eb492168e7e3d2f5c120371d950b9e03/docs/guides/principles/subclasser-apis.md) to override the display property (`table-cell`) to `flex`. By putting the proper accessible roles (`role="cell"`) in the markup, we guarantee our markup stays accessible.
+  - When an html table is used, we allow [subclassers](https://github.com/ing-bank/lion/blob/4649554021224763994601dd8d202c511d35013e/docs/guides/principles/subclasser-apis.md) to override the display property (`table-cell`) to `flex`. By putting the proper accessible roles (`role="cell"`) in the markup, we guarantee our markup stays accessible.
 
 Although Lion components try to stay as unbiased as possible with regard to styling, defaults will be needed. In these cases we try to follow the platform as much as possible. If the platform doesn't provide defaults, the largest common denominator across existing UI systems is taken as a lead.
 

package/exports/define/lion-item.js

@@ -0,0 +1,3 @@
+import { LionItem } from '../menu.js';
+
+customElements.define('lion-item', LionItem);

package/exports/define/lion-menu.js

@@ -0,0 +1,3 @@
+import { LionMenu } from '../menu.js';
+
+customElements.define('lion-menu', LionMenu);

package/exports/define/lion-menuitem.js

@@ -0,0 +1,3 @@
+import { LionMenuitem } from '../menu.js';
+
+customElements.define('lion-menuitem', LionMenuitem);

package/exports/menu-test-suites.js

@@ -0,0 +1,4 @@
+/* eslint-disable import/no-relative-packages */
+export { runInteractiveListMixinSuite } from '../components/menu/test-suites/InteractiveListMixin.suite.js';
+export { runMultiLevelListMixinSuite } from '../components/menu/test-suites/MultiLevelListMixin.suite.js';
+export { runLionMenuInteractionsSuite } from '../components/menu/test-suites/LionMenuInteractions.suite.js';

package/exports/menu.js

@@ -0,0 +1,3 @@
+/* eslint-disable import/no-relative-packages */
+export { LionMenu } from '../components/menu/src/LionMenu.js';
+export { LionItem, LionMenuitem } from '../components/menu/src/InteractiveListMixin.js';

package/exports/overlays.js

@@ -9,6 +9,8 @@ export { withModalDialogConfig } from '../components/overlays/src/configurations
 export { withDropdownConfig } from '../components/overlays/src/configurations/withDropdownConfig.js';
 export { withTooltipConfig } from '../components/overlays/src/configurations/withTooltipConfig.js';
 export { withPopoverConfig } from '../components/overlays/src/configurations/withPopoverConfig.js';
+export { withClickInteraction } from '../components/overlays/src/configurations/visibility-trigger-partials/withClickInteraction.js';
+export { withHoverInteraction } from '../components/overlays/src/configurations/visibility-trigger-partials/withHoverInteraction.js';
 
 export { deepContains } from '../components/overlays/src/utils/deep-contains.js';
 // re-export via this entrypoint for backwards compatibility
@@ -20,3 +22,7 @@ export {
 } from '../components/overlays/src/utils/inert-siblings.js';
 
 export { overlays } from '../components/overlays/src/singleton.js';
+
+/**
+ * @typedef {import('../components/overlays/types/OverlayConfig.js').OverlayConfig} OverlayConfig
+ */

package/menu-test-suites.js

@@ -0,0 +1,4 @@
+/* eslint-disable import/no-relative-packages */
+export { runInteractiveListMixinSuite } from './components/menu/test-suites/InteractiveListMixin.suite.js';
+export { runMultiLevelListMixinSuite } from './components/menu/test-suites/MultiLevelListMixin.suite.js';
+export { runLionMenuInteractionsSuite } from './components/menu/test-suites/LionMenuInteractions.suite.js';

package/menu.js

@@ -0,0 +1,3 @@
+/* eslint-disable import/no-relative-packages */
+export { LionMenu } from './components/menu/src/LionMenu.js';
+export { LionItem, LionMenuitem } from './components/menu/src/InteractiveListMixin.js';

package/overlays.js

@@ -7,6 +7,8 @@ export { withModalDialogConfig } from './components/overlays/src/configurations/
 export { withDropdownConfig } from './components/overlays/src/configurations/withDropdownConfig.js';
 export { withTooltipConfig } from './components/overlays/src/configurations/withTooltipConfig.js';
 export { withPopoverConfig } from './components/overlays/src/configurations/withPopoverConfig.js';
+export { withClickInteraction } from './components/overlays/src/configurations/visibility-trigger-partials/withClickInteraction.js';
+export { withHoverInteraction } from './components/overlays/src/configurations/visibility-trigger-partials/withHoverInteraction.js';
 export { deepContains } from './components/overlays/src/utils/deep-contains.js';
 // re-export via this entrypoint for backwards compatibility
 export { getDeepActiveElement } from './components/core/src/getDeepActiveElement.js';
@@ -16,3 +18,7 @@ export {
   setSiblingsInert,
 } from './components/overlays/src/utils/inert-siblings.js';
 export { overlays } from './components/overlays/src/singleton.js';
+
+/**
+ * @typedef {import('../components/overlays/types/OverlayConfig.js').OverlayConfig} OverlayConfig
+ */

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lion/ui",
-  "version": "0.22.0",
+  "version": "0.23.0",
   "description": "A package of extendable web components",
   "license": "MIT",
   "author": "ing-bank",
@@ -81,6 +81,7 @@
     "dist-types",
     "docs",
     "exports",
+    "vendor",
     "vscode.css-custom-data.json",
     "vscode.html-custom-data.json",
     "web-types.json",
@@ -93,10 +94,12 @@
     "debug:firefox": "cd ../../ && npm run debug:firefox",
     "debug:webkit": "cd ../../ && npm run debug:webkit",
     "generate-lion-exports": "node ./scripts/generate-lion-exports.js",
+    "prepack": "node ./scripts/prepare-vendored-phone.js",
     "prepublishOnly": "npm run types && npm run create-npm-publish-docs && npm run publish-docs && npm run custom-elements-manifest && npm run generate-lion-exports",
     "publish-docs": "node ../../packages-node/publish-docs/src/cli.js --github-url https://github.com/ing-bank/lion/ --git-root-dir ../../",
     "test": "cd ../../ && npm run test:browser",
     "types": "wireit",
+    "types-check-consumer": "node ./scripts/check-consumer-types.js",
     "types-check-only": "tsc --project tsconfig-check-only.json",
     "types-restore-visibility": "node ./scripts/types-restore-visibility.js"
   },
@@ -113,11 +116,14 @@
     "@open-wc/scoped-elements": "^3.0.6",
     "@popperjs/core": "^2.11.8",
     "autosize": "^6.0.0",
-    "awesome-phonenumber": "^7.8.0",
+    "awesome-phonenumber": "file:vendor/awesome-phonenumber-7.9.0-tlouisse.libphonenumber-9.0.41.tgz",
     "ibantools": "^4.3.9",
     "lit": "^3.1.2",
     "singleton-manager": "^1.8.0"
   },
+  "bundledDependencies": {
+    "0": "awesome-phonenumber"
+  },
   "keywords": [
     "design-system",
     "lion",
@@ -130,7 +136,7 @@
   "web-types": "./web-types.json",
   "wireit": {
     "types": {
-      "command": "tsc --build --pretty && npm run types-restore-visibility",
+      "command": "tsc --build --pretty && npm run types-restore-visibility && npm run types-check-consumer",
       "dependencies": [
         "../singleton-manager:types"
       ],
@@ -138,7 +144,8 @@
         "exports/**/*.js",
         "components/**/*",
         "tsconfig.json",
-        "scripts/types-restore-visibility.js"
+        "scripts/types-restore-visibility.js",
+        "scripts/check-consumer-types.js"
       ],
       "output": [
         "dist-types/**"

package/vendor/README.md

@@ -0,0 +1,61 @@
+# Vendored awesome-phonenumber
+
+This temporary artifact replaces the registry dependency until the next upstream
+awesome-phonenumber release incorporating the required metadata is available.
+
+- Package: `awesome-phonenumber@7.9.0-tlouisse.libphonenumber-9.0.41`.
+- Google libphonenumber: `v9.0.41`.
+- Source: [tlouisse/awesome-phonenumber](https://github.com/tlouisse/awesome-phonenumber),
+  commit `b4b6439136053624351f1c0fd8eb200ee867f37f`
+  on branch `hu84jr-ing-phone-package-workflow`, based on upstream `9ff7ec8`.
+- Artifact: `awesome-phonenumber-7.9.0-tlouisse.libphonenumber-9.0.41.tgz`.
+- SHA-256: `855b0476ea7784457e8ec63d4824ff925eed0e339f72e8e05b7eea75a80ec018`.
+- npm integrity:
+  `sha512-v1ZQJG8WeBfH2PFjiZidVnBwXrD/IxNbUbeNVAXltkGdOtZiNN5n/Bllfp601GhkUPByZPvrPjHEj+gT9LnZIQ==`.
+- [Verified packaging workflow](https://github.com/tlouisse/awesome-phonenumber/actions/runs/38529804810):
+  Node 22/npm 10 and local Node 24/npm 11 produced byte-identical artifacts.
+
+## Reproduce
+
+In a separate checkout of the source repository:
+
+```sh
+git checkout b4b6439136053624351f1c0fd8eb200ee867f37f
+yarn install --immutable
+PACK_DESTINATION=/absolute/path/to/artifacts npm run pack
+npm run pack:verify -- /absolute/path/to/artifacts/awesome-phonenumber-7.9.0-tlouisse.libphonenumber-9.0.41.tgz
+shasum -a 256 /absolute/path/to/artifacts/awesome-phonenumber-7.9.0-tlouisse.libphonenumber-9.0.41.tgz
+```
+
+The source workflow rebuilds Google's metadata and verifies the installed tarball's
+CommonJS, ESM, and TypeScript entrypoints. The artifact has no runtime dependencies.
+It contains the upstream README and `LICENSE`, `LICENSE.libphonenumber`, and
+`LICENSE.closure-library`; these notices also accompany the bundled installed
+package in published Lion packages.
+
+## Packaging and removal
+
+The package-relative dependency is accompanied by `bundledDependencies` so consumers
+receive the installed package, not an unresolved path into this repository.
+The private root declares the same tarball as a development dependency so npm
+hoists and installs it during `npm ci`; otherwise npm treats the workspace's
+bundled dependency as already provided and skips installing it. Both declarations
+must point to this exact artifact. The old docs package retains its registry version.
+The temporary `prepack` helper verifies the checksum, installs only this artifact
+in an isolated temporary prefix using offline npm, copies the npm-installed package
+into the local bundle, and cleans up the temporary prefix. npm does not bundle
+dependencies hoisted outside the workspace. The helper disables dependency scripts
+and lockfile writes, cannot fetch network dependencies, and does not reinstall
+Lion's other runtime dependencies.
+Run `npm ci`, `npm run prepublishOnly --workspace @lion/ui`, and
+`npm pack --workspace @lion/ui --pack-destination /absolute/path/to/artifacts`.
+Install the resulting Lion tarball in a fresh consumer outside the checkout, with
+`npm install --offline`, and verify the bundled phone package resolves and accepts
+the French Guiana premium-rate example `+594890123456`.
+
+When the next upstream awesome-phonenumber release incorporates this metadata,
+restore the registry dependency, remove bundling and this vendor directory, update
+the lockfile, remove the root development dependency, and retain the metadata
+regression test. Remove the temporary `prepack` lifecycle and
+`scripts/prepare-vendored-phone.js` helper too. See the root README for
+the complete removal checklist.

package/vscode.html-custom-data.json

@@ -104,7 +104,7 @@
     },
     {
       "name": "lion-combobox",
-      "description": "LionCombobox: implements the wai-aria combobox design pattern and integrates it as a Lion\nFormControl\n\n\n---\n\n\n\n\n### **Events:**\n - **model-value-changed** - undefined\n\n### **Methods:**\n - **matchCondition(option: _LionOption_, textboxValue: _string_)** - When the preconfigurable `match-mode` conditions are not sufficient,\none can define a custom matching function.\n- **parser(value: _string|string[]_): _*_** - Converts viewValue to modelValue\n- **_autoSelectCondition()** - When this condition is false, an end user will have to manually select a suggested\noption from the list (by default when autocomplete is 'none' or 'list').\nFor autocomplete 'both' or 'inline', it will automatically select on a match.\n- **_getTextboxValueFromOption(option: _LionOption_): _string_** - Return the value to be used for the input value\n- **_handleAutocompletion()** - Handles autocompletion. This entails:\n- list: shows a list on keydown character press\n- filter: filters list of potential matches according to matchmode or provided matchCondition\n- focus: automatically focuses closest match (makes it the activedescendant)\n- check: automatically checks/selects closest match when selection-follows-focus is enabled\n(this is the default configuration)\n- complete: completes the textbox value inline (the 'missing characters' will be added as\nselected text)\n\n### **Slots:**\n - **listbox** - The listbox element for the combobox, e.g. <lion-options>\n- **selection-display** - The selection display element for the combobox, e.g. <lion-selection-display>",
+      "description": "LionCombobox: implements the wai-aria combobox design pattern and integrates it as a Lion\nFormControl\n\n\n---\n\n\n\n\n### **Events:**\n - **model-value-changed** - undefined\n- **opened-changed** - undefined\n\n### **Methods:**\n - **close()** - Hides the overlay\n- **matchCondition(option: _LionOption_, textboxValue: _string_)** - When the preconfigurable `match-mode` conditions are not sufficient,\none can define a custom matching function.\n- **open()** - Shows the overlay\n- **parser(value: _string|string[]_): _*_** - Converts viewValue to modelValue\n- **repositionOverlay()** - Sometimes it's needed to recompute Popper position of an overlay, for instance when we have\nan opened combobox and the surrounding context changes (the space consumed by the textbox\nincreases vertically)\n- **toggle()** - Toggles the overlay\n- **_autoSelectCondition()** - When this condition is false, an end user will have to manually select a suggested\noption from the list (by default when autocomplete is 'none' or 'list').\nFor autocomplete 'both' or 'inline', it will automatically select on a match.\n- **_getFocusableInvokerEl(focusableElOrWrapper: _Element | null | undefined_): _Element | null_** - Returns the element that can actually receive focus inside the passed\ninvoker (wrapper) element: the element itself when it is focusable,\notherwise the first focusable descendant.\n- **_getTextboxValueFromOption(option: _LionOption_): _string_** - Return the value to be used for the input value\n- **_handleAutocompletion()** - Handles autocompletion. This entails:\n- list: shows a list on keydown character press\n- filter: filters list of potential matches according to matchmode or provided matchCondition\n- focus: automatically focuses closest match (makes it the activedescendant)\n- check: automatically checks/selects closest match when selection-follows-focus is enabled\n(this is the default configuration)\n- complete: completes the textbox value inline (the 'missing characters' will be added as\nselected text)\n- **_isPermanentlyDisconnected(): _Promise<boolean>_** - When we're moving around in dom, disconnectedCallback gets called.\nBefore we decide to teardown, let's wait to see if we were not just moving nodes around.\n- **_setOpenedWithoutPropertyEffects(newOpened: _boolean_)** - When the opened state is changed by an Application Developer,cthe OverlayController is\nrequested to show/hide. It might happen that this request is not honoured\n(intercepted in before-hide for instance), so that we need to sync the controller state\nto this webcomponent again, preventing eternal loops.\n\n### **Slots:**\n - **listbox** - The listbox element for the combobox, e.g. <lion-options>\n- **selection-display** - The selection display element for the combobox, e.g. <lion-selection-display>",
       "attributes": [
         {
           "name": "autocomplete",
@@ -132,14 +132,26 @@
           "values": []
         },
         { "name": "allow-custom-choice", "values": [] },
-        { "name": "__shouldAutocompleteNextUpdate", "values": [] }
+        { "name": "__shouldAutocompleteNextUpdate", "values": [] },
+        {
+          "name": "opened",
+          "description": "If you add the opened attribute a dialog will be opened on page load. The invoker can be left out\nin case the user does not need to be able to reopen the dialog.",
+          "values": []
+        }
       ],
       "references": []
     },
     {
       "name": "lion-dialog",
-      "description": "\n\n\n---\n\n\n",
-      "attributes": [{ "name": "is-alert-dialog", "values": [] }],
+      "description": "\n\n\n---\n\n\n\n\n### **Events:**\n - **opened-changed** - undefined\n\n### **Methods:**\n - **close()** - Hides the overlay\n- **open()** - Shows the overlay\n- **repositionOverlay()** - Sometimes it's needed to recompute Popper position of an overlay, for instance when we have\nan opened combobox and the surrounding context changes (the space consumed by the textbox\nincreases vertically)\n- **toggle()** - Toggles the overlay\n- **_getFocusableInvokerEl(focusableElOrWrapper: _Element | null | undefined_): _Element | null_** - Returns the element that can actually receive focus inside the passed\ninvoker (wrapper) element: the element itself when it is focusable,\notherwise the first focusable descendant.\n- **_isPermanentlyDisconnected(): _Promise<boolean>_** - When we're moving around in dom, disconnectedCallback gets called.\nBefore we decide to teardown, let's wait to see if we were not just moving nodes around.\n- **_setOpenedWithoutPropertyEffects(newOpened: _boolean_)** - When the opened state is changed by an Application Developer,cthe OverlayController is\nrequested to show/hide. It might happen that this request is not honoured\n(intercepted in before-hide for instance), so that we need to sync the controller state\nto this webcomponent again, preventing eternal loops.",
+      "attributes": [
+        { "name": "is-alert-dialog", "values": [] },
+        {
+          "name": "opened",
+          "description": "If you add the opened attribute a dialog will be opened on page load. The invoker can be left out\nin case the user does not need to be able to reopen the dialog.",
+          "values": []
+        }
+      ],
       "references": []
     },
     {
@@ -295,6 +307,7 @@
           "values": []
         },
         { "name": "currency", "values": [] },
+        { "name": "currency-label", "values": [] },
         { "name": "modelValue", "values": [] },
         {
           "name": "readonly",
@@ -311,6 +324,7 @@
       "description": "`LionInputAmount` is a class for an amount custom form element (`<lion-input-amount>`).\n\n\n---\n\n\n\n\n### **Events:**\n - **user-input-changed** - undefined\n\n### **Methods:**\n - **clear()** - Clears modelValue.\nInteraction states are not cleared (use resetInteractionState for this)\n- **reset()** - Resets modelValue to initial value.\nInteraction states are cleared\n- **_connectSlotMixin()** - Upon connecting slot mixin, we should check if\nthe required slot was created by the slot mixin,\nand if so, we should execute the currency changed flow\nwhich evaluates whether the slot node should be\nremoved for invalid currencies\n- **_onChange(ev: _Event=_)** - Dispatches custom bubble event",
       "attributes": [
         { "name": "currency", "values": [] },
+        { "name": "currency-label", "values": [] },
         { "name": "modelValue", "values": [] },
         {
           "name": "readonly",
@@ -339,13 +353,18 @@
     },
     {
       "name": "lion-input-datepicker",
-      "description": "\n\n\n---\n\n\n\n\n### **Events:**\n - **user-input-changed** - undefined\n\n### **Methods:**\n - **clear()** - Clears modelValue.\nInteraction states are not cleared (use resetInteractionState for this)\n- **reset()** - Resets modelValue to initial value.\nInteraction states are cleared\n- **_calendarTemplate()** - Subclassers can replace this with their custom extension of\nLionCalendar, like `<my-calendar id=\"calendar\"></my-calendar>`\n- **_invokerIconTemplate()** - Subclassers can replace this with their custom extension invoker icon\n- **_invokerTemplate()** - Subclassers can replace this with their custom extension invoker,\nlike `<my-button><calendar-icon></calendar-icon></my-button>`\n- **_onCalendarOverlayOpened()** - Lifecycle callback for subclassers\n- **_onCalendarUserSelectedChanged({ target: { selectedDate } }, opts: _{ target: { selectedDate: Date }}_)** - Triggered when a user selects a date from the calendar overlay\n- **_onChange(ev: _Event=_)** - Dispatches custom bubble event\n- **_onValidatorUpdated(e: _Event|CustomEvent_, metaData: _{validator: Validator}_)** - Responsible for listening param change event and\nsync the calendar dates with the updated validator params\n- **_overlayTemplate()** - Defining this overlay as a templates from OverlayMixin\nthis is our source to give as .contentNode to OverlayController.\nImportant: do not change the name of this method.",
+      "description": "\n\n\n---\n\n\n\n\n### **Events:**\n - **opened-changed** - undefined\n- **user-input-changed** - undefined\n\n### **Methods:**\n - **clear()** - Clears modelValue.\nInteraction states are not cleared (use resetInteractionState for this)\n- **close()** - Hides the overlay\n- **open()** - Shows the overlay\n- **repositionOverlay()** - Sometimes it's needed to recompute Popper position of an overlay, for instance when we have\nan opened combobox and the surrounding context changes (the space consumed by the textbox\nincreases vertically)\n- **reset()** - Resets modelValue to initial value.\nInteraction states are cleared\n- **toggle()** - Toggles the overlay\n- **_calendarTemplate()** - Subclassers can replace this with their custom extension of\nLionCalendar, like `<my-calendar id=\"calendar\"></my-calendar>`\n- **_getFocusableInvokerEl(focusableElOrWrapper: _Element | null | undefined_): _Element | null_** - Returns the element that can actually receive focus inside the passed\ninvoker (wrapper) element: the element itself when it is focusable,\notherwise the first focusable descendant.\n- **_invokerIconTemplate()** - Subclassers can replace this with their custom extension invoker icon\n- **_invokerTemplate()** - Subclassers can replace this with their custom extension invoker,\nlike `<my-button><calendar-icon></calendar-icon></my-button>`\n- **_isPermanentlyDisconnected(): _Promise<boolean>_** - When we're moving around in dom, disconnectedCallback gets called.\nBefore we decide to teardown, let's wait to see if we were not just moving nodes around.\n- **_onCalendarOverlayOpened()** - Lifecycle callback for subclassers\n- **_onCalendarUserSelectedChanged({ target: { selectedDate } }, opts: _{ target: { selectedDate: Date }}_)** - Triggered when a user selects a date from the calendar overlay\n- **_onChange(ev: _Event=_)** - Dispatches custom bubble event\n- **_onValidatorUpdated(e: _Event|CustomEvent_, metaData: _{validator: Validator}_)** - Responsible for listening param change event and\nsync the calendar dates with the updated validator params\n- **_overlayTemplate()** - Defining this overlay as a templates from OverlayMixin\nthis is our source to give as .contentNode to OverlayController.\nImportant: do not change the name of this method.\n- **_setOpenedWithoutPropertyEffects(newOpened: _boolean_)** - When the opened state is changed by an Application Developer,cthe OverlayController is\nrequested to show/hide. It might happen that this request is not honoured\n(intercepted in before-hide for instance), so that we need to sync the controller state\nto this webcomponent again, preventing eternal loops.",
       "attributes": [
         {
           "name": "calendar-heading",
           "description": "The heading to be added on top of the calendar overlay.\nNaming chosen from an Application Developer perspective.\nFor a Subclasser 'calendarOverlayHeading' would be more appropriate.",
           "values": []
         },
+        {
+          "name": "opened",
+          "description": "If you add the opened attribute a dialog will be opened on page load. The invoker can be left out\nin case the user does not need to be able to reopen the dialog.",
+          "values": []
+        },
         { "name": "modelValue", "values": [] },
         {
           "name": "readonly",
@@ -575,6 +594,45 @@
       "attributes": [{ "name": "tabindex", "values": [] }],
       "references": [null]
     },
+    {
+      "name": "lion-menu",
+      "description": "LionMenu is a list of choices. Whether it opens as an overlay or as a regular\ncollapsible (disclosure) is configurable via `openable-mode`.\n\nN.B. the actual switching will be delegated to the disclosure system (see the\nvisibility-toggle controller); for now `disclosure` is the default.\n\n\n---\n\n\n\n\n### **Methods:**\n - **setCheckedIndex(index: _number_)** - Allows groups within one level. In case we deal with menuitemcheckbox,\nwe treat it as multiple choice group",
+      "attributes": [
+        {
+          "name": "openable-mode",
+          "description": "Terminology aligned with https://open-ui.org/components/openable.explainer/",
+          "values": [{ "name": "disclosure" }, { "name": "overlay" }]
+        },
+        {
+          "name": "bar",
+          "description": "Enable bar to use [role=\"menubar\"] and horizontal navigation",
+          "values": []
+        }
+      ],
+      "references": [null]
+    },
+    {
+      "name": "lion-item",
+      "description": "Lightweight component supporting InteractiveListItemRole as a type.\n\nSupports:\n- 1. menu item\n<lion-item> Item label </lion-item>\n- 2. sub menu\n<lion-item>\n  <button slot=\"invoker\"> Item label </button>\n  <lion-menu slot=\"subitems\"> ... </lion-menu>\n</lion-item>\n\nSets the role property on the right element. For case 1, this would be the item itself,\nfor case 2 it would be the [slot=invoker].\n\n\n---\n\n\n",
+      "attributes": [
+        {
+          "name": "type",
+          "values": [{ "name": "InteractiveListItemRole" }, { "name": "''" }]
+        }
+      ],
+      "references": [null]
+    },
+    {
+      "name": "lion-menuitem",
+      "description": "\n\n\n---\n\n\n",
+      "attributes": [
+        {
+          "name": "type",
+          "values": [{ "name": "InteractiveListItemRole" }, { "name": "''" }]
+        }
+      ],
+      "references": []
+    },
     {
       "name": "lion-pagination",
       "description": "`LionPagination` is a class for custom Pagination element (`<lion-pagination>` web component).\n\n\n---\n\n\n\n\n### **Methods:**\n - **first()** - Go to first page\n- **goto(pageNumber: _number_)** - Go to the specific page\n- **last()** - Go to the last page\n- **next()** - Go next in pagination\n- **previous()** - Go back in pagination\n- **_disabledButtonTemplate(label: _String_): _TemplateResult_** - Get disabled button template.\nThis method can be overridden to apply customized template in wrapper.\n- **_prevNextButtonTemplate(label: _String_, pageNumber: _Number_, namespace: _String_): _TemplateResult_** - Get next or previous button template.\nThis method can be overridden to apply customized template in wrapper.\n- **_prevNextIconTemplate(label: _String_): _TemplateResult_** - Get previous or next button template.\nThis method can be overridden to apply customized template in wrapper.\n- **_renderNavList(): _TemplateResult[]_** - Render navigation list",
@@ -618,7 +676,7 @@
     },
     {
       "name": "lion-field-with-select",
-      "description": "LionSelectRich: wraps the <lion-listbox> element\n\n\n---\n\n\n\n\n### **Events:**\n - **blur** - undefined\n\n### **Methods:**\n - **_alignInvokerWidth()** - Align invoker width with content width\nMake sure display is not set to \"none\" while calculating the content width\n- **_getCheckedElements()** - In the select disabled options are still going to a possible value for example\nwhen prefilling or programmatically setting it.\n- **_noDefaultSelectedInheritsWidth()** - With no selected element, we should override the inheritsReferenceWidth in most cases.\nBy default, we will set it to 'min', and then set it back to what it was initially when\nsomething is selected.\nAs a subclasser you can override this behavior.",
+      "description": "LionSelectRich: wraps the <lion-listbox> element\n\n\n---\n\n\n\n\n### **Events:**\n - **blur** - undefined\n- **opened-changed** - undefined\n\n### **Methods:**\n - **close()** - Hides the overlay\n- **open()** - Shows the overlay\n- **repositionOverlay()** - Sometimes it's needed to recompute Popper position of an overlay, for instance when we have\nan opened combobox and the surrounding context changes (the space consumed by the textbox\nincreases vertically)\n- **toggle()** - Toggles the overlay\n- **_alignInvokerWidth()** - Align invoker width with content width\nMake sure display is not set to \"none\" while calculating the content width\n- **_getCheckedElements()** - In the select disabled options are still going to a possible value for example\nwhen prefilling or programmatically setting it.\n- **_getFocusableInvokerEl(focusableElOrWrapper: _Element | null | undefined_): _Element | null_** - Returns the element that can actually receive focus inside the passed\ninvoker (wrapper) element: the element itself when it is focusable,\notherwise the first focusable descendant.\n- **_isPermanentlyDisconnected(): _Promise<boolean>_** - When we're moving around in dom, disconnectedCallback gets called.\nBefore we decide to teardown, let's wait to see if we were not just moving nodes around.\n- **_noDefaultSelectedInheritsWidth()** - With no selected element, we should override the inheritsReferenceWidth in most cases.\nBy default, we will set it to 'min', and then set it back to what it was initially when\nsomething is selected.\nAs a subclasser you can override this behavior.\n- **_setOpenedWithoutPropertyEffects(newOpened: _boolean_)** - When the opened state is changed by an Application Developer,cthe OverlayController is\nrequested to show/hide. It might happen that this request is not honoured\n(intercepted in before-hide for instance), so that we need to sync the controller state\nto this webcomponent again, preventing eternal loops.",
       "attributes": [
         {
           "name": "navigate-within-invoker",
@@ -634,7 +692,12 @@
             { "name": "auto" }
           ]
         },
-        { "name": "single-option", "values": [] }
+        { "name": "single-option", "values": [] },
+        {
+          "name": "opened",
+          "description": "If you add the opened attribute a dialog will be opened on page load. The invoker can be left out\nin case the user does not need to be able to reopen the dialog.",
+          "values": []
+        }
       ],
       "references": []
     },
@@ -763,12 +826,17 @@
     },
     {
       "name": "lion-tooltip",
-      "description": "\n\n\n---\n\n\n",
+      "description": "\n\n\n---\n\n\n\n\n### **Events:**\n - **opened-changed** - undefined\n\n### **Methods:**\n - **close()** - Hides the overlay\n- **open()** - Shows the overlay\n- **repositionOverlay()** - Sometimes it's needed to recompute Popper position of an overlay, for instance when we have\nan opened combobox and the surrounding context changes (the space consumed by the textbox\nincreases vertically)\n- **toggle()** - Toggles the overlay\n- **_getFocusableInvokerEl(focusableElOrWrapper: _Element | null | undefined_): _Element | null_** - Returns the element that can actually receive focus inside the passed\ninvoker (wrapper) element: the element itself when it is focusable,\notherwise the first focusable descendant.\n- **_isPermanentlyDisconnected(): _Promise<boolean>_** - When we're moving around in dom, disconnectedCallback gets called.\nBefore we decide to teardown, let's wait to see if we were not just moving nodes around.\n- **_setOpenedWithoutPropertyEffects(newOpened: _boolean_)** - When the opened state is changed by an Application Developer,cthe OverlayController is\nrequested to show/hide. It might happen that this request is not honoured\n(intercepted in before-hide for instance), so that we need to sync the controller state\nto this webcomponent again, preventing eternal loops.",
       "attributes": [
         {
           "name": "invoker-relation",
           "description": "Decides whether the tooltip invoker text should be considered a description\n(sets aria-describedby) or a label (sets aria-labelledby).",
           "values": [{ "name": "label" }, { "name": "description" }]
+        },
+        {
+          "name": "opened",
+          "description": "If you add the opened attribute a dialog will be opened on page load. The invoker can be left out\nin case the user does not need to be able to reopen the dialog.",
+          "values": []
         }
       ],
       "references": []