Update npm non-major dependencies #117

renovate · 2025-09-11T03:38:21Z

This PR contains the following updates:

Package	Change	Age	Confidence
@conform-to/react (source)	`1.6.0` -> `1.13.3`
@conform-to/zod (source)	`1.7.2` -> `1.13.3`
@digdir/designsystemet-css (source)	`1.1.2` -> `1.7.3`
@digdir/designsystemet-react (source)	`1.1.2` -> `1.7.3`
@digdir/designsystemet-theme (source)	`1.1.1` -> `1.7.3`
@eslint/js (source)	`9.29.0` -> `9.39.1`
@navikt/aksel-icons (source)	`7.24.0` -> `7.33.5`
@playwright/test (source)	`1.53.1` -> `1.56.1`
@react-router/dev (source)	`7.6.2` -> `7.9.6`
@react-router/fs-routes (source)	`7.6.2` -> `7.9.6`
@react-router/node (source)	`7.6.2` -> `7.9.6`
@react-router/serve (source)	`7.6.2` -> `7.9.6`
@types/node (source)	`24.0.4` -> `24.10.1`
@types/react (source)	`19.1.8` -> `19.2.6`
@types/react-dom (source)	`19.1.6` -> `19.2.3`
autoprefixer	`10.4.21` -> `10.4.22`
eslint (source)	`9.29.0` -> `9.39.1`
eslint-import-resolver-typescript	`4.3.5` -> `4.4.4`
eslint-plugin-import	`2.31.0` -> `2.32.0`
globals	`16.2.0` -> `16.5.0`
isbot (source)	`5.1.28` -> `5.1.32`
openapi-typescript (source)	`7.8.0` -> `7.10.1`
openid-client	`6.5.1` -> `6.8.1`
postcss (source)	`8.5.5` -> `8.5.6`
react (source)	`19.1.0` -> `19.2.0`
react-dom (source)	`19.1.0` -> `19.2.0`
react-router (source)	`7.6.2` -> `7.9.6`
tailwindcss (source)	`3.4.17` -> `3.4.18`
typescript (source)	`5.8.3` -> `5.9.3`
typescript-eslint (source)	`8.32.1` -> `8.47.0`
vitest (source)	`3.1.4` -> `3.2.4`
zod (source)	`3.25.67` -> `3.25.76`

Release Notes

edmundhung/conform (@conform-to/react)

`v1.13.3`

Compare Source

What's Changed

Fixed Zod v4 .required() support with coerceFormValue by @chimame (#1084)

Full Changelog: edmundhung/conform@v1.13.2...v1.13.3

`v1.13.2`

Compare Source

What's Changed

Fix change detection to avoid triggering unnecessary change events when a File input or select value hasn't actually changed (#1078)
Updated vitest and vitest/browser dependencies to latest versions by @chimame (#1077)

Full Changelog: edmundhung/conform@v1.13.1...v1.13.2

`v1.13.1`

Compare Source

What's Changed

Fixed a type regression with DefaultValue that prevented setting undefined on required fields when exactOptionalPropertyTypes is enabled. (#1072)

Full Changelog: edmundhung/conform@v1.13.0...v1.13.1

`v1.13.0`

Compare Source

Breaking changes on `future` exports

The following metadata will no longer returns undefined to resolves behavior difference on React 18 and 19 with regards to the defaultValue property:

metadata.defaultValue now returns an empty string '' instead of undefined when no default value is set or the value cannot be serialized
metadata.defaultOptions now returns an empty array [] instead of undefined when no default options are set or the value cannot be serialized
metadata.defaultChecked now explicitly returns false instead of undefined when the field value is not 'on'

What's Changed

The intent.reset() method now accepts an optional defaultValue parameter to reset forms to a different value (#1065)
```
// Clear all fields
<button type="button" onClick={() => intent.reset({ defaultValue: null })}>
  Clear
</button>

// Restore to a specific snapshot
<button type="button" onClick={() => intent.reset({ defaultValue: savedValue })}>
  Restore
</button>
```
Additionally, intent.update() has been optimized to behave more consistently with intent.reset(), with improved type inference when updating form value by not specifying the name option.

Added formRef to useControl hook (#1059)

The useControl hook now exposes a formRef property that provides access to the form element associated with the registered input. This is particularly useful when using useControl with other form-level hooks like useFormData() and useIntent().

const control = useControl({ defaultValue: '' });

// Dispatch intent with useIntent
const intent = useIntent(control.formRef);

// The formRef automatically stays in sync even if the form attribute changes
<input ref={control.register} form="dynamic-form-id" />;

Fixed an issue with coerceFormValue widening the schema type to GenericSchema | GenericSchemaAsync. It now preserves the exact schema type with compatibility to the standard schema types. (#1060)

Full Changelog: edmundhung/conform@v1.12.1...v1.13.0

`v1.12.1`

Compare Source

What's Changed

Fixed an issue where React DevTools would throw an error when inspecting field metadata. The Proxy now handles symbol properties used by React internals gracefully. (#1062)
Fixed insert and update intent type inference when field shape cannot be inferred. (#1063)

Full Changelog: edmundhung/conform@v1.12.0...v1.12.1

`v1.12.0`

Compare Source

What's changed

Metadata Customization

This update introduces a <FormOptionsProvider /> component under the future export. (#1047)

You can now define global form options, including custom metadata properties that match your form component types when integrating with UI libraries or any custom components.

import {
  FormOptionsProvider,
  type BaseMetadata,
} from '@&#8203;conform-to/react/future';
import { TextField } from './components/TextField';

// Define custom metadata properties that matches the type of our custom form components
function defineCustomMetadata<FieldShape, ErrorShape>(
  metadata: BaseMetadata<FieldShape, ErrorShape>,
) {
  return {
    get textFieldProps() {
      return {
        name: metadata.name,
        defaultValue: metadata.defaultValue,
        isInvalid: !metadata.valid,
      } satisfies Partial<React.ComponentProps<typeof TextField>>;
    },
  };
}

// Extend the CustomMetadata interface with our implementation
// This makes the custom metadata types available on all field metadata objects
declare module '@&#8203;conform-to/react/future' {
  interface CustomMetadata<FieldShape, ErrorShape>
    extends ReturnType<typeof defineCustomMetadata<FieldShape, ErrorShape>> {}
}

// Wrap your app with FormOptionsProvider
<FormOptionsProvider
  shouldValidate="onBlur"
  defineCustomMetadata={defineCustomMetadata}
>
  <App />
</FormOptionsProvider>;

// Use custom metadata properties in your components
function Example() {
  const { form, fields } = useForm({
    // shouldValidate now defaults to "onBlur"
  });

  return (
    <form {...form.props}>
      <TextField {...fields.email.textFieldProps} />
    </form>
  );
}

Additionally, you can now customize the base error shape globally using the CustomTypes interface:

declare module '@&#8203;conform-to/react/future' {
  interface CustomTypes {
    errorShape: { message: string; code: string };
  }
}

This restricts the error shape expected from forms and improves type inference when using useField and useFormMetadata.

Improvements

Added ariaInvalid and ariaDescribedBy field metadata (#1047)
Added Zod 4 prefault schema support (#1052) - Thanks @chimame!
Improved docs layout setup (#1051) - Thanks @fiws!
Fixed an issue with checkbox not being marked as touched on form submit with async validation (#1048)
Fixed a bug with default values from Zod 3 default schema not being validated when coercion is enabled (#1050)

Full Changelog: edmundhung/conform@v1.11.0...v1.12.0

`v1.11.0`

Compare Source

What's Changed

Breaking change (Future APIs)

In this release, we simplified some of the type signatures by removing the Metadata generic parameter (#1045):

FormMetadata<ErrorShape = string> (previously FormMetadata<ErrorShape, Metadata>)
FieldMetadata<FieldShape, ErrorShape = string> (previously FieldMetadata<FieldShape, Metadata>)
Fieldset<FieldShape, ErrorShape = string> (previously Fieldset<FieldShape, Metadata>)

Improvements

Added standard schema issue support to report (#1041)

The report helper now accepts standard schema issues directly, eliminating the need to use formatResult in most cases:
```
return report(submission, {
+  error: { issues: result.error.issues },  // Zod
+  error: { issues: result.issues },        // Valibot
-  error: formatResult(result),
});
```
When both issues and formErrors / fieldErrors are provided, they will be merged together, with issues being formatted first:
```
return report(submission, {
  error: {
    issues: result.error.issues,
    formErrors: ['Custom form error'],
  },
});
```
This allows you to pass the validation results from Zod and Valibot to report directly without using formatResult. But it is still useful when you need to customize the error shape.

Added schemaValue property to the onValidate callback argument containing the validated value from successful schema validation. This property is undefined when no schema is provided or when validation fails. (#1046)

const form = useForm({
  schema: z.object({ email: z.string().email() }),
  onValidate({ schemaValue }) {
    if (schemaValue) {
      // Access the validated data: { email: string }
      console.log(schemaValue.email);
    }
  },
});

Full Changelog: edmundhung/conform@v1.10.1...v1.11.0

`v1.10.1`

Compare Source

What's Changed

Fixed an issue with form.getFieldset() requiring a name parameter. This should be optional instead. (#1037 by @luchsamapparat)
Improved the form state setup to fix Next.js prerendering hydration issues (#1039 by @apostolos)

New Contributors

@luchsamapparat made their first contribution in #1037

Full Changelog: edmundhung/conform@v1.10.0...v1.10.1

`v1.10.0`

Compare Source

What's changed

This release brings better Valibot integration with the future useForm hook while also fixing a few rough edges.

Breaking change

The memoize helper has moved into @conform-to/react/future. (#1022 by @chimame)
If you were previously importing it from @conform-to/zod/v3/future or @conform-to/zod/v4/future, you will need to update your imports:
```
- import { memoize } from '@&#8203;conform-to/zod/v4/future';
+ import { memoize } from '@&#8203;conform-to/react/future';
```
No other changes are required.

New in `@conform-to/react/future`

Exposed several internal types, which can be useful if you are building abstractions on top of Conform:
Submission, SubmissionResult, FormContext, FormMetadata, FormRef, FieldMetadata, FieldName, and IntentDispatcher. (#1033)

New in `@conform-to/valibot/future`

Added formatResult helpers for smoother integration with the future useForm hook. (#1018 by @chimame)

Fixes and improvements

Fixed an issue where the valid metadata did not properly consider subfield errors. (#1024)
Fixed an issue where useForm might clear all form values during form submission after a form reset. (#1028)
Inlined types from @standard-schema/spec to fix type inference issues with standard schema. (#1029)
Improved file handling so that the future useForm hook does not crash when submitting an empty file input. (#1027)

Full Changelog: edmundhung/conform@v1.9.1...v1.10.0

`v1.9.1`

Compare Source

What's Changed

This release restored form and field metadata that were present in v1 but accidentally omitted from the future useForm hook (#1020). This includes:

Adding key, errorId and descriptionId properties to form metadata
Adding valid property to both form and field metadata with invalid deprecated and to be removed in 1.10.0
Adding formId property to field metadata
Adding fieldErrors to field metadata (renamed from v1's allErrors) with improvements:
- Keys use relative paths scoped to the parent field instead of full field names
- Excludes the current field's own errors (only includes child field errors)

Full Changelog: edmundhung/conform@v1.9.0...v1.9.1

`v1.9.0`

Compare Source

What's changed

This version introduces a set of new experimental APIs under the future export.

Learn more about these APIs in the announcement post.

New React APIs (`@conform-to/react/future`)

useForm: The future main hook for form state, validation, and submission
useFormMetadata: Access form-level metadata (errors, validation state)
useField: Access individual field metadata with auto-generated IDs
useIntent: Create intent dispatchers for programmatic form actions
parseSubmission: Parses FormData/URLSearchParams into structured objects with nested data support. This is already used internally by the isDirty helper.
report: Creates submission results with validation errors and security features

Enhanced Zod Integration (`@conform-to/zod/v3/future` or `@conform-to/zod/v4/future`):

coerceFormValue: Enhances the schema to strip empty value and coerce form value
formatResult: Transforms Zod validation results into Conform's error format, supporting value extraction and custom error formatting
memoize: Caches most recent result to prevent redundant API calls during async validation

Additional Changes

Improved ZodPipe resolution in getZodConstraint() with zod v4. Thanks @taku-hatano!

No changes were made to the existing future hook in this release. Everything should continue to work as expected.

Full Changelog: edmundhung/conform@v1.8.2...v1.9.0

`v1.8.2`

Compare Source

What's Changed

fix: ensure input not managed by conform are untouched during form reset by @edmundhung in #980
fix: updated @conform-to/zod's zod version requirements to ^3.21.0 || ^4.0.0 by @chimame in #985
docs: added ja translation in ui-libraries.md by @WataruNishimura in #986
chore: update vitest config to prevent unnecessary tests from being executed by @chimame in #984

New Contributors

@WataruNishimura made their first contribution in #986

Full Changelog: edmundhung/conform@v1.8.1...v1.8.2

`v1.8.1`

Compare Source

What's Changed

fix(future-export): useControl now properly resets file inputs when receiving an empty array (#976)

Full Changelog: edmundhung/conform@v1.8.0...v1.8.1

`v1.8.0`

Compare Source

What's changed

This version introduced two new experimental APIs under the future export.

useFormData: A low-level React hook that lets you derive a value from the current FormData of a form and re-render only when that value changes.
```
const fullName = useFormData(
  formRef,
  (formData) => formData?.get('role') === 'admin',
);
```
isDirty: A utility function for checking whether the current form values differ from the default values.
```
const dirty = isDirty(formData, { defaultValue });
```

These APIs are designed to decouple form state from the core logic and provide more flexibility for reacting to form changes without relying on internal context. They are also part of the groundwork for a simpler useForm model in future versions.

Learn more in the announcement post.

No changes were made to the future useControl hook in this release. Everything should continue to work as expected.

Full Changelog: edmundhung/conform@v1.7.2...v1.8.0

`v1.7.2`

Compare Source

What's Changed

Fixed zod 4 nested discriminated unions support by @chimame (#969)

Full Changelog: edmundhung/conform@v1.7.1...v1.7.2

`v1.7.1`

Compare Source

What's Changed

Stop setting aria-invalid attriabute when using getFormProps or getFieldsetProps by @evaogbe (#963)
Ensure the useControl future export works when File or FileList is undefined by @edmundhung (#966)

New Contributors

@evaogbe made their first contribution in #963

Full Changelog: edmundhung/conform@v1.7.0...v1.7.1

`v1.7.0`

What's changed

The `future` export and `useControl` hook

We’ve introduced the first API under the new future export: useControl.

The future export is a new entry point for previewing upcoming features that may evolve before being stabilized in a future major version. If you haven’t seen it yet, check out our announcement for context.

The first experimental API is useControl — a new hook that helps you integrate custom inputs with Conform. Compared to useInputControl, it offers a more flexible setup with better support for multi-select, file inputs, and checkbox groups.

We’ve documented it in detail:

Give it a try — and let us know what you think!

New field metadata for default values

Field metadata now includes three new properties:

defaultValue (string | undefined)
defaultChecked (boolean | undefined)
defaultOptions (string[] | undefined)

const { fields } = useForm({
  defaultValue: {
    username: 'edmundhung',
    tags: ['react', 'forms'],
    subscribe: true,
  }
});

fields.username.defaultValue; // 'edmundhung'
fields.tags.defaultOptions;   // ['react', 'forms']
fields.subscribe.defaultChecked; // true

These values are automatically derived from your form’s defaultValue, making it easier to connect each field with useControl and wire up individual input elements.

Full Changelog: edmundhung/conform@v1.6.0...v1.7.0

digdir/designsystemet (@digdir/designsystemet-css)

`v1.7.3`

Compare Source

@digdir/designsystemet@1.7.3

@digdir/designsystemet-css@1.7.3

@digdir/designsystemet-react@1.7.3

Patch Changes

Update npm non-major dependencies (#4233)
Tooltip: Check if trim() is available (#4239)
- Fixes if Tooltip has <svg> as a child

@digdir/designsystemet-theme@1.7.3

`v1.7.2`

Compare Source

@digdir/designsystemet@1.7.2

Patch Changes

Add option to override linkVisited color in config: (#4182)

"theme": {
  "overrides": {
    "linkVisited": {
      "light": "#ff1234",
      "dark": "#&#8203;1234ff"
    }
  }
}

New command that lets you generate a config file from your design tokens: (#4207)
npx @digdir/designsystemet generate-config-from-tokens --dir <path to design tokens>
- This command does not include any overrides you may have done.
Update npm non-major dependencies (#4193)
Update npm non-major dependencies (#4214)
For your config file, you can now get the schema file from designsystemet.no (#4195)
```
"$schema": "https://designsystemet.no/schemas/cli/[VERSION].json"
```

@digdir/designsystemet-css@1.7.2

Patch Changes

input: Remove hover effect when <label> is hovered (#4196)
tag: Add new variant, [data-variant="outline"]. (#4173)
- To use the old variant, either don't set data-variant, or set it to default.
Update npm non-major dependencies (#4214)
card: Add support for <picture> (#4137)
search: Don't set position: relative, but use isolation: isolate on .ds-search (#4212)
- This removes z-index on button[type="reset"]
tag: New css variables to go with [data-variant="outline"]: (#4173)
- --dsc-tag-border-width
- --dsc-tag-border-color
- --dsc-tag-border-style

@digdir/designsystemet-react@1.7.2

Patch Changes

Update @u-elements/combobox to v1.0.4 (#4226)
Dialog: If the browser supports closedBy on <dialog>, we let the browser handle it (#4210)
Tooltip: Tooltip is now automatically aria-describedby or aria-labelledby based on the content of the trigger component. (#4202)
- This can be overridden with the new type-prop that accepts decribedby or labelledby.
Update npm non-major dependencies (#4193)
Update npm non-major dependencies (#4214)
Tag: Add new prop variant (#4173)
- Accepts default|outline. default is the default value.

@digdir/designsystemet-theme@1.7.2

Patch Changes

Update npm non-major dependencies (#4214)

`v1.7.1`

Compare Source

@digdir/designsystemet@1.7.1

@digdir/designsystemet-css@1.7.1

@digdir/designsystemet-react@1.7.1

Patch Changes

Suggestion: Fix onSelectedChange not always calling the latest callback (#4176)

@digdir/designsystemet-theme@1.7.1

`v1.7.0`

Compare Source

@digdir/designsystemet@1.7.0

Minor Changes

Restructure design tokens: (#4105)
- Removes primitives/modes/color-scheme/[dark/light]/global.json
- Removes global colors (red, green, blue, orange, purple)
- Moved severity colors directly to your theme file
- "link.color.visited" now references "$value": "color.link.visited" from your theme file
Make sure to regenerate your design tokens: npx @digdir/designsystemet tokens create <options> --clean

Patch Changes

Update npm non-major dependencies (#4147)
Export zod schema and type for config file: (#4170)
- configSchema
- type ConfigSchema

Add option override severity colors from config. (#4105)
You can override the base-hexcode, as well as individual steps:

"theme": {
  "overrides": {
    "colors": {
      "danger": {
        "background-default": {
          "light": "#&#8203;0000ff",
          "dark": "#&#8203;0000ff"
        }
      }
    },
    "severity": {
      "danger": "#ff00ff"
    }
  }
}

Update npm non-major dependencies (#4167)
Update dependency ramda to ^0.32.0 (#4146)

@digdir/designsystemet-css@1.7.0

Patch Changes

Field: Set display: block on <label> (#4134)
ToggleGroup: ensure ToggleGroup has same height as Button, and that individual buttons within the group never wrap their text (#4139)
ToggleGroup: use correct border-color (--ds-color-text-default) to match text/icon color on selected button in secondary variant (#4139)
Label: Use line-height: var(--ds-body-md-line-height); (#4134)
Field: data-field="description" no longer gets margin-top (#4134)
chip: Remove hover effect on .ds-input (#4165)

@digdir/designsystemet-react@1.7.0

Patch Changes

Update npm non-major dependencies (#4147)
Suggestion, Tooltip, Popover: Positioning of floating elements rounded to nearest pixel (#4142)
Update npm non-major dependencies (#4167)
Dialog: Removed the autofocus attribute from built in closeButton, which prevented setting autofocus on other elements in Dialog. (#4159)
Field.Counter: Adjustments to how it works internally. (#4140)
Now, none of the validation messages underneath are aria-described on the input/textarea. This is done by an aria-live region only for screenreaders.

A new hint prop has been added, to announce how many characters are allowed when entering the input/textarea. Default value is 'Maks %d tegn tillatt.'.

@digdir/designsystemet-theme@1.7.0

Patch Changes

Update design-tokens to reflect changes made in @digdir/designsystemet. See changelog for changes (#4105)

`v1.6.1`

Compare Source

@digdir/designsystemet@1.6.1

Patch Changes

Update npm non-major dependencies (#4129)
Update npm non-major dependencies (#4110)

@digdir/designsystemet-css@1.6.1

Patch Changes

pagination: If direct child of li has aria-hidden="true" it sets visibility: hidden; (#4123)
input: Add outline on :hover when not :focus-visible, :disabled or [readonly]. This adds a few new CSS variables: (#4125)
- --dsc-input-outline-color--hover
- --dsc-input-outline-color--toggle--hover
- --dsc-input-outline-width--hover
- --dsc-input-outline-style--hover
Chip, Tag: Ensure font size scales correctly with the current size mode by using the token --ds-body-sm-font-size. Note: there might be a small visual change for Chip used without explicit data-size, since it used to have font-size: 90%. (#4098)

@digdir/designsystemet-react@1.6.1

Patch Changes

Button: For icon-buttons, dont render children if loading is true (#4023)
Update npm non-major dependencies (#4129)
Suggestion: Updated u-combobox to 1.0.2 to fix a bug where input would not clear in conrolled mode (#4119)
Update npm non-major dependencies (#4110)
usePagination: Hide prev/next buttons with aria-hidden="true" and visibility: hidden; instead of disabling (#4123)
Textfield: Move counter error message before error (#4104)

@digdir/designsystemet-theme@1.6.1

`v1.6.0`

Compare Source

@digdir/designsystemet@1.6.0

Patch Changes

Add possiblity to override colors in config: (#4073)

"theme": {
  "overrides": {
    "colors": {
      "dominant": {
        "background-default": {
          "light": "#ff0000",
          "dark": "#&#8203;000fff"
        },
        "background-tinted": {
          "light": "#f0ff00",
          "dark": "#ff00ff"
        }
      }
    }
  }
}

Font size variables are now rounded to the nearest pixel. This affects size modes "sm" and "lg", which had subpixel values after v1.5.0. (#4070)
Update npm non-major dependencies (#4093)
Update supported engines. Now supports node >=20 <25 (#3925)

@digdir/designsystemet-css@1.6.0

Minor Changes

toggle-group: Added new secondary design available with data-variant="secondary" (or variant="secondary" in react) (#4092)
toggle-group: Changed border-radius to --ds-border-radius-default, border-color to --ds-color-border-default and color to --ds-color-text-default. (#4092)

Patch Changes

link: Change :focus-visible styling to use border, not background (#4095)
- Removes --dsc-link-background--focus
- Removes --dsc-link-color--focus
link: Add --dsc-link-border-radius, default is var(--ds-border-radius-md) (#4095)
Dropdown: Dropdown.Heading (h2-h6) - changed color to text-default and font-weight to 500 (#4076)

@digdir/designsystemet-react@1.6.0

Minor Changes

ToggleGroup: Added new prop variant to enable new secondary design option (#4092)

Patch Changes

Spinner: Allow using aria-hidden when aria-label is set, which can be useful to hide or show the element from the accessibility tree based on some UI state like whether a visual label is also rendered. ([#4077](https://redirect.github.com/digdir/designsysteme

Configuration

📅 Schedule: Branch creation - "before 07:00 on Thursday" in timezone Europe/Oslo, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

renovate bot force-pushed the renovate/npm-minor-patch branch 6 times, most recently from bd25740 to 91f9403 Compare September 18, 2025 12:33

renovate bot force-pushed the renovate/npm-minor-patch branch 6 times, most recently from f091f5f to 6913b7c Compare September 25, 2025 12:25

renovate bot force-pushed the renovate/npm-minor-patch branch 7 times, most recently from 1763bc8 to 96405c7 Compare October 3, 2025 12:11

renovate bot force-pushed the renovate/npm-minor-patch branch 5 times, most recently from 085088c to 2fe84d6 Compare October 10, 2025 20:03

renovate bot force-pushed the renovate/npm-minor-patch branch 5 times, most recently from d0d6741 to 3469f8d Compare October 18, 2025 12:14

renovate bot force-pushed the renovate/npm-minor-patch branch from 3469f8d to 5ffe5bd Compare October 19, 2025 08:12

renovate bot force-pushed the renovate/npm-minor-patch branch 5 times, most recently from 91f0853 to fcc196d Compare October 26, 2025 03:53

renovate bot force-pushed the renovate/npm-minor-patch branch 2 times, most recently from 7ca4995 to e1030cc Compare November 2, 2025 11:46

renovate bot force-pushed the renovate/npm-minor-patch branch from e1030cc to 720d5ac Compare November 8, 2025 15:58

renovate bot force-pushed the renovate/npm-minor-patch branch 4 times, most recently from 6f0c8e3 to 4d322b2 Compare November 22, 2025 16:12

Update npm non-major dependencies

a18b672

renovate bot force-pushed the renovate/npm-minor-patch branch from 4d322b2 to a18b672 Compare November 24, 2025 19:59

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Update npm non-major dependencies #117

Update npm non-major dependencies #117

Uh oh!

renovate bot commented Sep 11, 2025 •

edited

Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Update npm non-major dependencies #117

Are you sure you want to change the base?

Update npm non-major dependencies #117

Uh oh!

Conversation

renovate bot commented Sep 11, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Notes

What's Changed

What's Changed

What's Changed

Breaking changes on future exports

What's Changed

What's Changed

What's changed

Metadata Customization

Improvements

What's Changed

Breaking change (Future APIs)

Improvements

What's Changed

New Contributors

What's changed

Breaking change

New in @conform-to/react/future

New in @conform-to/valibot/future

Fixes and improvements

What's Changed

What's changed

New React APIs (@conform-to/react/future)

Enhanced Zod Integration (@conform-to/zod/v3/future or @conform-to/zod/v4/future):

Additional Changes

What's Changed

New Contributors

What's Changed

What's changed

What's Changed

What's Changed

New Contributors

What's changed

The future export and useControl hook

New field metadata for default values

@​digdir/designsystemet@​1.7.3

@​digdir/designsystemet-css@​1.7.3

@​digdir/designsystemet-react@​1.7.3

Patch Changes

@​digdir/designsystemet-theme@​1.7.3

@​digdir/designsystemet@​1.7.2

Patch Changes

@​digdir/designsystemet-css@​1.7.2

Patch Changes

@​digdir/designsystemet-react@​1.7.2

Patch Changes

@​digdir/designsystemet-theme@​1.7.2

Patch Changes

@​digdir/designsystemet@​1.7.1

@​digdir/designsystemet-css@​1.7.1

@​digdir/designsystemet-react@​1.7.1

Patch Changes

@​digdir/designsystemet-theme@​1.7.1

@​digdir/designsystemet@​1.7.0

Minor Changes

Patch Changes

@​digdir/designsystemet-css@​1.7.0

Patch Changes

@​digdir/designsystemet-react@​1.7.0

Patch Changes

@​digdir/designsystemet-theme@​1.7.0

Patch Changes

@​digdir/designsystemet@​1.6.1

Patch Changes

@​digdir/designsystemet-css@​1.6.1

Patch Changes

@​digdir/designsystemet-react@​1.6.1

Patch Changes

@​digdir/designsystemet-theme@​1.6.1

@​digdir/designsystemet@​1.6.0

Patch Changes

@​digdir/designsystemet-css@​1.6.0

Minor Changes

renovate bot commented Sep 11, 2025 •

edited

Loading

Breaking changes on `future` exports

New in `@conform-to/react/future`

New in `@conform-to/valibot/future`

New React APIs (`@conform-to/react/future`)

Enhanced Zod Integration (`@conform-to/zod/v3/future` or `@conform-to/zod/v4/future`):

The `future` export and `useControl` hook

@digdir/designsystemet@1.7.3

@digdir/designsystemet-css@1.7.3

@digdir/designsystemet-react@1.7.3

@digdir/designsystemet-theme@1.7.3

@digdir/designsystemet@1.7.2

@digdir/designsystemet-css@1.7.2

@digdir/designsystemet-react@1.7.2

@digdir/designsystemet-theme@1.7.2

@digdir/designsystemet@1.7.1

@digdir/designsystemet-css@1.7.1

@digdir/designsystemet-react@1.7.1

@digdir/designsystemet-theme@1.7.1

@digdir/designsystemet@1.7.0

@digdir/designsystemet-css@1.7.0

@digdir/designsystemet-react@1.7.0

@digdir/designsystemet-theme@1.7.0

@digdir/designsystemet@1.6.1

@digdir/designsystemet-css@1.6.1

@digdir/designsystemet-react@1.6.1

@digdir/designsystemet-theme@1.6.1

@digdir/designsystemet@1.6.0

@digdir/designsystemet-css@1.6.0

@digdir/designsystemet-react@1.6.0