Releases: vintl-dev/nuxt
@vintl/[email protected]
@vintl/[email protected]
Patch Changes
- db449d4: Fix missing options in the newer Nuxt versions
@vintl/[email protected]
Patch Changes
-
2590b2f: Downgrade and pin versions of FormatJS packages
Newest versions of FormatJS packages contain exports map that result in illegal ESM as CJS imports. This downgrades them
For more details see the issue at formatjs/formatjs#4126.
@vintl/[email protected]
Patch Changes
-
f62ae92: Adapt to new export conditions of the parser
@formatjs/icu-messageformat-parser
has been updated and now has export conditions, this change adapts and fixes the error caused by the previous direct import of the file forno-parser
alias. -
47f1739: Fix consola not being actually listed as a dependency or used
@vintl/[email protected]
Minor Changes
-
3d41dd1: Update VIntl to 4.2.0
Previously VIntl was depending on Vue directly, which caused issues, and wasn't correct, as Vue is not its implementation detail. 4.2.0 made Vue a peer dependency, fixing this issue. It also brought updates to other dependencies like
@formatjs/intl
.
Patch Changes
- 9756d4a: Upgrade
import-meta-resolve
to v3
@vintl/[email protected]
Patch Changes
-
8f4ca76: Fix compatibility with newer versions of Nuxt
It seems that TypeScript has a trouble identifying similar types from different packages, which caused it to disregard any types from VIntl.
Now that the
@nuxt/schema
is moved todevDependencies
(since it's used for types only anyway), and doesn't have to strictly match the version, this should be fixed.
@vintl/[email protected]
Patch Changes
- 25b5acf: Don't require additionalImports to be a non-empty array
@vintl/[email protected]
Patch Changes
- 71b9000: Fix object import sources not resolving by default
@vintl/[email protected]
Patch Changes
- 70c440e: Fix arrays of imports having incorrect types