Repository navigation
deps: update npm patch and minor - #150
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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:
26.5.7→26.5.106.42.1→6.43.0Release Notes
i18next/i18next (i18next)
v26.5.10Compare Source
supportedLngs, the best match no longer picks a different language whose code only starts with the same letters. The last fuzzy check took any supported code starting with the language part, so withsupportedLngs: ['en', 'fil-PH']a Finnish user (fi-FI) got Filipino instead of the fallback language, andha(Hausa) pickedhaw-US(Hawaiian). Other regions of the same language still match as before (de-CH→de-DE,pt-PT→pt-BR,fil→fil-PH). Compatibility note: a two-letter code no longer matches a supported three-letter code that extends it, likear→arz-EG,sw→swh-KEorno→nob-NO; list the two-letter code insupportedLngs(or map it withfallbackLng) if you relied on that. Thanks @Pharex38 (#2460).v26.5.9Compare Source
constructor,toStringormap. Only the top level was guarded, so{{constructor}}was treated as missing, but{{user.constructor}}rendered the function source (with a class instance, the full source code of the class), and{{user.toString}},{{items.map}}or a class method like{{user.greet}}did the same. The same lookup is used for translation keys whenignoreJSONStructureis on (the default): a nested key named like an inherited method that is missing in the current language (t('roles.constructor')withroles.constructoronly in the fallback language) returnedfunction Object() { [native code] }instead of falling back, andexists('roles.valueOf')returnedtrue. These keys are now missing, so the fallback language,missingInterpolationHandler,saveMissingand the missing key handler apply as for any other missing key. Getters defined on a class ({{user.fullName}}withget fullName()) still work. Nested lookups also no longer walk into the prototype via__proto__, so{{user.__proto__.constructor}}no longer prints the class source either. Thanks @Pharex38 (#2459).v26.5.8Compare Source
joinArraysnow get the same resolved details as strings. The joined value was extended withlastKeyin the place of the resolved lookup, so withpostProcessPassResolveda post processor got nousedLng,usedNSorexactUsedKey(t('steps', { joinArrays: ' / ' })reportedundefined/undefined:undefined). This affected the subliminal post processor used by the locize InContext editor, which could not map a joined array to its key. The nesting recursion guard did not get the parent key either, so arrays that nest each other (listA: ['a', '$t(listB)'],listB: ['b', '$t(listA)']) threwMaximum call stack size exceeded. They now stop at the guard, as strings do. Ani18nFormatplugin withhandleAsObjectandparsealso no longer throwsCannot read properties of undefined (reading 'usedNS')on joined arrays. Thanks @nk-batman21 (#2458).webpro-nl/knip (knip)
v6.43.0: Release 6.43.0Compare Source
39af70a)46a825d)ba527f7)dbd3a8b) - thanks @tlq5l!@referencein Tailwind CSS compiler (#2177) (219f16d) - thanks @mkantautas!{ find, replacement }array form of Vitealias(#2179) (5d0779b) - thanks @mkantautas!100ef49) - thanks @Cayan!9cf928b) - thanks @jakeleventhal!c301e44) - thanks @abrahamguo!--fixfor exports in multi-declarator variable statements (#2178) (326afd9) - thanks @mkantautas!16d9932) - thanks @abrahamguo!references(#2186) (d741c46) - thanks @mkantautas!@pluginoptions blocks in Tailwind CSS compiler (#2187) (9fae773) - thanks @mkantautas!--fix(#2188) (6748259) - thanks @mkantautas!e971b09) - thanks @TomasHubelbauer!90216c2) - thanks @ryanquinn3!isSsrBuildto Vite config functions (#2191) (d2aa101) - thanks @mkantautas!srcof<script>and<style>blocks in Vue SFCs (#2193) (3d14839) - thanks @mkantautas!--fix(#2192) (231026c) - thanks @mkantautas!b2cc439)parserOptions.parserin ESLint flat configs (#2198) (302f908) - thanks @mkantautas!test.projectsto their config (#2195) (4d38613) - thanks @fixfon!script-*when extracting script blocks (#2199) (23e6479) - thanks @mkantautas!fc92470) - thanks @jakeleventhal!8f21ea2)6569cdc)--fixexport ranges inside a larger removal (204a809).travis.ymlwith a stat instead of a glob (3601c6e)813fa30) - thanks @mkantautas!12e4355) - thanks @mehdimirzafaruk!test.projects(#2197) (ec293d1) - thanks @mkantautas!89dfdc8) - thanks @sushanta-neupane!t,tstandrun-scriptaliases (ce91e23)vitest-environment-nuxtas optional (it comes with@nuxt/test-utils) (db9aa74)9434bf6)21c3b75)engines.nodeto follow Astro's (9d7a5e0)Configuration
📅 Schedule: (in timezone Europe/Istanbul)
* 0-5 * * *)🚦 Automerge: Enabled.
♻ 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.
This PR was generated by Mend Renovate. View the repository job log.