This repository was archived by the owner on May 6, 2025. It is now read-only.
chore(deps): update npm packages (major) #6
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^18->^22.15.11^1.4.0->^3.0.1^9.1.1->^10.1.0^0.31.4->^3.1.3Release Notes
vinejs/vine (@vinejs/vine)
v3.0.1: Fix CamelCase utilities to not work with keys containing numbersCompare Source
Bug Fixes
Full Changelog: vinejs/vine@v3.0.0...v3.0.1
v3.0.0: Breaking changes and bug fixesCompare Source
This release contains a few breaking changes along with a handful of new improvements and bug fixes.
Breaking changes
Infer type
The infer type of schema now marks
optionalfields asoptionalwithin the TypeScript types. This ensures the property can be missing altogether from the data object/inferred types vs being marked asundefinedexplicitly. For example:SUBTYPE symbol
Custom types extending the VineJS
BaseLiteralTypenow must define thesymbols.SUBTYPEproperty on the schema. This property can be used by schema transformers to get a more accurate type for the schema node. Here's how theStringSchemadefines theSUBTYPEproperty.For example:
Bug Fixes
Features
Pull Requests
New Contributors
Full Changelog: vinejs/vine@v2.1.0...v3.0.0
v2.1.0: Add "tryValidate", "toJSON" method and "in" validation ruleCompare Source
tryValidateThe
tryValidatemethod can be used to perform validation without throwing a validation error. Instead, the errors are returned as the return value of the method, which is a tuple.The
tryprefix is inspired from the Java world.inThe
invalidation rule has been added for theVineNumberschema type and can be used to ensure the value of field is part of the allowed values list.toJSONThe
validator.toJSONmethod can be used to get the validator and its refs as JSON.Commits
a70ff38)cebb8e0)39204e4)0b5e212)72912af)34e07fc)a7e18b7)62d450c)5259933)What's Changed
New Contributors
Full Changelog: vinejs/vine@v2.0.0...v2.1.0
v2.0.0: Improved error reporting for fields inside arrays and infer schema input typesCompare Source
This release contains a couple of minor breaking changes. So let's first talk about them.
Improved error reporting for fields inside arrays ( Breaking )
In the previous versions of VineJS, the error reporting for fields inside arrays could have been better.
Given the following schema and data
The errors reported up until 2.0 were
If you notice, the field name inside arrays is defined as
categories.*and not the actual index of the item inside the array. Now, you may think that I can replace the*with theindexproperty value and get a nested path to the item index within the array.Well, the replacement of
*might work in this situation. But it will not work when there are errors inside nested arrays or the field that failed the validation is a grandchild of an array. Because theindexproperty only exists when the field is an immediate child of an array.But anyway, after this release, you do not have to perform any manual substitutions. The field names are nested paths with the correct index. The following is an example of errors with
@vinejs/vine@2.Infer Schema Input value ( Breaking )
After this release, you can infer the input values a Schema type accepts. Let's consider the following example.
If you notice, the
is_adminproperty accepts aboolean | string | number. VineJS is built for parsing form inputs submitted over HTTP. Therefore, it receives all inputs asstringvalues and performs normalization before performing any sort of validation.Because of this change, the
BaseSchemaclasses accept another generic value for theInputTypes. So, if you use the BaseSchema anywhere in your apps, make sure to pass the Input type as the first generic argument.Also, please consult this commit for a better understanding of the change. vinejs/vine@df27df8
Define error messages for specific array index or a wildcard ( New feature )
Now, you will be able to define custom error messages for specific array indexes with a wildcard fallback for rest of the indexes. For example:
Commits
9dd733cdf27df83d59dad8ff246fWhat's Changed
New Contributors
Full Changelog: vinejs/vine@v1.7.0...v2.0.0
v1.8.0: Add requiredIf rulesCompare Source
Please check docs to learn how
requiredIfrules work. And check this PR to understand the difference betweenvine.unionandrequiredIfrules.Commits
893d37881beff721ac492d2a03a3ef50170200bb3963c49e2f94d27402ff0a5d6f5589ffb2a4eWhat's Changed
New Contributors
Full Changelog: vinejs/vine@v1.7.1...v1.8.0
v1.7.1: Bug fix and performance improvementsCompare Source
bcebea59dd9d856e412b23e35b834c88fa192a48c8What's Changed
Full Changelog: vinejs/vine@v1.7.0...v1.7.1
v1.7.0: Support for validating datesCompare Source
This release adds support for validating dates in VineJS. You may check the documentation here. https://vinejs.dev/docs/types/date
The
vine.dateschema type accepts a string value formatted as a date and returns an instance of the JavaScript Date object. The reason we accept a string is because the data submitted over an HTTP request will always represent date/datetime as a string.Once you have a date, you may validate it further by comparing it against a fixed value or compare it against values from other fields. You may refer the documentation to view all the available validation rules.
Commits
e85356be07cb691b5c497b39b00c02c2945223bb93c893f10628b4c7ce6c52ccf08e2a72d098d16bd6e85d2a97af98e099v1.6.0: Bundling with tsupCompare Source
627ee41v1.5.3: Use validator.js specific importsCompare Source
459f3e5v1.5.2: Export VineValidator classCompare Source
cfaeeff74ca7e09b7bc07Full Changelog: vinejs/vine@v1.5.1...v1.5.2
v1.5.1: Fix: Make schema classes Macroable to be extensibleCompare Source
2f5258c89efc20d04800ca41741841bd3d5Full Changelog: vinejs/vine@v1.5.0...v1.5.1
v1.5.0: Add API to make validation metadata type-safeCompare Source
In VineJS, you can pass runtime metadata to the validation pipeline, which you can access from the validation rules, union predicates, etc. The metadata API was not type-safe until now. However, this release allows you to define the static metadata types and a validation function to validate them at runtime.
One example is the
uniquevalidation rule. You might want the unique validation rule to check all the database rows except the one for the currently logged-in user. In that case, you will pass the currently logged-in userId to the statically compiled validation schema using metadata as follows.However, there is no way to know that
updateUserValidatorneeds the currently logged-in user id to be functional.From
@vinejs/[email protected], you can use thewithMetaDatamethod to define static types for the metadata a validator accepts. The schema will look as follows.You can pass a callback to
withMetaDatato validate the metadata at runtime if needed.Commits
09c4097a02908d4181ee4f24ebb892697c4fcad2fbFull Changelog: vinejs/vine@v1.4.1...v1.5.0
v1.4.1: Export testing factoriesCompare Source
ffe8279Full Changelog: vinejs/vine@v1.4.0...v1.4.1
antfu-collective/bumpp (bumpp)
v10.1.0Compare Source
🚀 Features
View changes on GitHub
v10.0.3Compare Source
🐞 Bug Fixes
View changes on GitHub
v10.0.2Compare Source
No significant changes
View changes on GitHub
v10.0.1Compare Source
🐞 Bug Fixes
log-symbols- by @antfu (9f4fd)View changes on GitHub
v10.0.0Compare Source
🚨 Breaking Changes
View changes on GitHub
v9.11.1Compare Source
🚀 Features
View changes on GitHub
v9.11.0Compare Source
🚀 Features
View changes on GitHub
v9.10.2Compare Source
🐞 Bug Fixes
View changes on GitHub
v9.10.1Compare Source
🚀 Features
View changes on GitHub
v9.10.0Compare Source
🚀 Features
--installflag - by @antfu (96a47)View changes on GitHub
v9.9.3Compare Source
🐞 Bug Fixes
View changes on GitHub
v9.9.2Compare Source
No significant changes
View changes on GitHub
v9.9.1Compare Source
🐞 Bug Fixes
View changes on GitHub
v9.9.0Compare Source
🚀 Features
tinyexec- by @antfu (780b7)🐞 Bug Fixes
executetype fix. - by @s3xysteak in https://github.com/antfu-collective/bumpp/issues/59 (bb023)View changes on GitHub
v9.8.1Compare Source
🐞 Bug Fixes
View changes on GitHub
v9.8.0Compare Source
🚀 Features
View changes on GitHub
v9.7.1Compare Source
🐞 Bug Fixes
View changes on GitHub
v9.7.0Compare Source
🚀 Features
View changes on GitHub
v9.6.1Compare Source
🚀 Features
View changes on GitHub
v9.6.0Compare Source
🚀 Features
🐞 Bug Fixes
View changes on GitHub
v9.5.2Compare Source
🐞 Bug Fixes
View changes on GitHub
v9.5.1Compare Source
🚀 Features
View changes on GitHub
v9.5.0Compare Source
🚀 Features
deno.jsonfor version check - by @ryoppippi in https://github.com/antfu-collective/bumpp/issues/37 (9a210)View changes on GitHub
v9.4.2Compare Source
🚀 Features
deno.json&deno.jsoncby default - by @ryoppippi in https://github.com/antfu-collective/bumpp/issues/35 (1480d)View changes on GitHub
v9.4.1Compare Source
v9.4.0Compare Source
🚀 Features
nextas release type - by @Vision010, Anthony Fu and @antfu in https://github.com/antfu/bumpp/issues/15 (81b7e)--current-versionto override the current version - by @murongg and @antfu in https://github.com/antfu/bumpp/issues/17 (48778)🐞 Bug Fixes
View changes on GitHub
v9.3.1Compare Source
🚀 Features
package-lock.json- by @Sec-ant in https://github.com/antfu/bumpp/issues/26 (ba39e)View changes on GitHub
v9.3.0Compare Source
🚀 Features
🐞 Bug Fixes
ReleaseTypeerror - by @dockfries in https://github.com/antfu/bumpp/issues/22 (61500)View changes on GitHub
v9.2.1Compare Source
🚀 Features
customVersionfrom config - by @antfu (86e27)View changes on GitHub
v9.2.0Compare Source
🚀 Features
View changes on GitHub
vitest-dev/vitest (vitest)
v3.1.3Compare Source
🐞 Bug Fixes
inline: trueis set - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/7856 (a83f3)--merge-reportsto show each total run times - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/7877 (d613b)View changes on GitHub
v3.1.2Compare Source
🚀 Features
🐞 Bug Fixes
chaivariable invitest/globals(fix: #7474) - by @Jay-Karia in https://github.com/vitest-dev/vitest/issues/7771 and https://github.com/vitest-dev/vitest/issues/7474 (d9297)test.excludewhen same object passed incoverage.exclude- by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/7774 (c3751)envionmentOptions- by @hi-ogawa in https://github.com/vitest-dev/vitest/issues/7795 (67430)awaitprofiler calls - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/7763 (795a6)Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.