vv
4.8/516

vee-validate

npm i vee-validate

282 Versions

4.6.10

latest
2 days ago
🐛 Bug Fixes
  • Fixed using File constructor while in SSR (56663aa2e50d7aa285ca1cb22887c8e8b3f7fd3c)
i18n 🌍
  • Updated SK and CS language files to include missing rules thanks to @Liwoj #3936 #3937

4.6.9

12 days ago
🐛 Bug Fix
  • Fixed an issue where resetForm would leave behind null or undefined in array fields after reset #3934 (1c016d93b367229644dca643931ef63bc6e433dc)

4.6.8

13 days ago
🐛 Bug Fixes
  • Run validation if we skip checkbox value setting if event trigger should validate #3927 (#3930)
  • Fix File value instance equality checks #3911 (#3932)
  • Fix nested value change not triggering validation when validateOnValueUpdate is enabled #3926 (#3929)
👕 TypeScript
  • Exposed RuleExpression type #3913 (cdaf22df04b42a68f55133ad3854aae9a7ad6953)

4.6.7

1 month ago
👕 TypeScript

Allow generics types to be passed to GenericValidatorFunction which previously caused errors with simple snippets like this:

function validator(value: string) {
  // ...
}

const { value } = useField('field', validator);
🐛 Bug Fixes
  • Fixed an issue with async function validators not respecting the last run error messages #3906 (#3908)

4.6.6

1 month ago
🐛 Bug Fixes
  • Fixed emitted value when there are no model modifiers defined #3895 (#3896)

4.6.5

2 months ago
🐛 Bug Fixes
  • Fixed an issue where checkboxes bound to an object could fail unchecking #3883 (#3885)
  • Fixed an issue with field's meta.dirty not being set correctly after calling resetField with a new value #3891 (#3892)

4.6.4

2 months ago
🐛 Bug Fixes
  • Fixed an issue where useFieldModel did not trigger validation for nested paths (fbe273c6f2c5d30a1996777561eda2268d8a02e0)

4.6.3

2 months ago
🐛 Bug Fixes
  • fix form's meta.dirty not calculated correctly when using FieldArray API #3874 (#3875)

4.6.2

2 months ago
👕 TypeScript
  • Expose FieldOptions and FormOptions interfaces #3843 (7437612ab554f8f65b445f7b065725b570a9a14a)
🐛 Bug Fixes
  • Avoid toggling field array checkboxes values when an item is removed #3844 (fffad4bea68cc949d0bce440b5daf43901aaca7f)

4.6.1

3 months ago
🐛 Bug Fixes
  • Pass onInvalidSubmit prop to submitForm #3841 (b6cf543b600246942fc7f6802a0cc6ea1038603a)

4.6.0

3 months ago

This release has been in the making for a while and I'm really glad it is finally released with a lot of requested improvements and new features.

🆕 New Features v-model with FieldArray API

You can now use v-model directive with any kind of input to mutate the field array value directly without having to use <Field /> or useField.

<Form>
  <FieldArray name="users" v-slot="{ fields }">
    <div v-for="(field, idx) in fields" :key="field.key">
      <input v-model="fields[idx].value" />
    </div>
  </FieldArray>
  
  <button>Submit</button>
</Form>
Keep values after fields are unmounted

By default, vee-validate destroys the form values automatically whenever a field is unmounted. This made creating tabbed forms or multi-step forms a little bit harder to achieve since you needed to implement a mechanism to track the values independently from vee-validate.

Now there is a new (config available) (e6e1c1d) that allows you to control this behavior on the form and field levels.

In the component API, you can pass keepValue or keepValues to <Field /> and <Form /> components respectively.

<!-- Now all field will keep their values when unmounted unless specified otherwise -->
<Form keep-values>
  <template v-if="showFields">
    <Field name="field" as="input" rules="required" />
    <!-- This field opts out and its value will be destroyed -->
    <Field name="[non-nested.field]" :keep-value="false" />
    <Field name="drink" as="input" type="checkbox" value="Tea" rules="required" /> Tea
  </template>

  <button>Submit</button>
</Form>

You can also pass keepValueOnUnmount and keepValuesOnUnmount to useField() and useForm() respectively:

useForm({
 // default is false
  keepValuesOnUnmount: true
});

useField('field', undefined, {
  // default is whatever the form is configured to, if no form then `false`
  keepValueOnUnmount: true
});

Note Keep in mind that the field config takes priority over the form config if specified. Otherwise, all fields will follow the form's config.

useFieldModel API

A new useFieldModel function was added] to useForm which introduces a new way to use useForm without having to call useField.

The reason for this is useField is meant to create input components, not model bindings. The useFieldModel allows you to create bindable refs that you can use directly with v-model on your components or any 3rd party components. This makes it significantly easier to integrate with 3rd party libraries.

<template>
  <input name="email" v-model="email" />
  <span>{{ errors.email }}</span>

  <input name="password" v-model="password" type="password" />
  <span>{{ errors.password }}</span>
</template>

<script setup>
import { useForm } from 'vee-validate';
import MyTextInput from '@/components/MyTextInput.vue';

// Define a validation schema
const simpleSchema = {
  email(value) {
    // validate email value and return messages...
  },
  name(value) {
    // validate name value and return messages...
  },
};

// Create a form context with the validation schema
const { errors, useFieldModel } = useForm({
  validationSchema: simpleSchema,
});

const email = useFieldModel('email');
const password = useFieldModel('password');

// or multiple models at once
const [email, password] = useFieldModel(['email', 'password']);
</script>

This is much less verbose than useField and is optimized to be just a validatable model. However you will no longer have access to the advanced state and capabilities of useField like meta and validation triggers. So you will need to implement your own logic for when to show errors as they will be generated immediately whenever the value changes.

Automatic v-model events with useField

Quite often you will setup your component to support v-model directive by adding a modelValue prop and emitting a update:modelValue event whenever the value changes.

If you use useField in your input component you don't have to manage that yourself, it is automatically done for you. Whenever the useField value changes it will emit the update:modelValue event and whenever the modelValue prop changes the useField value will be synced and validated automatically.

The only requirement is you need to define your model prop on your component explicitly.

<script setup>
import { useField } from 'vee-validate';

defineProps({
  // Must be defined
  modelValue: {
    type: String,
    default: '',
  },
});

const { value } = useField('field', undefined);
</script>

You can change the default model prop name by passing modelPropName option to useField:

<script setup>
import { useField } from 'vee-validate';

defineProps({
  // Must be defined
  custom: {
    type: String,
    default: '',
  },
});

// component will now emit `update:custom` and sync `custom` prop value with the `value` returned from `useField`.
const { value } = useField('field', undefined, {
  modelPropName: 'custom',
});
</script>

You can also disable this behavior completely and manage those events yourself by passing syncVModel option to useField:

<script setup>
import { useField } from 'vee-validate';

// Now it won't emit anything and won't sync anything
const { value } = useField('field', undefined, {
  syncVModel: false,
});
</script>
Other minor new features
  • Added move() to FieldArray (a52f133)
  • If you are using a native <input type="file"> element its value will now respect the multiple attribute, if it is present and set to true then it will be an array of files. Otherwise, it will be a single file. This could be a breaking change for some.
👕 TypeScript Changes
  • Expose ValidationOptions type #3825 (9854865)
  • Exposed component APIs to their TS defs with refs #3292 (ae59d0f)
  • Remove yup type dependency (#3704) (e772f9a). This sadly loses the ability to infer the types from a yup schema, however it caused more errors than it is worth and introduced an installation dependency on yup even if it is not used.
🐛 Bug Fixes
  • Use multiple batch queues for both validation modes #3783 (6156603)
  • Compare form's meta.dirty based on original values than staged initials #3782 (f3ffd3c)
  • Avoid value binding for file type inputs #3760 (3c76bb2)
  • Added existing undefined path fallback for optional arrays #3801 (fd0500c)
  • Added argument order for digits rule inja.json#3780 (9385457)

4.5.11

6 months ago
🐛 Bug Fixes
  • Ignored validation of fields during unmounting #3748 (3d49faa4101902c2e77aee0a2d43cd29b69f7b4e)
🆕 New Features

useField now allows the usage of array of functions instead of a single function to perform validation (https://github.com/logaretm/vee-validate/issues/3725) #3726 thanks to @gbaquedano

const {
  value: value,
  errors: errors,
} = useField(
  'field',
  [
    val => (val ? true : REQUIRED_MESSAGE),
    val => ((val as string)?.length >= 3 ? true : MIN_MESSAGE)
  ],
  { bails: false }
);

4.5.10

7 months ago
🐛 Bug Fixes
  • Fixed an issue with da.json locale which caused the JSON file to not parse correctly (94853105e0ca4f425a2c6b5bb7cea2233ec7480d)

4.5.9

7 months ago
🐛 Bug Fixes
  • Set meta.validated for fields validated by the form API's validate (ad9fa9d853a8cabb26cdde04c20c07d4f2673aa4)
🌏 i18n
  • Updated locale for ko, ja, zh-CN, zh-TW (d5fc7325a943bd6e42d19fa0b6057648d689be80)

4.5.8

next
8 months ago
🐛 Bug Fixes
  • Fixed a general issue when a field changes its name and has errors at the old name path #3664 (f736e62b1bb82f940d14d74a6d505c913c1c3dde)
  • Fixed an issue where FieldArray.swap function wasn't working when either indices had falsy values (40afbd9cc3fb3de71de3f6ebb0a1b2774d9018ff)

4.5.7

10 months ago
🐛 Bug Fixes
  • Always ensure update:modelValue listener existing on field binding object #3583 (6a53e80525a9c38ce8851407b832bc8409c3f334)
🌏 i18n
  • Added Uzbek locale thanks to @akahon (#3601)

4.5.6

10 months ago
🐛 Bug Fixes
  • Use watchEffect to calculate FormContext.meta instead of computed #3580 (e8729dc72d2a027a666515360c9537a62a8d46ad)

As a result of this, there should be a performance improvement depending on the size of your forms

👕 TypeScript
  • Corrected the typings for resetField #3568 (4e9460e3a4f51f4a78ddcdf17f7c3073f899404f)
🌏 i18n
  • Added missing Estonian locale messages and fixes by (#3584) @Tarinu

3.4.14

1 year ago
ğŸŒŽ i18n

4.5.5

1 year ago
🐛 Bug Fixes
  • Fixed an issue where singular checkboxes would be toggled when the form is reset #3551 (cad12ba7502af7268029930a9176d8e160efeef6)

4.5.4

1 year ago
👕 TypeScript
  • Published various internal types that are considered stable #3548 (88ed4e7efde0b55d7a5aca65c92343f5fca05fa8)

4.5.3

1 year ago
👕 TypeScript
  • Added scoped slot types for Field, Form, FieldArray and ErrorMessage components #3534 (#3537)

4.5.2

1 year ago
✨ Enhancements
  • Use the full mode of lukeed/klona which is used to clone values internally to support Luxon data structures #3508 (048c9c03d38ffd871ee4b3504daf1c83d42e9516)

4.5.1

1 year ago
🐛 Bug Fixes
  • Fixed field name not rendering in messages correctly in default error messages (#3506) thanks to @cexbrayat

4.5.0

1 year ago
🆕 New Features Field Arrays

A long-requested feature is a proper way to handle field arrays. With this release you get two ways you can manage your array fields:

  • useFieldArray a composition API version. Read more in docs
  • <FieldArray /> a component API version. Read more in docs.

Both have the same API, and they make managing those fields much easier.

Invalid Submission Handler

Another common request is the ability to handle invalid submissions, for example, you may want to scroll to the first invalid element.

This is now possible with both <Form /> component and useForm composition function. Check the links for their documentation:

Devtools Plugin

vee-validate now ships with its VueDevtools plugin, this will be an invaluable tool to help you debug your forms and their validation state.

This is the initial release for the plugin, so please report any bugs and suggest any improvements you can think of. 🙏

Check the guide page.

💨 Performance Enhancements

A partial re-write of vee-validate v4 fixed a long-standing performance issue that was reported here #3399

💀 Breaking Changes

handleInput is removed from useField after being deprecated since 4.3, you can use handleChange instead of handleInput as follows:

const { handleChange } = useField('email', {
  validateOnValueUpdate: false
});

handleChange('value'); // updates the value and validates
handleChange('value', false); // updates the value without validation

// replace deprecated handleInput with custom one
const handleInput = (val) => handleChange(val, false);

Note that handleInput prop still exists in <Field /> scope slot. This is only for useField.

Note: This release was a 2-month work in progress, so there aren't any bug fixes as 4.4.x was already being worked on in parallel to this release, so both 4.4.x and 4.5.0 contain the same bug fixes which won't be mentioned here in the release notes. Check the previous releases for more information.


3.4.13

1 year ago
✨ Enhancements

The double rule now accepts integers (#3481) thanks to @MauriceChocoSwiss


4.4.11

1 year ago
🐛 Bug Fixes
  • Fixed an issue where computed rules triggered validation before the field was explicitly validated (via event trigger or calling validate).

4.5.0-alpha.6

edge
1 year ago

4.4.10

1 year ago
🐛 Bug Fixes
  • Fixed resetField and resetForm setting the valid flag to true, it should reflect the current validity state of the form as it always should regardless of errors being displayed or not, this can be breaking for some but it was a bug. #3463 (a61f7ab532d6d2fd9f237145f91bbcc9043431f6)
  • Fixed a Vue crash when the provided v-model value is undefined #3467 #3468 (2c4a7ffb84811ae86a1698e6e15f41dc32f8fb8d)
  • Fixed native Select input not setting the bound value of options #3440 (b1446152d6f6cd4843ab206d667a7d744c2a14fc)
👕 TypeScript

Corrected the type for handleReset function (#3451) thanks to @iamandrewluca


3.4.12

1 year ago

4.5.0-alpha.5

1 year ago

4.5.0-alpha.4

1 year ago

4.4.9

1 year ago
🐛 Bug Fixes
  • Fixes an issue where initial values were using the same reference as the current values #3428 #3434 (6470a1fa7e5c8f04498d627a3759d445b0587793)

4.4.8

1 year ago
🐛 Bug Fixes
  • Fixed checkboxes emitting the absent value symbol to bound models when using v-model and not specifying an uncheckedValue #3422 #3422 (3824103)

4.5.0-alpha.3

1 year ago

4.4.7

1 year ago
🐛 Bug Fixes
  • Fixed extra validation being triggered with Vue 3.2.0-beta.x at the end of a resetField call #3407 (86f594f4a7cee5ed5f581419bdbd985fc53f8358)
👕 TypeScript
  • Exported the FieldContext type #3398 (a6e4c0ac580d4145c72118ac535bfa082c771068)
⚙️ Misc
  • Exported FormContextKey and FormFieldKey injection keys to make mocking in unit tests easier (6034e66836e0566e17f36744da19088aca33fbad)

3.4.11

1 year ago
🐛 Bug Fixes
  • Fixed an issue where Hebrew characters were not recognized by the alpha_xx rules (#3397) thanks to @MHGuitarte

4.5.0-alpha.2

next-edge
1 year ago

4.4.6

1 year ago
🐛 Bug Fixes
  • fix: clean error message for singular fields after unmounting #3384 https://github.com/formvuelate/formvuelate/issues/210 (#3385)
  • fix: quit unsetting path if its already unset, you may have encountered this if you use vue-router (64ba5f9ad23603fbcbfdf4ce17866dc657c6846d)

4.5.0-alpha.1

1 year ago

3.4.10

1 year ago
🐛 Bug Fixes
  • Fixed Japanese locale validation in alpha validators #3357 (#3356) thanks to @nachogarcia

4.4.5

1 year ago
🐛 Bug Fixes
  • Fixed null initial values not being respected #3352 (1e9cfd16591fab9cedf39dc9210151ab5b4be4c6)

3.4.9

1 year ago
🐛 Bug Fixes
  • Fixed required flag not re-evaulating its value #2843 (#3318) thanks to @Andrevwv

4.4.4

1 year ago
🐛 Bug Fixes
  • field with pre-register schema errors should be validated on register #3342 (61c73597b2e69c094e75c02476d825c5236710b5)

4.5.0-alpha.0

1 year ago

4.4.3

1 year ago
🐛 Bug Fixes
  • Fixed bails option being ignored in <Field /> component when using form schema with global rules #3332 (6679387)

3.4.8

1 year ago
🔧 Compatability
  • fixed IE 9 compatibility issue introduced in fd5bacb2519eb862727a7f7aae2df87bf93531fa #3326 (4545fb9633c639e84d07023ba4ed4bda5dda3a7b)

4.4.2

1 year ago
🐛 Bug Fixes
  • Clean up form values fields that exchange their name with another field #3325 (fe51c126ae6258ac0888ee47d9d01a27b889a5c1)

3.4.7

1 year ago
🐛 Bug Fixes
  • fixed recursive objects comparison for the changed flag triggering maximum callstack errors #3320 (fd5bacb2519eb862727a7f7aae2df87bf93531fa)

4.4.1

1 year ago
🐛 Bug Fixes
  • Bring back errors object on the form validation result that was removed by mistake #3317

4.4.0

1 year ago

This release commits the changes from 4.4.0-alpha releases

🐛 Bug Fixes
  • Fixed the URL rule not exported #3310 (abeccfbc2eb5e009e4c562e8b1702427ed96041e)
  • Fixed an issue with Field component not emitting onUpdate:modelValue when bound to undefined #3312 (5e72852e80b971121d10422cf84085b07bb2d8fb)

3.4.6

1 year ago
🐛 Bug Fixes
  • Implemented recursive checking for changed flag for nested arrays and objects #3300 (#3313) thanks to @AdelineCaro

4.4.0-alpha.2

1 year ago
🐛 Bug Fixes

Fixed errors being cleared whenever any input was being validated


4.4.0-alpha.1

1 year ago
🐛 Bug Fixes

Fixed an issue where the dist files code didn't preserve the result of a conditional promise


4.4.0-alpha.0

1 year ago
⚠️ Important Changes Schema Behavior Change

Previously vee-validate treated schemas loosly, meaning if there are validations for fields that were not rendered with Field or useField it will ignore the errors for those fields. This was found unexpected from the few reports I got.

In 4.4.x and onwards, vee-validate will treat schemas as the source of truth and will no longer ignore any errors generated by the validation schema.

There are a few side effects to this change:

  • You can now set custom form errors with setErrors or setFieldError for non-existing fields and it will affect the form's validity.
  • You can set custom values with setValues or setFieldValue for non-existing fields.
  • Defining a schema for multi-step forms will require partitioning them into separate ones per step

The first two side effects should not be breaking in your apps unless you have typos when setting fields values/errors

The official examples for multi-step forms will be updated in the docs to reflect these changes

Depreactions
  • handleInput is now marked for deprecation, you may still use it but it will be removed in the next minor release, instead use handleChange(event, shouldValidate = false) as an alternative.
  • valueProp was renamed to checkedValue to better reflect its usage, you may still use the old prop name but it will be removed in the next minor release.

4.3.6

1 year ago

Compatibility: This patch is to adjust to some changes introduced in Vue 3.1

  • Added a new way to detect if modelValue was passed as a prop or not #3294 (#3295)

4.3.5

1 year ago
🐛 Bug Fixes
  • prioritize self injections over parent injections #3270 (07c12341d7f2e25e41a56ea0d5e38e9a374ae84b)
🌍 i18n
  • Added Welsh language translations thanks to @al3d

4.3.4

1 year ago
🐛 Bug Fixes
  • Ensure the valid flag is updated correctly regardless of the validation intent #3284 (6594ad15e4423c6a7861da188560b06f98365d9d)

4.3.3

1 year ago
🆕 New behavior
  • submitting forms rendered by <Form /> or handleSubmit or submitForm functions, all fields will be automatically "touched" (#3278)

You can find documentation for the submission full behavior here


4.3.2

1 year ago
🐛 Bug Fixes
  • Fixed an issue with the initial value being wrapped in a ref which caused some issues for individual resetField calls and dirty field-level flags #3272 (#3274)

4.3.1

1 year ago
✨ Enhancements
  • Added name to the ErrorMessage component ctor options which should make it identifiable in Vue dev tools
  • Tweaked slots rendering for custom components with Field, Form, ErrorMessage component which avoids Vue warning in some situations

4.3.0

1 year ago
🆕 New Features
  • Computed Validation Schema Support: Previously when working with yup schemas, in particular, it was hard to create a dynamic schema using just the Yup.mixed and Yup.when API, now you can create computed schema to make it easier to do so. Check the docs for more information
  • v-model.number modifier support: TheField component v-model now supports the .number modifier, thanks to @davidguilherme who worked on this
  • New global rule: The url rule is added back to the global validators, thanks to @davidguilherme who worked on this. You can find more information in the documentation

📢 The language files need your help, if you find the url locale message missing for your language, please contribute it 🙏

👕 TypeScript

Removed the SubmitEvent type which caused some tools like volar to display errors for form @submit handlers created by handleSubmit function in the composition API

🌏 I18n

Several enhancements to the ja locale, thanks to @kuanyui


4.2.4

2 years ago
🐛 Bug Fixes
  • Fixed an issue where validation would trigger on value change with useField even if validateOnValueChange is set to false (10549b77dc350cee4f198cb14e3fd12f61e12b80)

4.2.3

2 years ago
🐛 Bug Fixes
  • fix: prevent yup schema validation from accidentally setting non-interacted fields errors #3228 (534f8b28850c9f28245a748f956d1358bb7cb2e1)
👕 TypeScript
  • Exposed PublicFormContext interface (#3222) thanks to @notiv-nt
🌍 i18n
  • Fixed mistype in digits rule message for LT locale #3209 (#3215) thanks to @vaidotas

4.2.2

2 years ago
🐛 Bug Fixes
  • Fixed an issue for pending validation with fields/forms being unmounted with vue-router (ef5a7ccb269db8bbdee446e76dd60ebe8704b57e)
🌏 i18n
  • Added Uyghur locale thanks to @uqkun09 (#3201 )

4.2.1

2 years ago

This release fixes some issues introduced in 4.2.1 due to the limitations mentioned in #3189

Enahanced valid flag behavior

Instead of having the valid flag starts with either true or false, it will have its own validation ecosystem where silent validations would be run when:

  • The field is mounted
  • The field value changed

This means you can now always rely on the valid flag to present the accurate form state, note that the valid flag is now completely independent from the errors array as it can be false while there are no errors. But the opposite is not true, the valid flag cannot be true while there are some errors.

Until that silent validation is run, the valid flag will be true, so it is still good idea to combine it with dirty or touched as to avoid this issue.

This change makes easier to disable various UI elements based on the validity and interactivity with the form, here are some common ones:

ExpressionDescription
validForm/Field is valid or might've not been validated yet
!validForm/Field is invalid
valid && dirtyForm/Field is valid and some values have been changed
valid && touchedForm/Field is valid and the user blurred some controls
!valid || !dirtyForm/Field is invalid or no value was changed yet (good for disabling submit buttons)

4.2.0

2 years ago

This PR introduces several updates to the meta objects in both field and form APIs, these changes are considered breaking for non-intended use-cases, so it doesn't warrant a major release.

🆕 New Changes dirty flag changes

The flag now acts as a changed flag, it will be read-only and will be set to true if the field current value is not deeply equal to its initial value.

The reason for this change is the dirty and touched flags are not that different from one another, so users end up using one or the other. Having the dirty flag reflects whether the form values have changed or not gives it more utility and is more valuable to several common tasks done by FE developers.

valid flag changes

Changes in this release has been overwritten by 4.2.1 due to bad DX

Rules and Empty Values

The global validators published under @vee-validate/rules didn't handle the empty values before, meaning they gave an incorrect behavior when used without required. The changes in this PR introduce a consistent behavior across all these rules:

  • If the value is empty, the value is valid
  • Empty values are: empty strings, empty arrays, null or undefined

That closely mirrors the behavior in v3 where validation is skipped for empty non-required fields, except now the validation passes rather than skipped. #3170

🐛 Bug Fixes
  • Fixed the checkboxes setting their initial value twice causing malformed form values #3183

4.1.20

2 years ago
🐛 Bug Fixes
  • Fixed nested errors for @vee-validate/zod not being picked up correctly (01b89e4940e997ef65dc950be3a13e0ffc18e881) #3184
  • Fixed an issue where initial values for checkboxes would cause malformed output (ab5f82103f8cfe5f5934a51057ce989ad30d0d44) #3183

4.1.19

2 years ago
🆕 New Features Added Support for Zod Schema Validation #3160 (#3171)

A new companion package @vee-validate/zod was published which allows vee-validate to perform field-level and form-level schema validation with Zod as a drop-in replacement for yup

Check the documentation here


4.1.18

2 years ago
🐛 Bug Fixes
  • Fixed an issue where fields value is set to blank after being switched with another that shares the same name due to a race condition #3166 (f5a79fe3b15f7437acf183c162e69178fd4fa7ec)

4.1.17

2 years ago

No major changes in this release, but starting from 4.1.17 both @vee-validate/rules and @vee-validate/i18n will be versioned in sync to reduce confusion as suggested here #3162

🐛 Bug Fixes
  • Added a fallback event object detection in case the handler receives a non-standard window.Event instance #3161

4.1.16

2 years ago

4.1.15

2 years ago

4.1.14

2 years ago

4.1.13

2 years ago

4.1.12

2 years ago

4.1.11

2 years ago

4.1.10

2 years ago

4.1.9

2 years ago

4.1.8

2 years ago

4.1.7

2 years ago

4.1.6

2 years ago

4.1.5

2 years ago

4.1.4

2 years ago

4.1.3

2 years ago

4.1.2

2 years ago

4.1.1

2 years ago

4.1.0

2 years ago

4.0.7

2 years ago

4.0.6

2 years ago

4.0.5

2 years ago

4.0.4

2 years ago

4.0.3

2 years ago

4.0.2

2 years ago

4.0.1

2 years ago

4.0.0

2 years ago

3.4.5

2 years ago
🐛 Bug Fixes
  • fixed double rule signature not being compatible with extend TypeScript signature #3012 (f341c1491584c51fa0a9a8ffc10fdff71255bff7)

3.4.4

2 years ago
🐛 Fixes
  • Disabled observers no longer participate in validation #2916 #2994 (#3019) thanks to @Mikilll94

4.0.0-beta.19

2 years ago

4.0.0-beta.18

2 years ago

4.0.0-beta.17

2 years ago

282 Versions

TagPublished
4.6.10latest2d ago
4.6.912d ago
4.6.813d ago
4.6.71mo ago
4.6.61mo ago
4.6.52mos ago
4.6.42mos ago
4.6.32mos ago
4.6.22mos ago
4.6.13mos ago
4.6.03mos ago
4.5.116mos ago
4.5.107mos ago
4.5.97mos ago
4.5.8next8mos ago
4.5.710mos ago
4.5.610mos ago
3.4.141yr ago
4.5.51yr ago
4.5.41yr ago
4.5.31yr ago
4.5.21yr ago
4.5.11yr ago
4.5.01yr ago
3.4.131yr ago
4.4.111yr ago
4.5.0-alpha.6edge1yr ago
4.4.101yr ago
3.4.121yr ago
4.5.0-alpha.51yr ago
4.5.0-alpha.41yr ago
4.4.91yr ago
4.4.81yr ago
4.5.0-alpha.31yr ago
4.4.71yr ago
3.4.111yr ago
4.5.0-alpha.2next-edge1yr ago
4.4.61yr ago
4.5.0-alpha.11yr ago
3.4.101yr ago
4.4.51yr ago
3.4.91yr ago
4.4.41yr ago
4.5.0-alpha.01yr ago
4.4.31yr ago
3.4.81yr ago
4.4.21yr ago
3.4.71yr ago
4.4.11yr ago
4.4.01yr ago
3.4.61yr ago
4.4.0-alpha.21yr ago
4.4.0-alpha.11yr ago
4.4.0-alpha.01yr ago
4.3.61yr ago
4.3.51yr ago
4.3.41yr ago
4.3.31yr ago
4.3.21yr ago
4.3.11yr ago
4.3.01yr ago
4.2.42yrs ago
4.2.32yrs ago
4.2.22yrs ago
4.2.12yrs ago
4.2.02yrs ago
4.1.202yrs ago
4.1.192yrs ago
4.1.182yrs ago
4.1.172yrs ago
4.1.162yrs ago
4.1.152yrs ago
4.1.142yrs ago
4.1.132yrs ago
4.1.122yrs ago
4.1.112yrs ago
4.1.102yrs ago
4.1.92yrs ago
4.1.82yrs ago
4.1.72yrs ago
4.1.62yrs ago
4.1.52yrs ago
4.1.42yrs ago
4.1.32yrs ago
4.1.22yrs ago
4.1.12yrs ago
4.1.02yrs ago
4.0.72yrs ago
4.0.62yrs ago
4.0.52yrs ago
4.0.42yrs ago
4.0.32yrs ago
4.0.22yrs ago
4.0.12yrs ago
4.0.02yrs ago
3.4.52yrs ago
3.4.42yrs ago
4.0.0-beta.192yrs ago
4.0.0-beta.182yrs ago
4.0.0-beta.172yrs ago