mirror of
https://github.com/unraid/api.git
synced 2026-01-01 14:10:10 -06:00
2c01ba9610
This PR contains the following updates: | Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | [vue-i18n](https://redirect.github.com/intlify/vue-i18n/tree/master/packages/vue-i18n#readme) ([source](https://redirect.github.com/intlify/vue-i18n/tree/HEAD/packages/vue-i18n)) | [`^10.0.5` -> `^11.0.0`](https://renovatebot.com/diffs/npm/vue-i18n/10.0.6/11.1.2) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | --- ### Release Notes <details> <summary>intlify/vue-i18n (vue-i18n)</summary> ### [`v11.1.2`](https://redirect.github.com/intlify/vue-i18n/releases/tag/v11.1.2) [Compare Source](https://redirect.github.com/intlify/vue-i18n/compare/v11.1.1...v11.1.2) <!-- Release notes generated using configuration in .github/release.yml at v11.1.2 --> #### What's Changed ##### 🔒 Security Fixes - fix: prototype pollution in `handleFlatJson`, about details see https://github.com/intlify/vue-i18n/security/advisories/GHSA-p2ph-7g93-hw3m **Full Changelog**: https://github.com/intlify/vue-i18n/compare/v11.1.1...v11.1.2 ### [`v11.1.1`](https://redirect.github.com/intlify/vue-i18n/releases/tag/v11.1.1) [Compare Source](https://redirect.github.com/intlify/vue-i18n/compare/v11.1.0...v11.1.1) <!-- Release notes generated using configuration in .github/release.yml at v11.1.1 --> **Full Changelog**: https://github.com/intlify/vue-i18n/compare/v11.1.0...v11.1.1 ### [`v11.1.0`](https://redirect.github.com/intlify/vue-i18n/releases/tag/v11.1.0) [Compare Source](https://redirect.github.com/intlify/vue-i18n/compare/v11.0.1...v11.1.0) <!-- Release notes generated using configuration in .github/release.yml at v11.1.0 --> #### What's Changed ##### 🌟 Features - feat: configurable `ComponentCustomProperties['$i18n']` type by [@​BobbieGoede](https://redirect.github.com/BobbieGoede) in [https://github.com/intlify/vue-i18n/pull/2094](https://redirect.github.com/intlify/vue-i18n/pull/2094) ##### 📝️ Documentations - fix: vue-i18n v8 EOL by [@​kazupon](https://redirect.github.com/kazupon) in [https://github.com/intlify/vue-i18n/pull/2060](https://redirect.github.com/intlify/vue-i18n/pull/2060) **Full Changelog**: https://github.com/intlify/vue-i18n/compare/v11.0.1...v11.1.0 ### [`v11.0.1`](https://redirect.github.com/intlify/vue-i18n/blob/HEAD/CHANGELOG.md#v1101-2024-12-26T074058Z) [Compare Source](https://redirect.github.com/intlify/vue-i18n/compare/v11.0.0...v11.0.1) This changelog is generated by [GitHub Releases](https://redirect.github.com/intlify/vue-i18n/releases/tag/v11.0.1) <!-- Release notes generated using configuration in .github/release.yml at v11.0.1 --> #### What's Changed ##### ⚡ Improvement Features - fix: v-t custom directive warning when it will run by [@​kazupon](https://redirect.github.com/kazupon) in [https://github.com/intlify/vue-i18n/pull/2057](https://redirect.github.com/intlify/vue-i18n/pull/2057) **Full Changelog**: https://github.com/intlify/vue-i18n/compare/v11.0.0...v11.0.1 ### [`v11.0.0`](https://redirect.github.com/intlify/vue-i18n/blob/HEAD/CHANGELOG.md#v1100-2024-12-24T150100Z) [Compare Source](https://redirect.github.com/intlify/vue-i18n/compare/v10.0.6...v11.0.0) This changelog is generated by [GitHub Releases](https://redirect.github.com/intlify/vue-i18n/releases/tag/v11.0.0) <!-- Release notes generated using configuration in .github/release.yml at v11.0.0 --> #### What's Changed ##### Deprecate Legacy API mode The Legacy API mode was the API mode compatible with v8 for Vue 2. When v9 was released, the Legacy API was provided to smooth the migration from v8 to v9. Legacy API mode will be deprecated in v11, as previous vue-i18n releases have already provided the following to support migration to Composition API mode - Migration from Legacy API mode to Composition API mode, see the [docs](https://vue-i18n.intlify.dev/guide/migration/vue3.html) - Composition API usage, see the [docs](https://vue-i18n.intlify.dev/guide/advanced/composition.html) For compatibility, Legacy API mode still works in v11, but will be removed entirely in v12, so Legacy API mode will not work after that version. ##### Deprecate Custom Directive `v-t` The advantage of `v-t` was that it could optimize performance using the vue compiler transform and the pre-translation of `vue-i18n-extension`. This feature was supported from Vue 2. About details see the blog [article](https://medium.com/@​kazu_pon/performance-optimization-of-vue-i18n-83099eb45c2d) In Vue 3, due to the Composition API, the pre-translation of [`vue-i18n-extension`](https://redirect.github.com/intlify/vue-i18n-extensions) is now limited only for global scope. In addition, Vue 3 Virtual DOM optimization has been introduced, and the optimization provided by `vue-i18n-extension` is no longer very effective. We need to require settings for SSR, the benefits of using `v-t` have disappeared. And DX of templates using `v-t` is not good. Custom directives do not work with key completion in editors (e.g. vscode). For compatibility, `v-t` mode still works in v11, but will be removed entirely in v12, so `v-t` will not work after that version. ##### Drop `tc` and `$tc` for Legacy API mode These APIs had already deprecated in warning about being dropped in v11. docs [says](https://vue-i18n.intlify.dev/guide/migration/breaking10.html#deprecate-tc-and-tc-for-legacy-api-mode) ##### Vue I18n maintenance Status Vue I18n v8 is no longer supported after 2025. Vue I18n v9 and Vue I18n v10 is in maintenance mode after 2025 July. With the release of Vue I18n v11, that version will become mainstream. The maintenance detail status of Vue I18n v9 and Vue I18n v10 is as follows: <img src="https://raw.githubusercontent.com/intlify/vue-i18n/master/docs/public/lifecycle2025.svg" /> You can check the maintenance status on the [docs](https://vue-i18n.intlify.dev/guide/maintenance.html) ##### ❗ Braeking Changes - feat!: deprecate Legacy API mode by [@​kazupon](https://redirect.github.com/kazupon) in [https://github.com/intlify/vue-i18n/pull/2016](https://redirect.github.com/intlify/vue-i18n/pull/2016) - breaking: drop `$tc` and `tc` by [@​kazupon](https://redirect.github.com/kazupon) in [https://github.com/intlify/vue-i18n/pull/2017](https://redirect.github.com/intlify/vue-i18n/pull/2017) - feat!: deprecate `v-t` custom directive by [@​kazupon](https://redirect.github.com/kazupon) in [https://github.com/intlify/vue-i18n/pull/2045](https://redirect.github.com/intlify/vue-i18n/pull/2045) ##### ⚡ Improvement Features - fix: `tm` function should accept `DefineLocaleMessage` key type by [@​BobbieGoede](https://redirect.github.com/BobbieGoede) in [https://github.com/intlify/vue-i18n/pull/2014](https://redirect.github.com/intlify/vue-i18n/pull/2014) ##### 🔒 Security Fixes - fix: security vulnerability fix porting by [@​kazupon](https://redirect.github.com/kazupon) in [https://github.com/intlify/vue-i18n/pull/2034](https://redirect.github.com/intlify/vue-i18n/pull/2034) ##### 📝️ Documentations - Change config prop for quasar flags by [@​chrissyast](https://redirect.github.com/chrissyast) in [https://github.com/intlify/vue-i18n/pull/2003](https://redirect.github.com/intlify/vue-i18n/pull/2003) - docs: Pluralization Page by [@​Sammuel09](https://redirect.github.com/Sammuel09) in [https://github.com/intlify/vue-i18n/pull/1998](https://redirect.github.com/intlify/vue-i18n/pull/1998) - docs: fix composition section by [@​Sammuel09](https://redirect.github.com/Sammuel09) in [https://github.com/intlify/vue-i18n/pull/2008](https://redirect.github.com/intlify/vue-i18n/pull/2008) - fix(docs): correct output in composition api example by [@​pejeio](https://redirect.github.com/pejeio) in [https://github.com/intlify/vue-i18n/pull/2012](https://redirect.github.com/intlify/vue-i18n/pull/2012) - docs: not use deprecated api by [@​kazupon](https://redirect.github.com/kazupon) in [https://github.com/intlify/vue-i18n/pull/2013](https://redirect.github.com/intlify/vue-i18n/pull/2013) - docs: fix wrong plural example by [@​kazupon](https://redirect.github.com/kazupon) in [https://github.com/intlify/vue-i18n/pull/2033](https://redirect.github.com/intlify/vue-i18n/pull/2033) - docx(pluralization.md): Correct spelling from 'gloal' to 'global' by [@​PuppyOne](https://redirect.github.com/PuppyOne) in [https://github.com/intlify/vue-i18n/pull/2038](https://redirect.github.com/intlify/vue-i18n/pull/2038) - Fix typo by [@​shaedrich](https://redirect.github.com/shaedrich) in [https://github.com/intlify/vue-i18n/pull/2040](https://redirect.github.com/intlify/vue-i18n/pull/2040) - Fix another typo by [@​shaedrich](https://redirect.github.com/shaedrich) in [https://github.com/intlify/vue-i18n/pull/2041](https://redirect.github.com/intlify/vue-i18n/pull/2041) - docs: add maintenance status by [@​kazupon](https://redirect.github.com/kazupon) in [https://github.com/intlify/vue-i18n/pull/2044](https://redirect.github.com/intlify/vue-i18n/pull/2044) #### 👋 New Contributors - [@​chrissyast](https://redirect.github.com/chrissyast) made their first contribution in [https://github.com/intlify/vue-i18n/pull/2003](https://redirect.github.com/intlify/vue-i18n/pull/2003) - [@​Sammuel09](https://redirect.github.com/Sammuel09) made their first contribution in [https://github.com/intlify/vue-i18n/pull/1998](https://redirect.github.com/intlify/vue-i18n/pull/1998) - [@​pejeio](https://redirect.github.com/pejeio) made their first contribution in [https://github.com/intlify/vue-i18n/pull/2012](https://redirect.github.com/intlify/vue-i18n/pull/2012) - [@​PuppyOne](https://redirect.github.com/PuppyOne) made their first contribution in [https://github.com/intlify/vue-i18n/pull/2038](https://redirect.github.com/intlify/vue-i18n/pull/2038) - [@​shaedrich](https://redirect.github.com/shaedrich) made their first contribution in [https://github.com/intlify/vue-i18n/pull/2040](https://redirect.github.com/intlify/vue-i18n/pull/2040) **Full Changelog**: https://github.com/intlify/vue-i18n/compare/v10.0.4...v11.0.0 </details> --- ### 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 is behind base branch, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR was generated by [Mend Renovate](https://mend.io/renovate/). View the [repository job log](https://developer.mend.io/github/unraid/api). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzOS4yMDcuMSIsInVwZGF0ZWRJblZlciI6IjM5LjIwNy4xIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6W119--> Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
connect-components via Nuxt 3
Install dependencies
npm i
Dev testing and builds with .env setup
There's 3 version required for various types of development, testing builds in the Unraid webgui, and creating a prod build for the Unraid webgui.
.envfornpm run devlocal development.env.stagingfornpm run build:devwhich tests builds in the Unraid webgui.env.productionfornpm run build:webguiwhich does a production build for the Unraid webgui
For the URL values, you can use what you'd like. So if you're testing locally, you can use http://localhost:5555 for the account app if you have a local version running. Alternatively you're free to use the staging or production URLs.
For productions URLs you could ultimately not provide any value and the URL helpers will default to the production URLs. But for local dev and testing, it's usually easiest to keep the .env key value pairs so you don't forget about them.
.env for npm run dev local development
VITE_ACCOUNT=http://localhost:5555
VITE_CONNECT=https://connect.myunraid.net
VITE_UNRAID_NET=https://preview.unraid.net
VITE_OS_RELEASES="https://releases.unraid.net/os"
VITE_CALLBACK_KEY="FIND_IN_1PASSWORD"
VITE_ALLOW_CONSOLE_LOGS=true
VITE_TAILWIND_BASE_FONT_SIZE=16
.env.staging for npm run build:dev which tests builds in the Unraid webgui
Please take a look at the prebuild:dev & postbuild:dev scripts in package.json to see how the .env.staging file is used.
VITE_ACCOUNT=https://staging.account.unraid.net
VITE_CONNECT=https://connect.myunraid.net
VITE_UNRAID_NET=https://staging.unraid.net
VITE_OS_RELEASES="https://releases.unraid.net/os"
VITE_CALLBACK_KEY="FIND_IN_1PASSWORD"
VITE_ALLOW_CONSOLE_LOGS=TRUE
Notice how VITE_TAILWIND_BASE_FONT_SIZE is not set in the .env.staging file.
This is because the Unraid webgui uses the font-size: 62.5% "trick".
.env.production for npm run build:webgui which does a production build for the Unraid webgui
Please take a look at the prebuild:webgui & postbuild:webgui scripts in package.json to see how the .env.production file is used.
VITE_ACCOUNT=https://account.unraid.net
VITE_CONNECT=https://connect.myunraid.net
VITE_UNRAID_NET=https://unraid.net
VITE_OS_RELEASES="https://releases.unraid.net/os"
VITE_CALLBACK_KEY="FIND_IN_1PASSWORD"
Both VITE_ALLOW_CONSOLE_LOGS and VITE_TAILWIND_BASE_FONT_SIZE should never be set here.