🍍 Intuitive, type safe, light and flexible Store for Vue using the composition api with DevTools support
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
This might be the same issue of computed referencing other computed properties needing an explicit type annotation. Have you tried this:
defineComponent({
data(): { data1: number } {
return {
data1: this.method1(),
}
},
methods: {
method1(): number {
return 1
}
}
})
docs(zh): sync with English version (#1911)
Co-authored-by: Yoshi Otobe 38850403+yoshiotobe@users.noreply.github.com Co-authored-by: Eduardo San Martin Morote posva13@gmail.com Co-authored-by: 林洵锋 linxunfeng@yeah.net Co-authored-by: Eduardo San Martin Morote posva@users.noreply.github.com
I had to do solve some manual merge conflicts. I'm going to give this a look and try to merge it to the other branch to avoid any further issues 😅
chore: up vue
docs: complete migration to vitepress 1
docs: fix slug generation api
chore: remove unused dep
docs: fix ids
docs(fix): api headers
chore: lock
chore: use vitepress updated
refactor: move docs folder
chore: unused font + sponsors update
docs(zh): update actions.md (#1937)
docs: old statement about actions
chore: comment
chore: update vitepress
refactor: type improvement
docs: add home links
docs: add guide to navbar
docs: use lighter green
docs: use script setup
docs: some warnings
chore: remove cache file
Close #1972
chore: up vue
docs: complete migration to vitepress 1
docs: fix slug generation api
chore: remove unused dep
docs: fix ids
docs(fix): api headers
chore: lock
chore: use vitepress updated
refactor: move docs folder
chore: unused font + sponsors update
docs(zh): update actions.md (#1937)
docs: old statement about actions
chore: comment
chore: update vitepress
refactor: type improvement
docs: add home links
docs: add guide to navbar
docs: use lighter green
docs: use script setup
chore: up vue
This PR contains the following updates:
| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
| vue (source) | ^2.7.14
-> ^3.2.47
| |
|
|
|
v3.2.47
v3.2.46
hgroup
to supported HTML_TAGS
(#6321) (7443174), closes #6313
triggerRef
working with toRef
from reactive (#7507) (e64c9ae)feDistanceLight
changed to feDistantLight
(#7540) (bef85e7)active
as readonly property (#6187) (59ffe5e), closes #6186
serverPrefetch()
(#7000) (5f1883e)v3.2.45
<script setup>
binding behavior consistency on this
between prod and dev (f73925d), closes #6248
<script setup>
(5a3d45a), closes #5655
v3.2.44
v3.2.43
v3.2.42
v-if
(#6689) (640cfce), closes #6641
defineProps
statement (#6461) (b72a4af), closes #6428
in
operator returning false
for built-in instance properties in exposeProxy
(#6138) (32b5124), closes #6137
undefined
as initial values (fix: #5032) (#5033) (bc167b5)$watch
callback parameters type (#6136) (41d9c47), closes #6135
Raw
type (#6380) (e9172db), closes #7048
EventHandlers
(#6855) (bad3f3c), closes #6899
v3.2.41
v3.2.40
v3.2.39
v3.2.38
v-bind
(#6489) (2024d11), closes #6201
v3.2.37
v3.2.36
withDefaults
(#5939) (b546282), closes #5938
v3.2.35
$props
(#5968) (0c7fd13)v3.2.34
export { default } from '...'
(#5937) (73e6523), closes #5935
defineComponent
inference to Component
(#5949) (7c8f457)v3.2.33
v3.2.32
v3.2.31
v3.2.30
v3.2.29
v3.2.28
📅 Schedule: Branch creation - "before 3am on Monday" (UTC), 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.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.
This file was included by accident
chore: remove cache file
Close #1972
Now I see that the import maps were version-fixed and had the wrong version of Vue 🥲
4.1.6
https://kotuh6-5173.preview.csb.app/en/
https://kotuh6-5173.preview.csb.app/en/
https://kotuh6-5173.preview.csb.app/en/about
https://kotuh6-5173.preview.csb.app/de/
https://kotuh6-5173.preview.csb.app/de/about
locale
parameter optional:"/:locale(de|en)" ---> "/:locale(de|en)?" (vite.config.js)
https://kotuh6-5173.preview.csb.app/en/
https://kotuh6-5173.preview.csb.app/
https://kotuh6-5173.preview.csb.app/about
https://kotuh6-5173.preview.csb.app/
https://kotuh6-5173.preview.csb.app/about
I expect the locale
parameter to be populated if passed in the URL
If the locale
parameter is not required, it is not filled in even if passed in the URL
Perhaps I am doing something wrong? How can I fill in the locale
parameter, automatically?
I understand that I can pass it manually:
<router-link
:to="{
name: 'index', params: { locale: $route.params.locale }
}"
>
Home
</router-link>
Or use beforeEach
to fetch the parameter from the previous route (in this case the locale will not be visible in the url and it doesn't make sense if I use SSR)
But, isn't there another way?
This is because the parameter is optional so not including it is the way to remove it. So yes, you have to manually pass it. Using a beforeEach()
should also be a way to ensure the parameter is there:
router.beforeEach((to, from) => {
if (!to.params.locale && from.params.locale) {
return { ...to, params: { ...to.params, locale: from.params.locale }}
}
})
Only required params are automatically preserved between navigations when the parameter matches but maybe this shouldn't be the default? I think the idea goes way beyond this though and has a big impact on the usage of vue router, so that should go in a proper RFC
Thanks for taking the time to explain the situation. I understand the reluctance to merge new features without tests. Regarding this functionality being opinionated, I could be wrong but it seems to be a standard among shells to use ctrl p for previous and n for next (differently from using ctrl j or k which is a vim thing). Currently, doing a ctrl sequence still types that invisible ctrl sequence and backspace removes it. It should probably be ignored
Ah i see. Yeah, given the state of IE, you will have to transpile pinia to use it with IE11
Hey @joeykilpatrick, do you know if the author of this package is still active? I noticed you merged the last PR but it hasn't been released
https://github.com/terkelg/prompts/pull/330 should implement this
docs: update sponsors
release: pinia@2.0.30
docs: complete migration to vitepress 1
docs: fix slug generation api
chore: remove unused dep
docs: fix ids
docs(fix): api headers
chore: lock
chore: use vitepress updated
refactor: move docs folder
chore: unused font + sponsors update
docs(zh): update actions.md (#1937)
docs: old statement about actions
chore: comment
chore: update vitepress
refactor: type improvement
docs: add home links
docs: add guide to navbar
docs: use lighter green
docs: use script setup
https://github.com/maIIady/pinia-ie-reproduction
There is no unsupported syntax in pinia.prod.cjs
Opening production build fails in IE11
Reproduction repo also contains workarounds about https://github.com/vuejs/pinia/issues/1143. Production build will also fail if devtools are bundled.
This issue resolves with manual traspilation of node_modules/pinia
with babel-loader (as I did in project I'm currently working on). However I didn't find a way to make it work in IE even with transpileDependencies: true
in vue.config.js
in reproduction example.
Is there a way to remove ES6 syntax from pinia production build or I have to manually transpile it with babel?
PS. Gonna gladly open a PR if you provide some information about possibe fixes
I released a new version with the fix of the spread operator in devtools code but note IE11 is not targeted as a supported versions of the devtools code, only of the production build.
Duplicate of #1143
release: pinia@2.0.30
Did you search existing issues 👀 ? This seems like this one: https://github.com/vuejs/router/issues/600
docs: mention both useRoute
and useRouter
functions (#1680)