posva
Repos
284
Followers
4573
Following
49

Next-gen file based typed routing for vue router

362
19

🍍 Intuitive, type safe, light and flexible Store for Vue using the composition api with DevTools support

9730
674

🚦 The official router for Vue.js

2677
855

🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

202124
32363

🔥 Firebase bindings for Vue.js

3467
288

🦦 Insanely fast image printing in your terminal

C
1167
54

Events

Created at 15 hours ago
issue comment
[Vue2.7] A type error. method can't be called in option "data"

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
    }
  }
})
Created at 20 hours ago

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

Created at 20 hours ago
pull request closed
docs(zh): sync with English version
Created at 20 hours ago
issue comment
docs(zh): sync with English version

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 😅

Created at 21 hours ago

chore: up lock

Created at 21 hours ago

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

Created at 21 hours ago

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

Created at 21 hours ago

chore: up vue

Created at 21 hours ago
pull request closed
chore(deps): update dependency vue to v3

Mend Renovate

This PR contains the following updates:

| Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | vue (source) | ^2.7.14 -> ^3.2.47 | age | adoption | passing | confidence |


Release Notes

v3.2.47

Compare Source

Bug Fixes
  • build: enforce __esModule interop for cjs builds (4b70366)

v3.2.46

Compare Source

Bug Fixes

v3.2.45

Compare Source

Bug Fixes
  • compiler/v-model: catch incorrect v-model usage on prop bindings (001184e), closes #​5584
  • custom-elements: also dispatch hyphenated version of emitted events (#​5378) (0b39e46), closes #​5373
  • custom-elements: custom element should re-instantiate when inserted again (#​6966) (67890da), closes #​6934
  • custom-elements: define declared properties in constructor (#​5328) (55382ae)
  • custom-elements: ensure custom elements can inherit provides from ancestors (#​5098) (192dcb6), closes #​5096
  • custom-elements: fix event emitting for async custom elements (#​5601) (665f2ae), closes #​5599
  • custom-elements: fix number type props casting check (89f37ce), closes #​5793 #​5794
  • custom-elements: properties set pre-upgrade should not show up in $attrs (afe8899)
  • custom-elements: respect slot props in custom element mode (ffef822)
  • custom-elements: should not reflect non-decalred properties set before upgrade (5e50909)
  • hmr/keep-alive: fix error in reload component (#​7049) (a54bff2), closes #​7042
  • runtime-core: fix move/removal of static fragments containing text nodes (#​6858) (4049ffc), closes #​6852
  • sfc: also generate getter for import bindings during dev (0594400)
  • sfc: ensure <script setup> binding behavior consistency on this between prod and dev (f73925d), closes #​6248
  • sfc: ensure consistent dev/prod behavior for non-reactive variables declared in <script setup> (5a3d45a), closes #​5655
  • teleport/css-v-bind: fix css v-bind for teleported content (42239cf), closes #​4605 #​4609
  • teleport/css-v-bind: fix css v-bind in teleport in child component slot (11214ee)
  • v-model: fix incorrect codegen for non-ref bindings (15e889a), closes #​6241

v3.2.44

Compare Source

Bug Fixes
  • watch: for immediate watch with single source, ensure cb is called with undefined as oldValue (#​7075) (5dc593b), closes #​7074

v3.2.43

Compare Source

Bug Fixes
  • watch: ensure oldValue in multi-source watcher is always an array (23e85e2), closes #​7070

v3.2.42

Compare Source

Bug Fixes

v3.2.41

Compare Source

Bug Fixes
  • devtools: avoid memory leak caused by devtools event buffer (24f4c47), closes #​6591
  • devtools: use cleanupBuffer instead of modifying _buffer (#​6812) (35a113e)
  • effectScope: calling off() of a detached scope should not break currentScope (a71f9ac)
  • runtime-core: ensure that errors in slot function execution do not affect block tracking (#​5670) (82a73da), closes #​5657
  • runtime-core: fix v-for ref reactivity behavior difference between prod and dev (#​6714) (9ae796d), closes #​6697
  • runtime-dom: fix event timestamp check in iframes (5ee4053), closes #​2513 #​3933 #​5474

v3.2.40

Compare Source

Bug Fixes
  • compat: list cjs dependencies for compat build (96cd924), closes #​6602
  • compiler-dom: remove v-bind boolean attribute with literal false value when stringifying (#​6635) (6c6fe2c), closes #​6617
  • compiler-sfc: fix expression check for v-on with object literal value (#​6652) (6958ec1), closes #​6650 #​6674
  • compilre-core: dynamic v-on and static v-on should be merged (#​6747) (f9d43b9), closes #​6742
  • runtime-core: avoid hoisted vnodes retaining detached DOM nodes (fc5bdb3), closes #​6591
  • runtime-core: Lifecycle hooks should support callbacks shared by reference (#​6687) (c71a08e), closes #​6686
  • runtime-core: remove prod-only hoisted clone behavior for manual DOM manipulation compat (aa70188), closes #​6727 #​6739
  • runtime-core: unset removed props first in full diff mode (c0d8db8), closes #​6571
  • runtime-dom: fix unnecessary warning when setting coerced dom property value (b1817fe), closes #​6616
  • ssr: avoid ast.helpers duplication (#​6664) (57ffc3e)
  • ssr: fix dynamic slot regression in ssr (8963c55), closes #​6651
  • ssr: fix hydration mismatch when entire multi-root template is stringified (9698dd3), closes #​6637
  • ssr: fix pre tag windows newline hydration mismatch (0382019), closes #​6410
  • ssr: respect case when rendering dynamic attrs on svg (121eb32), closes #​6755

v3.2.39

Compare Source

Bug Fixes

v3.2.38

Compare Source

Bug Fixes
  • compiler-sfc: fix template usage check edge case for v-on statements (769e555)
  • compiler-sfc: only add decorators-legacy parser plugin when new decorators plugin is not used (3ff8369)
  • compiler-sfc: rewriteDefault for class with decorators (#​6320) (81a7819), closes #​6318
  • custom-element: fix event listeners with capital letter event names on custom elements (0739f89)
  • hmr: fix HMR for nested non-SFC components (#​4077) (96eb745)
  • reactivity: fix shallow/readonly edge cases (a95554d)
  • runtime-core: only set cache for object keys (#​6266) (c3465c1)
  • slots: ensure different branches of dynamic slots have different keys (00036bb), closes #​6202
  • ssr: forward helpers provided by CSS v-bind (#​6489) (2024d11), closes #​6201
  • types: add types field for sub package exports (c1ee6ca)
  • types: fix on* props incorrect type for TS 4.7 (#​6216) (8dcb6c7), closes #​6052
  • watch: flush:pre watchers should not fire if state change causes (78c199d), closes #​2291
Features
  • custom-elements: automatically respect custom elements when compiling in browser (9f8f07e)
Performance Improvements

v3.2.37

Compare Source

Bug Fixes

v3.2.36

Compare Source

Bug Fixes
Performance Improvements

v3.2.35

Compare Source

Bug Fixes

v3.2.34

Compare Source

Bug Fixes
  • compiler-core: should generate HYDRATE_EVENTS flag on dynamic component that resolves to element (415091b), closes #​5870
  • compiler-sfc: support export { default } from '...' (#​5937) (73e6523), closes #​5935
  • compiler-sfc: type-only defineProps does not recognize Promise (fix #​5941) (#​5943) (991d623)
  • compiler-ssr: fix component event handlers inheritance in ssr (f811dc2), closes #​5664
  • compiler-ssr: fix wrong attrs fallthrough on non-single-root v-if branches (516bc54), closes #​5140
  • compiler-ssr: only inject fallthrough attrs for root transition/keep-alive (c65b805)
  • keep-alive: fix keep-alive rendering when placed in vnode branch (0841b9b), closes #​4817
  • runtime-core: adjust force diff of dev root fragments (cdda49b), closes #​5946
  • ssr/teleport: support nested teleports in ssr (595263c), closes #​5242
  • ssr: fix hydration error on falsy v-if inside transition/keep-alive (ee4186e), closes #​5352
  • ssr: fix hydration error when teleport is used as component root (b60cff0), closes #​4293
  • ssr: fix hydration error when transition contains comment children (3705b3b), closes #​5351
  • ssr: fix hydration for slot with empty text node (939209c), closes #​5728
  • ssr: fix hydration mismatch caused by multi-line comments inside slot (e1bc268), closes #​5355
  • ssr: inherit scope id on functional component during ssr (847d7f7), closes #​5817
  • ssr: render fallthrough attributes for transition-group with tag (aed10c5), closes #​5141
  • ssr: support client-compiled v-model with dynamic type during ssr (#​5787) (c03459b), closes #​5786
  • types: export ComponentProvideOptions (#​5947) (3e2850f)
  • types: fix defineComponent inference to Component (#​5949) (7c8f457)

v3.2.33

Compare Source

Bug Fixes

v3.2.32

Compare Source

Bug Fixes

v3.2.31

Compare Source

Bug Fixes
  • compiler-ssr: no need to inject resolveDirective calls for setup custom directives (436c500)
  • runtime-core: allow spying on proxy methods (#​4216) (8457d8b)
  • ssr: always hydrate children for HMR (#​5406) (0342fae), closes #​5405

v3.2.30

Compare Source

Features
  • ssr: support custom directive getSSRProps in optimized compilation (60cf175), closes #​5304
Performance Improvements
  • reactivity: optimize effect/effectScope active state tracking (2993a24)

v3.2.29

Compare Source

Bug Fixes

v3.2.28

Compare Source


Configuration

📅 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.


  • [ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

Created at 22 hours ago
issue comment
docs(zh): sync with English version

This file was included by accident

Created at 22 hours ago
pull request closed
fix EOL line
Created at 22 hours ago

chore: remove cache file

Close #1972

Created at 22 hours ago
issue comment
watchEffect within `effectScope()` stops working after navigating away from then back to component

Now I see that the import maps were version-fixed and had the wrong version of Vue 🥲

Created at 22 hours ago
closed issue
Inheritance of optional URL parameters not working

Version

4.1.6

Reproduction link

codesandbox.io

Steps to reproduce

  1. Go to /en/:
https://kotuh6-5173.preview.csb.app/en/
  1. Explore Navigation Links:
https://kotuh6-5173.preview.csb.app/en/
https://kotuh6-5173.preview.csb.app/en/about
  1. Select German language
  2. Explore Navigation Links:
https://kotuh6-5173.preview.csb.app/de/
https://kotuh6-5173.preview.csb.app/de/about
  1. Make the locale parameter optional:
"/:locale(de|en)" ---> "/:locale(de|en)?" (vite.config.js)
  1. Go to /en/:
https://kotuh6-5173.preview.csb.app/en/
  1. Explore Navigation Links:
https://kotuh6-5173.preview.csb.app/
https://kotuh6-5173.preview.csb.app/about
  1. Select German language
  2. Explore Navigation Links:
https://kotuh6-5173.preview.csb.app/
https://kotuh6-5173.preview.csb.app/about

What is expected?

I expect the locale parameter to be populated if passed in the URL

What is actually happening?

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?

Created at 22 hours ago
issue comment
Inheritance of optional URL parameters not working

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

Created at 22 hours ago
issue comment
Add ctrl n, p shortcuts, don't do anything with unknown control sequences

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

Created at 1 day ago
issue comment
Production build targeting IE11 contains ES6 syntax

Ah i see. Yeah, given the state of IE, you will have to transpile pinia to use it with IE11

Created at 1 day ago
issue comment
Add ctrl n, p shortcuts, don't do anything with unknown control sequences

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

Created at 1 day ago
issue comment
Support the use of UNIX keyboard shortcuts for navigation

https://github.com/terkelg/prompts/pull/330 should implement this

Created at 1 day ago

chore: fix tsconfig paths

Created at 1 day ago

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

Created at 1 day ago
closed issue
Production build targeting IE11 contains ES6 syntax (arrow functions)

Reproduction

https://github.com/maIIady/pinia-ie-reproduction

Steps to reproduce the bug

  1. clone repo
  2. npm i -> npm run build -> npx serve ./dist
  3. Try opening production build in IE11 and check errors

Expected behavior

There is no unsupported syntax in pinia.prod.cjs image

Actual behavior

Opening production build fails in IE11

Additional information

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

Created at 1 day ago
issue comment
Production build targeting IE11 contains ES6 syntax (arrow functions)

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.

Created at 1 day ago
issue comment
Production build targeting IE11 contains ES6 syntax (arrow functions)

Duplicate of #1143

Created at 1 day ago

release: pinia@2.0.30

Created at 1 day ago
create tag
posva create tag pinia@2.0.30
Created at 1 day ago
issue comment
getRoutes() no show passing props on the use of addRoute

Did you search existing issues 👀 ? This seems like this one: https://github.com/vuejs/router/issues/600

Created at 1 day ago

docs: mention both useRoute and useRouter functions (#1680)

Created at 1 day ago