repository stringclasses 156 values | issue title stringlengths 1 1.01k ⌀ | labels stringclasses 8 values | body stringlengths 1 270k ⌀ |
|---|---|---|---|
vuejscore | component with v if false break transition mode out in | Bug | version 3 2 21 reproduction link codesandbox io playground without router eyjbchaudnvlijoiphnjcmlwdcbzzxr1cd5cbmltcg9ydcb7ihjlziwgc2hhbgxvd1jlziwgy29tchv0zwqgfsbmcm9ticd2dwunxg4gigltcg9ydcbdb21wigzyb20gjy4vq29tcc52dwunxg4gigltcg9ydcbdb21wmsbmcm9ticcul0nvbxaxlnz1zsdcblxuy29uc3qgbxnnid0gcmvmkcdizwxsbybxb3jszcenkvxuxg5jb25zdcbdb21wb25lbnqgpsbzagfsbg93umvmkenvbxaxkvxuy29uc3qga2v5id0gy29tchv0zwqokckgpt4gq29tcg9uzw50lnzhbhvlid09psbdb21wid8gj2enidogj2inkvxuxg5mdw5jdglvbib0b2dnbguoksb7xg4gienvbxbvbmvudc52ywx1zsa9igtles52ywx1zsa9pt0gj2enid8gq29tcdegoibdb21wxg59xg48l3njcmlwdd5cblxuphrlbxbsyxrlplxua2v5oib7eybrzxkgfx1cbiagpgjyplxuica8ynv0dg9uiebjbgljaz1cinrvz2dszsgpxci xg4gicagvg9nz2xlxg4gidwvynv0dg9uplxuicagicagphryyw5zaxrpb24gbmftzt1cimzhzgvciibtb2rlpvwib3v0lwluxci xg4gicagicagicagpgnvbxbvbmvudca6axm9xcjdb21wb25lbnrciia6a2v5pvwia2v5xciglz5cbiagicagidwvdhjhbnnpdglvbj5cbjwvdgvtcgxhdgu iiwiaw1wb3j0lw1hcc5qc29uijoie1xuicbcimltcg9ydhncijoge1xuicagifwidnvlxci6ifwiahr0chm6ly9zzmmudnvlanmub3jnl3z1zs5ydw50aw1llmvzbs1icm93c2vylmpzxcjcbiagfvxufsisiknvbxaudnvlijoiphrlbxbsyxrlplxuica8zgl2ihytawy9xcjmywxzzvwipknvbxagmdwvzgl2plxupc90zw1wbgf0zt5cbiisiknvbxaxlnz1zsi6ijx0zw1wbgf0zt5cbiagpgrpdib2lwlmpvwidhj1zvwipknvbxagmtwvzgl2plxupc90zw1wbgf0zt5cbij9 a more realistic example eyjbchaudnvlijoiphnjcmlwdcbzzxr1cd5cbmltcg9ydcb7ihjlziwgc2hhbgxvd1jlziwgy29tchv0zwqsihbyb3zpzgugfsbmcm9ticd2dwunxg4gigltcg9ydcbdb21wigzyb20gjy4vq29tcc52dwunxg4gigltcg9ydcbdb21wmsbmcm9ticcul0nvbxaxlnz1zsdcblxuy29uc3qgaxnwaxnpymxlid0gcmvmkhrydwupxg5wcm92awrlkcdzag93jywgaxnwaxnpymxlkvxuxg5jb25zdcbdb21wb25lbnqgpsbzagfsbg93umvmkenvbxaxkvxuy29uc3qga2v5id0gy29tchv0zwqokckgpt4gq29tcg9uzw50lnzhbhvlid09psbdb21wid8gj2enidogj2inkvxuxg5mdw5jdglvbib0b2dnbguoksb7xg4gienvbxbvbmvudc52ywx1zsa9igtles52ywx1zsa9pt0gj2enid8gq29tcdegoibdb21wxg59xg48l3njcmlwdd5cblxuphrlbxbsyxrlplxua2v5oib7eybrzxkgfx1cbiagpgjyplxuica8ynv0dg9uiebjbgljaz1cinrvz2dszsgpxci xg4gicagvg9nz2xlxg4gidwvynv0dg9uplxuicagidxpbnb1dcb0exblpvwiy2hly2tib3hciib2lw1vzgvspvwiaxnwaxnpymxlxci ifzpc2libgvcbiagicagidx0cmfuc2l0aw9uig5hbwu9xcjmywrlxcigbw9kzt1cimlulw91dfwiplxuicagicagicagidxjb21wb25lbnqgomlzpvwiq29tcg9uzw50xcigomtlet1cimtlevwiic8 xg4gicagica8l3ryyw5zaxrpb24 xg48l3rlbxbsyxrlpiisimltcg9ydc1tyxauannvbii6intcbiagxcjpbxbvcnrzxci6ihtcbiagicbcinz1zvwioibcimh0dhbzoi8vc2zjlnz1zwpzlm9yzy92dwuucnvudgltzs5lc20tynjvd3nlci5qc1wixg4gih1cbn0ilcjdb21wlnz1zsi6ijx0zw1wbgf0zt5cbiagpgrpdib2lwlmpvwic2hvd1wipknvbxagmdwvzgl2plxupc90zw1wbgf0zt5cblxuphnjcmlwdcbzzxr1cd5cbmltcg9ydcb7aw5qzwn0fsbmcm9ticd2dwunxg4gignvbnn0ihnob3cgpsbpbmply3qoj3nob3cnkvxupc9zy3jpchq iiwiq29tcdeudnvlijoiphrlbxbsyxrlplxuica8zgl2ihytawy9xcj0cnvlxci q29tccaxpc9kaxy xg48l3rlbxbsyxrlplxuin0 with a toggle for the component visibility step to reproduce 1 click toggle multiple time what be expect the comp1 should be visible when toggle back what be actually happen nothing be display after toggle once |
vuejscore | component ref | Bug | version 3 2 20 reproduction link sfc vuejs org eyjbchaudnvlijoiphrlbxbsyxrlplxuica8zgl2iglkpvwizhluyw1pyy1jb21wb25lbnqtzgvtb1wiignsyxnzpvwizgvtb1wiplxuicagidxidxr0b25cbiagicagicb2lwzvcj1cinrhyibpbib0ywjzxcjcbiagicagica6a2v5pvwidgfixcjcbiagicagica6y2xhc3m9xcjbj3rhyi1idxr0b24nlcb7igfjdgl2ztogy3vycmvudfrhyia9pt0gdgfiih1dxcjcbiagicagicbay2xpy2s9xcjjdxjyzw50vgfiid0gdgfixcjcbiagicagplxuicagicage3sgdgfiih19xg4gicagpc9idxr0b24 xg5cdfx0pgrpdj5cbiagicagidxrzwvwlwfsaxzlplxuicagifx0xhq8y29tcg9uzw50idppcz1cimn1cnjlbnruywjdb21wb25lbnrciia6cmvmpvwiy3vycmvudfrhyljlzlwipjwvy29tcg9uzw50plxuicagicagpc9rzwvwlwfsaxzlplxuicagidwvzgl2plxuxhq8l2rpdj5cbjwvdgvtcgxhdgu xg5cbjxzy3jpchqgbgfuzz1cinrzxcigc2v0dxa xg5pbxbvcnqgeybyzwysig9utw91bnrlzcwgy29tchv0zwqgfsbmcm9ticd2dwunxg5cbmltcg9ydcbib21lvmlldybmcm9ticcul0hvbwvwawv3lnz1zsdcbmltcg9ydcbqb3n0c1zpzxcgznjvbsanli9qb3n0c1zpzxcudnvlj1xuaw1wb3j0iefyy2hpdmvwawv3igzyb20gjy4vqxjjagl2zvzpzxcudnvlj1xuxg5jb25zdcb0ywjzicagicagid0gwydib21ljywgj1bvc3rzjywgj0fyy2hpdmunxvxuy29uc3qgy3vycmvudfrhyiagicagicagica9ihjlzignsg9tzscpxg5jb25zdcbjdxjyzw50vgfiumvmicagicagid0gy29tchv0zwqokckgpt4gy3vycmvudfrhyi52ywx1zsaricdfvmlldycpxg5jb25zdcbjdxjyzw50vgfiq29tcg9uzw50id0gy29tchv0zwqokckgpt4ge1xuicbzd2l0y2ggkgn1cnjlbnruywiudmfsdwupihtcbiagicbjyxnlicdib21ljyagica6ihjldhvybibib21lvmlld1xuicagignhc2ugj1bvc3rzjyagidogcmv0dxjuifbvc3rzvmlld1xuicagignhc2ugj0fyy2hpdmunidogcmv0dxjuiefyy2hpdmvwawv3xg4gih1cbn0pxg5cbmnvbnn0iehvbwvfvmlldyagica9ihjlzihudwxskvxuy29uc3qgug9zdhnfvmlldyagid0gcmvmkg51bgwpxg5jb25zdcbbcmnoaxzlx1zpzxcgpsbyzwyobnvsbclcbmnvbnn0igxvz1jlzia9icgpid0 ihtcbiagy29uc29szs5sb2cosg9tzv9wawv3lnzhbhvllcbqb3n0c19wawv3lnzhbhvllcbbcmnoaxzlx1zpzxcudmfsdwusicc9pt09pt09pt09pt09pt09pt09pt09pt09pt09pscpxg59xg5cbm9utw91bnrlzcgoksa9pib7xg4gihnldeludgvydmfskgxvz1jlziwgmtawmclcbn0pxg48l3njcmlwdd4ilcjpbxbvcnqtbwfwlmpzb24ioij7xg4gifwiaw1wb3j0c1wioib7xg4gicagxcj2dwvcijogxcjodhrwczovl3nmyy52dwvqcy5vcmcvdnvllnj1bnrpbwuuzxntlwjyb3dzzxiuanncilxuicb9xg59iiwisg9tzvzpzxcudnvlijoiphrlbxbsyxrlplxuicbob21lxg48l3rlbxbsyxrlpiisilbvc3rzvmlldy52dwuioii8dgvtcgxhdgu xg4gifbvc3rzxg48l3rlbxbsyxrlpiisikfyy2hpdmvwawv3lnz1zsi6ijx0zw1wbgf0zt5cbiagqxjjagl2zvxupc90zw1wbgf0zt4ifq step to reproduce 1 ref home view value post view value archive view value 2 vite build ref what be expect ref what be actually happen ref |
vuejscore | the function in the lifecycle hook be call only 1 time | Bug | version 3 2 20 reproduction link jsfiddle net fdympu39 step to reproduce in the fiddle press the toggle button 4 time what be expect mount callback call 2 time unmounted callback call 2 time what be actually happen mount callback call 1 time unmounted callback call 2 time |
vuejscore | v model modifier trim number do not work if use hyphenate string in prop and camelize in emit or reverse | Bug | version 3 2 20 reproduction link sfc vuejs org eyjbchaudnvlijoiphnjcmlwdcbzzxr1cd5cbmltcg9ydcb7ihjlzib9igzyb20gj3z1zsdcbmltcg9ydcbdb21wigzyb20gjy4vq29tcc52dwunxg5cbmnvbnn0ig1zzya9ihjlzignsgvsbg8gv29ybgqhjylcbjwvc2nyaxb0plxuxg48dgvtcgxhdgu xg4gidxomt57eybtc2cgfx08l2gxplxuica8q29tccb2lw1vzgvsom1zzy10zxn0lnryaw09xcjtc2dciiavplxupc90zw1wbgf0zt4ilcjpbxbvcnqtbwfwlmpzb24ioij7xg4gifwiaw1wb3j0c1wioib7xg4gicagxcj2dwvcijogxcjodhrwczovl3nmyy52dwvqcy5vcmcvdnvllnj1bnrpbwuuzxntlwjyb3dzzxiuanncilxuicb9xg59iiwiq29tcc52dwuioii8c2nyaxb0ihnldhvwplxuaw1wb3j0ihsgcmvmlcbvbk1vdw50zwqgfsbmcm9ticd2dwunxg5kzwzpbmvqcm9wcyh7xg4gig1zz1rlc3q6ihtcbiagicb0exbloibtdhjpbmcsxg4gicagcmvxdwlyzwq6ihrydwusxg4gih1cbn0pxg4gifxupc9zy3jpchq xg5cbjxzy3jpchq xg4gigv4cg9ydcbkzwzhdwx0ihtcbiagicbtb3vudgvkkckge1xuicagicagdghpcy4kzw1pdcgndxbkyxrlom1zz1rlc3qnlcanicb0zxn0dhr0dcagiccpo1xuicagih0gxg4gih1cbjwvc2nyaxb0plxuxg48dgvtcgxhdgu xg4gidxomj5izwzvcmv7eybtc2duzxn0ih19ywz0zxi8l2gyplxupc90zw1wbgf0zt4ifq step to reproduce see message what be expect trim modifier work what be actually happen trim modifier do not work image |
vuejscore | ref to the element be throw away as soon as the leave active transition state start | Bug | version 3 2 20 reproduction link sfc vuejs org eyjbchaudnvlijoiphnjcmlwdcbzzxr1cd5cbmltcg9ydcb7ihjlziwgy29tchv0zwqgfsbmcm9ticd2dwunxg4gigltcg9ydcbdb21tzw50zwrdb21wb25lbnqgznjvbsanli9db21tzw50zwrdb21wb25lbnqudnvlj1xuicbcbmnvbnn0ihnob3dbbgwgpsbyzwyodhj1zslcblxuy29uc3qgaxrlbxm9cmvmkft7awq6msxuyw1loidvbmunfswge2lkojesbmftztondhdvj30sihtpzdoxlg5hbwu6j3rocmvlj31dkvxuxg5jb25zdcbkaxnwbgf5zwrjdgvtcya9ignvbxb1dgvkkcgppt57xg4giglmkhnob3dbbgwudmfsdwupe1xuicagihjldhvybibpdgvtcy52ywx1zvxuicb9xg4gicbyzxr1cm4gw119kvxuxg48l3njcmlwdd5cblxuphrlbxbsyxrlplxuica8zgl2plxuicagidxidxr0b24gqgnsawnrpvwic2hvd0fsbca9icfzag93qwxsxci vg9nz2xlihryyw5zaxrpb248l2j1dhrvbj5cbiagica8dhjhbnnpdglvbi1ncm91ccbuyw1lpvwizm9vlwjhclwiplxuicagicagpenvbw1lbnrlzenvbxbvbmvudcb2lwzvcj1ciml0zw0gaw4gzglzcgxhewvksxrlbxncilxuicagicagicagicagicagicagicagicagica6a2v5pvwiaxrlbs5pzfwixg4gicagicagicagicagicagicagicagicagidppdgvtlw5hbwu9xcjpdgvtlm5hbwvcii8 xg4gicagicbcbiagica8l3ryyw5zaxrpb24tz3jvdxa xg4gicagxg4gidwvzgl2plxupc90zw1wbgf0zt5cblxuphn0ewxlplxuxhquzm9vlwjhci1szwf2zs10byxcbiaglmzvby1iyxitzw50zxitznjvbxtcbibcdcbvcgfjaxr5oiawo1xuxhr9xg4gic5mb28tymfylwvudgvylwfjdgl2zxtcbiagicb0cmfuc2l0aw9uoibhbgwgmtbzigxpbmvhcjtcbiagfvxuicauzm9vlwjhci1szwf2zs1hy3rpdmuge1xuicagihryyw5zaxrpb246igfsbcaxmhmgbgluzwfyo1xuicb9xg4gifxupc9zdhlszt4ilcjpbxbvcnqtbwfwlmpzb24ioij7xg4gifwiaw1wb3j0c1wioib7xg4gicagxcj2dwvcijogxcjodhrwczovl3nmyy52dwvqcy5vcmcvdnvllnj1bnrpbwuuzxntlwjyb3dzzxiuanncilxuicb9xg59iiwiq29tbwvudgvkq29tcg9uzw50lnz1zsi6ijx0zw1wbgf0zt5cbjxwiebtb3vzzwvudgvypvwibg9nsxrciibyzwy9xcjyzwzlcmvuy2vcij57e2l0zw1oyw1lfx08l3a xg48l3rlbxbsyxrlplxuxg48c2nyaxb0ihnldhvwplxuaw1wb3j0ihtyzwz9igzyb20gj3z1zsdcbmrlzmluzvbyb3bzkhtcbiagaxrlbu5hbwu6ihtcbiagicb0exbloibtdhjpbmcsxg4gicagcmvxdwlyzwq6ihrydwusxg4gih1cbn0pxg4gifxuy29uc3qgcmvmzxjlbmnlid0gcmvmkck7xg4gifxuznvuy3rpb24gbg9nsxqokxtcbiagly8gcmvmiglzihrocm93bibhd2f5igfzihnvb24gyxmgdghlihryyw5zaxrpb24gc3rhcnrzxg4gignvbnnvbguubg9nkhjlzmvyzw5jzs52ywx1zskgly8glt4gbnvsbfxuicbjb25zb2xllmxvzyhyzwzlcmvuy2uudmfsdwuuz2v0qm91bmrpbmddbgllbnrszwn0kckpic8vic0 igvycm9yc1xufvxuxg48l3njcmlwdd4ifq step to reproduce 1 open the reproduction 2 click toggle transition button 3 hover the one two or three element within 10 second and watch the console log what be expect expect to still have a ref to the dom element while it be in a leave active transition state what be actually happen as soon as the leave active transition state begin ref be throw away and there be no access to the element I have mouseenter event that trigger on display item so I d need the ref to access the element while it s leave I have temporarily patch the event handler function to only work on the element if it s there js if reference value please note that the element s ref be available in it s enter active state it s only unavailable in the leave active state even though the element be still present in the dom |
vuejscore | html comment in custom component wrap with break transition | Bug | version 3 2 20 reproduction link sfc vuejs org eyjbchaudnvlijoiphnjcmlwdcbzzxr1cd5cbmltcg9ydcb7ihjlziwgy29tchv0zwqgfsbmcm9ticd2dwunxg4gigltcg9ydcbdb21tzw50zwrdb21wb25lbnqgznjvbsanli9db21tzw50zwrdb21wb25lbnqudnvlj1xuicbcbmnvbnn0ihnob3dbbgwgpsbyzwyozmfsc2upxg5cbmnvbnn0igl0zw1zpxjlzihbe2lkojesbmftztonb25lj30sihtpzdoxlg5hbwu6j3r3byd9lcb7awq6msxuyw1loid0ahjlzsd9xslcblxuy29uc3qgzglzcgxhewvksxrlbxmgpsbjb21wdxrlzcgokt0 e1xuicbpzihzag93qwxslnzhbhvlkxtcbiagicbyzxr1cm4gw2l0zw1zlnzhbhvlwzbdxvxuicb9xg4gihjldhvybibpdgvtcy52ywx1zx0pxg5cbjwvc2nyaxb0plxuxg48dgvtcgxhdgu xg4gidxkaxy xg4gicagpgj1dhrvbibay2xpy2s9xcjzag93qwxsid0gixnob3dbbgxcij5ub2dnbgugdhjhbnnpdglvbjwvynv0dg9uplxuicagidx0cmfuc2l0aw9ulwdyb3vwig5hbwu9xcjmb28tymfyxci xg4gicagica8q29tbwvudgvkq29tcg9uzw50ihytzm9ypvwiaxrlbsbpbibkaxnwbgf5zwrjdgvtc1wiidprzxk9xcjpdgvtlmlkxcigoml0zw0tbmftzt1ciml0zw0ubmftzvwipjwvq29tbwvudgvkq29tcg9uzw50plxuicagicagxg4gicagpc90cmfuc2l0aw9ulwdyb3vwplxuicagifxuica8l2rpdj5cbjwvdgvtcgxhdgu iiwiaw1wb3j0lw1hcc5qc29uijoie1xuicbcimltcg9ydhncijoge1xuicagifwidnvlxci6ifwiahr0chm6ly9zzmmudnvlanmub3jnl3z1zs5ydw50aw1llmvzbs1icm93c2vylmpzxcjcbiagfvxufsisiknvbw1lbnrlzenvbxbvbmvudc52dwuioii8dgvtcgxhdgu xg48cd57e2l0zw1oyw1lfx08l3a xg48is0tvghpcybjb21tzw50igjyzwfrcybpdc0tplxupc90zw1wbgf0zt5cblxuphnjcmlwdcbzzxr1cd5cbmrlzmluzvbyb3bzkhtcbiagaxrlbu5hbwu6ihtcbiagicb0exbloibtdhjpbmcsxg4gicagcmvxdwlyzwq6ihrydwusxg4gih1cbn0pxg5cbjwvc2nyaxb0pij9 step to reproduce open the link and click the toggle transition button what be expect expect normal transition behavior what be actually happen transition group throw an error typeerror child el getboundingclientrect be not a function I ve add the html comment in customcomponent vue remove it and the transition will work I assume vue read the html comment as the second template s root element have problem with this for hour because I leave one html tag comment out in my component figure it out by sheer luck |
vuejscore | warn when emit kebab case custom event | Bug | version 3 2 20 reproduction link sfc vuejs org eyjbchaudnvlijoiphnjcmlwdcbzzxr1cd5cbmltcg9ydcbdb21wigzyb20gjy4vq29tcc5qcydcbjwvc2nyaxb0plxuxg48dgvtcgxhdgu xg4gidxdb21wic8 xg48l3rlbxbsyxrlpiisimltcg9ydc1tyxauannvbii6intcbiagxcjpbxbvcnrzxci6ihtcbiagicbcinz1zvwioibcimh0dhbzoi8vc2zjlnz1zwpzlm9yzy92dwuucnvudgltzs5lc20tynjvd3nlci5qc1wixg4gih1cbn0ilcjdb21wlmpzijoiaw1wb3j0ihsgzgvmaw5lq29tcg9uzw50lcbvbk1vdw50zwqsigggfsbmcm9ticd2dwunxg5lehbvcnqgzgvmyxvsdcbkzwzpbmvdb21wb25lbnqoe1xuxhruyw1loianvghpbmcnlfxuicbwcm9wczogeybvbk5ld1zhbhvloibgdw5jdglvbib9lfxuicblbwl0czogw10sxg4gihnldhvwkhbyb3bzlcb7igvtaxqgfskge1xuicagig9utw91bnrlzcgoksa9pib7xg4gicagicblbwl0kcduzxctdmfsdwunlcanc29tzsb2ywx1zscpxg4gicagfslcblx0fsxcbiagcmvuzgvykckge1xuicagihjldhvybibokcdzcgfujywgwydizwxsbybxb3jszcddkvxuicb9xg59ktsifq step to reproduce open sfc what be expect no warning to be log as component define onnewvalue prop what be actually happen warning in console component emit event new value but it be neither declare in the emit option nor as an onnew value prop have a component that emit a kebab case event e g new value as in quasar s qselect you see the follow warning component emit event new value but it be neither declare in the emit option nor as an onnew value prop the component actually define a prop name onnewvalue without list new value in the component s emit property it look like this be due to the tohandlerkey l126 helper only capitalize l120 the event name which then only convert the first character to uppercase convention do t allow non camelize property so I think the tohandlerkey actually need to capitalize camelize str |
vuejscore | custom transform style be clear while have compute transform attribute | Bug | version 3 2 19 reproduction link codepen io step to reproduce click add what be expect item move to next position what be actually happen some item transform style be |
vuejscore | nest teleport of disabled teleport stay in dom when parent be unmounted | Bug | version 3 2 19 reproduction link codesandbox io step to reproduce 1 use a teleport and set it s disabled prop be true 2 put some component inside 3 make the teleport unmount e g v if switch route or other 4 these child component will not be unmount what be expect these child component will be unmount what be actually happen these child component will not be unmount |
vuejscore | type inference incorrect of definecomponent with htmlattribute | Bug | version 3 2 19 reproduction link step to reproduce ts const prop propa number propb string number propc type string require true const comp definecomponent prop setup return as unknown as definecomponent const render const onclick return what be expect what be actually happen image type number be not assignable to type numberconstructor |
vuejscore | transition group throw error attempt to transition whitespace node but only with migration build and client side compile template | Bug | version 3 2 11 reproduction link codesandbox io step to reproduce load the codesandbox link open the codesandbox console use the console link in the bottom leave corner of the preview area and note that a warning about have already appear click the toggle transition button what be expect the transition work the hidden image appear what be actually happen an error be throw when attempt the transition child el getboundingclientrect be not a function and the transition doesn t work additionally a warning be throw on load child must be key this issue be relate to 4621 but it s a much more bizarre version of it all of the follow condition must be meet to reproduce the bug a that contain two element separate by whitespace with the first element initially hide use v if and the second element always show unhide the first element trigger the error the migration build vue compat must be use the bug doesn t happen if you use the regular non migration build vue the component contain the must be compile on the client side the bug doesn t happen if this component be pre compile on the server side to make client side compilation work the full build must be use rather than the runtime only build like in 4621 the bug happen because the transitiongroup code try to process a text node as one of the node be transition in this case the text node between the two element text nodes don t have a getboundingclientrect method which be what cause the error the warning about transitiongroup child need to be key be also cause by the text node it s check for a key and it doesn t have one in the real world use case that reveal this bug see 7322619 the have tag div set one of the child be a component instead of a plain tag and the be nest inside a via another component s slot but those thing don t appear to matter so I ve remove they to simplify the already complex minimal reproduction |
vuejscore | component do not have default export with multiple | Bug | version 3 2 4 reproduction link step to reproduce 1 init the proyect with yarn serve 2 see the error that happen with helloworld component what be expect can export interface and other var in a normal |
vuejscore | nest element in keep alive component be replace before the transition | Bug | version 3 1 1 reproduction link playground eyjbchaudnvlijoiphrlbxbsyxrlplxuica8bwfpbj5cbiagicbxaxrob3v0ifjvdxrlclxuicagidxidxr0b24gqgnsawnrpvwidg9nz2xlvmlld1wiplrvz2dszsbwawv3pc9idxr0b24 xg4gicagpghyic8 xg4gicagphryyw5zaxrpb24gbmftzt1cimzhzgvciibhchblyxigbw9kzt1cim91dc1pblwiplxuicagicagpgtlzxatywxpdmu xg4gicagicagidxjb21wb25lbnqgomlzpvwivmlld1wipjwvy29tcg9uzw50plxuicagicagpc9rzwvwlwfsaxzlplxuicagidwvdhjhbnnpdglvbj5cbiagpc9tywluplxupc90zw1wbgf0zt5cblxuphnjcmlwdcbzzxr1cd5cbmltcg9ydcb7ig1hcmtsyxcsihnoywxsb3dszwysihbyb3zpzgugfsbmcm9ticd2dwunxg5pbxbvcnqgrm9vigzyb20gjy4vrm9vlnz1zsdcbmltcg9ydcbcyxigznjvbsanli9cyxiudnvlj1xuxg5jb25zdcbwawv3id0gc2hhbgxvd1jlzihtyxjrumf3kezvbykpxg5cbnbyb3zpzguoj3zpzxcnlcbwawv3kvxuxg5mdw5jdglvbib0b2dnbgvwawv3kckge1xuicbpziaovmlldy52ywx1zsa9pt0grm9vksb7xg4gicagvmlldy52ywx1zsa9ig1hcmtsyxcoqmfykvxuicb9igvsc2uge1xuicagifzpzxcudmfsdwugpsbtyxjrumf3kezvbylcbiagfvxufvxupc9zy3jpchq xg5cbjxzdhlszt5cbiaglmzhzgutzw50zxitywn0axzllfxulmzhzgutbgvhdmutywn0axzlihtcbiagb3bhy2l0etogmttcbiagdhjhbnnmb3jtoib0cmfuc2xhdguzzcgwlcawlcawkttcbiagdhjhbnnpdglvbjogywxsidewmdbtcybjdwjpyy1izxppzxiomc40lcawlji1lcawljisidepo1xufvxulmzhzgutzw50zxitznjvbsxcbi5mywrllwxlyxzllxrvihtcbiagb3bhy2l0etogmdtcbiagdhjhbnnmb3jtoib0cmfuc2xhdguzzcgwlcaymhb4lcawkttcbn1cbjwvc3r5bgu iiwirm9vlnz1zsi6ijx0zw1wbgf0zt5cbiagpgrpdj5cbiagica8cd5gb288l3a xg4gicagpgnvbxbvbmvudca6axm9xcjwawv3xciglz5cbiagpc9kaxy xg48l3rlbxbsyxrlplxuxg48c2nyaxb0ihnldhvwplxuaw1wb3j0ihsgaw5qzwn0lcbwcm92awrlih0gznjvbsandnvlj1xuxg5jb25zdcbpc0rvbmugpsbpbmply3qoj2rvbmunlcbmywxzzslcbnbyb3zpzguoj2rvbmunlcb0cnvlkvxuy29uc3qgvmlldya9iglzrg9uzsa ig51bgwgoibpbmply3qoj3zpzxcnkvxupc9zy3jpchq xg4ilcjcyxiudnvlijoiphrlbxbsyxrlplxuica8zgl2plxuicagidxidxr0b24 qmfypc9idxr0b24 xg4gicagpgnvbxbvbmvudca6axm9xcjwawv3xciglz5cbiagpc9kaxy xg48l3rlbxbsyxrlplxuxg48c2nyaxb0ihnldhvwplxuaw1wb3j0ihsgaw5qzwn0lcbwcm92awrlih0gznjvbsandnvlj1xuxg5jb25zdcbpc0rvbmugpsbpbmply3qoj2rvbmunlcbmywxzzslcbnbyb3zpzguoj2rvbmunlcb0cnvlkvxuy29uc3qgvmlldya9iglzrg9uzsa ig51bgwgoibpbmply3qoj3zpzxcnkvxupc9zy3jpchq xg4ifq step to reproduce 1 click on toggle multiple time what be expect it should transition from foo foo to bar bar and vice versa what be actually happen it transition from foo bar to bar bar and then bar foo foo foo simplify from remove keepalive fix the problem this behavior be different from vue 2 |
vuejscore | wrap around transition component throw when transition be toggle before it have complete previously | Bug | version 3 0 11 reproduction link link eyjbchaudnvlijoiphrlbxbsyxrlplxuica8zgl2plxuxhqgicagpgxhymvsplrvz2dszsb0aglzignozwnrym94igzhc3rlcib0agfuigl0cybkdxjhdglvbjwvbgfizww xg5cdcagica8aw5wdxqgdhlwzt1cimnozwnrym94xcigbmftzt1cinnob3dciib2lw1vzgvspvwic2hvd1wilz5cbiagica8l2rpdj5cblx0xhq8zgl2ihn0ewxlpvwid2lkdgg6idewmhb4oybozwlnahq6idewmhb4o1wiplxuxhrcdfx0pgn1c3rvbs10cmfuc2l0aw9uig5hbwu9xcjmywrllwlub3v0xci xg5cdfx0xhrcddxkaxygdi1pzj1cinnob3dciibzdhlszt1cindpzhrooiaxmdbwedsgagvpz2h0oiaxmdbwedsgymfja2dyb3vuzdogy29yywxcij48l2rpdj5cblx0xhrcddwvy3vzdg9tlxryyw5zaxrpb24 xg5cdfx0pc9kaxy xg48l3rlbxbsyxrlplxuxg48c2nyaxb0ihnldhvwpvwichjvchncij5cbiagaw1wb3j0ihsgcmvmih0gznjvbsbcinz1zvwio1xuicbpbxbvcnqgq3vzdg9tvhjhbnnpdglvbibmcm9tifwili9ddxn0b21ucmfuc2l0aw9ulnz1zvwio1xuicbcbiagy29uc3qgc2hvdya9ihjlzihmywxzzslcbibcbjwvc2nyaxb0plxuphn0ewxlplxuicbcbiaglmzhzgutaw5vdxqge1xuicagihryyw5zaxrpb24tchjvcgvydhk6ig9wywnpdhk7xg4gicagdhjhbnnpdglvbi1kdxjhdglvbjogmtawmg1zo1xuicagihryyw5zaxrpb24tdgltaw5nlwz1bmn0aw9uoiblyxnllw91ddtcbiagfvxuicbcbiaglmzhzgutaw5vdxqtzw50zxitywn0axzllcauzmfkzs1pbm91dc1szwf2zs1hy3rpdmuge1xuicagihryyw5zaxrpb24tchjvcgvydhk6ig9wywnpdhk7xg4gicagdhjhbnnpdglvbi1kdxjhdglvbjogmtawmg1zo1xuicagihryyw5zaxrpb24tdgltaw5nlwz1bmn0aw9uoiblyxnllw91ddtcbiagfvxuicbcbiaglmzhzgutaw5vdxqtzw50zxitznjvbswglmzhzgutaw5vdxqtbgvhdmutdg8ge1xuicagig9wywnpdhk6ida7xg4gih1cbjwvc3r5bgu iiwiq3vzdg9tvhjhbnnpdglvbi52dwuioii8dgvtcgxhdgu xg5cddx0cmfuc2l0aw9uihytymluzd1ciirwcm9wc1wiidpjbgfzcz1cilskchjvchmubmftzv1cij5cbiagica8c2xvdd48l3nsb3q xg4gidwvdhjhbnnpdglvbj5cbjwvdgvtcgxhdgu xg48c2nyaxb0ihnldhvwplxuicbcbi8viefsbcb0aglzignvbxbvbmvudcbkb2vziglzihdyyxagyxjvdw5kigegc3rhbmrhcmqgdhjhbnnpdglvbibhbmqgywrkcybhignsyxnzihdpdgggdghlig5hbwugb2ygdghligrlc2lyzwqgdhjhbnnpdglvbiwgxg4vlybuaglziglzigluc3rlywqgb2ygdxnpbmcgdghligvudgvyl2xlyxzllwfjdgl2zsbjbgfzc2vzlcb3agljacbjyxvzzsb0agugdhjhbnnpdglvbib0byb1bmrlc2lyywjsesbqdw1wigjldhdlzw4gc3rhdgvzihdozw4gdg9nz2xlzcbizwzvcmugaxqgagfzignvbxbszxrlzcb0agugchjldmlvdxmgdhjhbnnpdglvblxuaw1wb3j0ihsgzgvmaw5luhjvchmgfsbmcm9tifwidnvlxci7xg4gifxuy29uc3qgchjvchmgpsbkzwzpbmvqcm9wcyh7xg4gig5hbwu6ifn0cmluz1xufsk7icbcbjwvc2nyaxb0pij9 step to reproduce toggle the check box to start the transition then toggle it again before it have complete try replace the custom transition component with the standard transition what be expect should be able to toggle a transition as quickly as I like what be actually happen a warning and two error be throw any further attempt to toggle the transition at all produce the same error vue warn unhandled error during execution of scheduler flush this be likely a vue internal bug please open an issue at at at at at uncaught typeerror can not read property 0 of undefined at object on console index 969554ad js 1 at pw handle repl message index 969554ad js 1 at handle event index 969554ad js 1 uncaught in promise typeerror can not read property leavecb of null at object beforeenter vue runtime esm browser js 3490 at mountelement vue runtime esm browser js 5938 at processelement vue runtime esm browser js 5882 at patch vue runtime esm browser js 5802 at componenteffect vue runtime esm browser js 6369 at reactiveeffect vue runtime esm browser js 342 at callwitherrorhandle vue runtime esm browser js 1335 at flushjob vue runtime esm browser js 1561 |
vuejscore | v if resolvedynamiccomponent compute when hide or delete component will cause null reference | Bug | version 3 0 11 reproduction link step to reproduce see codesandbox for detail when click delate button will cause uncaught in promise typeerror can not read property type of null what be expect normal work no error will be report what be actually happen runtime core esm bundler js 5c40 4818 uncaught in promise typeerror can not read property type of null at unmountcomponent runtime core esm bundler js 5c40 4818 at unmount runtime core esm bundler js 5c40 4736 at unmountchildren runtime core esm bundler js 5c40 4864 at unmount runtime core esm bundler js 5c40 4754 at patch runtime core esm bundler js 5c40 3760 at patchblockchildren runtime core esm bundler js 5c40 4091 at processfragment runtime core esm bundler js 5c40 4152 at patch runtime core esm bundler js 5c40 3784 at componenteffect runtime core esm bundler js 5c40 4368 at reactiveeffect reactivity esm bundler js a1e9 42 |
vuejscore | invalid vnode type when create vnode | Bug | version 3 0 11 reproduction link step to reproduce const type ref open the console in the low right corner and then you can see some warning eg vue warn invalid vnode type when create vnode const type ref null there be no those warn what be expect const type ref no those warn what be actually happen const type ref vue warn invalid vnode type when create vnode |
vuejscore | switch between slot child s child that have v if do not update dom | Bug | version 3 0 11 reproduction link step to reproduce click button click I multiple time what be expect text below button should show 1 2 3 in a loop what be actually happen text show 1 1 3 instead also happen without child default use instead in this variant original context be a tab component |
vuejscore | v if work incorrectly when use with sparse array | Bug | version 3 0 11 reproduction link step to reproduce 1 clone this repo or open it on codesandbox 2 run and open it with chrome browser 3 click the router link use sparse array and vshow 4 open element devtool panel and inspect the expand ul tag recursively 5 when click on remove first button you will see only remove element be re render as expect 6 but if you change tab to use sparse array and vif and click the button again all element be re render what be expect only the remove element be re render what be actually happen all element be re render this behavior be work correctly in vue 2 |
vuejscore | typescript unable to compile project when return extended array interface from datum | Bug | version 3 0 11 reproduction link see app vue step to reproduce run npm run build what be expect typescript should compile project should be able to assign the array return from datum to both array and myarray type what be actually happen typescript compiler complain about assignment of the array return from datum ts2739 type x number number length number tostre string tolocalestre string pop number undefined push item number number concat item concatarray number item number concatarray number 25 more flat 19 const x array this array 20 const y myarray this array 21 console log x y 22 this work as expect with version prior to vue 3 0 8 if this be a problem with vue can anyone suggest a temporary workaround until this be fix I can t change the type since in the actual real project this be a nest type inside 3rd party library |
vuejscore | hydration error when async component be use as app root | Bug | version 3 0 7 reproduction link step to reproduce create ssr application and attempt hydration with an app that use async component what be expect hydration occur smoothy what be actually happen error be throw uncaught in promise typeerror can not read property proxy of null posva I search here for this issue and I find the issue 2626 but I already try the recommend solution there and it didn t help I m not use vite yet this be pure vue v3 0 7 before I be pass a vue defineasynccomponent to the vuerout configuration but I already replace that with a function that return a promise that return the component definition I also be enhance the vue resolvecomponent function myownfunction that load the component base on the name and this be return a vue defineasynccomponent value the error be here js function createappapi render hydrate return function createapp rootcomponent rootprop null snip const app context app snip mount rootcontainer ishydrate if ismounte snip return vnode component proxy vnode component be null below be the value of vnode js v isvnode true v skip true type name asynccomponentwrapper setup setup const instance currentinstance already resolve if resolvedcomp return asyncloader proto object prop null key null ref null scopeid null child null component null suspense null sscontent null ssfallback null dir null transition null el null anchor null target null targetanchor null staticcount 0 shapeflag 4 patchflag 0 dynamicprop null dynamicchildren null appcontext null before I be get a warning from vuerouter say that I couldn t use vue defineasynccomponent on the route definition after I change it I m no long get that warning but somehow I still have the vnode component be null error |
vuejscore | derive child vnode prop inside render function can be break by static template optimization | Bug | version 3 0 7 reproduction link image step to reproduce follow the link I mean to derive some prop before its child do the first rendering however it win t re render in a template context what be expect re render should work what be actually happen doesn t happen |
vuejscore | vue warn incorrectly if component be surround by functional component | Bug | version 3 0 5 reproduction link step to reproduce please have a look at the minimal reproduction as soon as I create a component inside of a functional component it show s a warning what be expect it shouldn t warn what be actually happen vue warn slot default invoke outside of the render function this will not track dependency use in the slot invoke the slot function inside the render function instead the warning be only show if I create the watch in mycomponent vue or if I access ismandatoryorslotvisible value directly if I use the same code without the surround mycontainer component it work s without any warning since there be no invokation of the slot function in the surround mycontainer component the warning be mislead |
vuejscore | class undefined cause class be render | Bug | version 3 2 6 step to reproduce html what be expect none of title class style should be render what be actually happen class be render the same thing apply to null additional info this be fix in v3 1 5 but be reproducible eyjbchaudnvlijoiphrlbxbsyxrlplxuica8zgl2idp0axrszt1cinvuzgvmaw5lzfwiidpjbgfzcz1cinvuzgvmaw5lzfwiidpzdhlszt1cinvuzgvmaw5lzfwiplxuicagigzvb1xuica8l2rpdj5cbjwvdgvtcgxhdgu in0 when use the late commit |
vuejscore | inconsistent behaviour on nest transition group | Bug | version 3 0 0 beta 18 reproduction link codepen vue 2 version vue 3 version step to reproduce bug 1 1 open vue 3 example click reverse outer button title transition in correct position but nest transition group team name with red and green will be instantly teleport to side then start transition in vue 2 example nest transition group be animate right bug 2 this be vue 2 bug maybe should be discuss on vue 2 repo 1 open vue 2 example click reverse inner button then click right after to reverse outer button in this case the nest transition group team name with red and green at the left one will lose its transition animation in vue 3 example this issue be not happen what be expect describe what be actually happen describe I move my flex flex row class from div match to nest transition group on vue 2 example because it be wrap |
vuejscore | regression of multiselect integer form value 3 4 15 | Bug | vue version 3 4 15 link to minimal reproduction step to reproduce please see the reproduction link since 3 4 15 all html multiselect option be only preselecte if the data array value be string integer array value be now ignore and not match to their string counterpart what be expect in the following example the multiselect form field have pre select value vue 3 4 14 what be actually happen it seem vue disregard the original model value due to the int string type change this be a change in behaviour to all previous version of vue and differ in behaviour to single select field which continue to work as expect eg integer value 2 be match correctly to two system info shell n a impact firefox chrome on linux mac and window any additional comment vue have always have a relaxed integer string relationship regard select value in form give that all form select value be in fact string eg two I have work out that this regression be introduce in 3 4 15 and I suspect via commit v model optimize v model multiple select w large list 2ffb956 |
vuejscore | vue 3 4 21 where style result be not as expect | Bug | vue version 3 4 21 link to minimal reproduction enp9ktflwzaqxv vce8koz7ou50dlt3og4r6gjaupbtsarksszcz 9 9tgywisufxl7vd8d3ptu4977oekij06ic9iqiuvizaadxg8alxwhbbyrcbns6e8pumd5j4foci3wob27kox8waujrpb diirnswalygn20i4qtw6cs7yurcd6vtp9xrndbpyy8kjcug7d5sm8manh9felshd4ijub0q4cr5qzzgacxdnst26kvxswt cmisqo13ptmlx60s5gcwuej irubnjn 9rihh5kcrjar1p oqbrmm4s1gxnchhknhvwiqbnv 8yjbro9m6 pkmd5jvmn0juwma baq3lsedenfwq9c6rt8xnnw0ibd0vlojnc97we guez6z f e6uon7 hvc hedhsu4 step to reproduce visit link enp9ktflwzaqxv vce8koz7ou50dlt3og4r6gjaupbtsarksszcz 9 9tgywisufxl7vd8d3ptu4977oekij06ic9iqiuvizaadxg8alxwhbbyrcbns6e8pumd5j4foci3wob27kox8waujrpb diirnswalygn20i4qtw6cs7yurcd6vtp9xrndbpyy8kjcug7d5sm8manh9felshd4ijub0q4cr5qzzgacxdnst26kvxswt cmisqo13ptmlx60s5gcwuej irubnjn 9rihh5kcrjar1p oqbrmm4s1gxnchhknhvwiqbnv 8yjbro9m6 pkmd5jvmn0juwma baq3lsedenfwq9c6rt8xnnw0ibd0vlojnc97we guez6z f e6uon7 hvc hedhsu4 1 hover div block 2 the hover effect be not apply because between 3 3 4 and 3 4 21 vue change the approach and because of scope the specificity of this style be downgrade instead of upgrade what be expect hover work properly what be actually happen hover be not work system info shell system os macos 14 3 1 cpu 10 arm64 apple m1 pro memory 50 53 mb 32 00 gb shell 5 9 bin zsh binarie node 20 9 0 nvm version node v20 9 0 bin node yarn 1 22 19 nvm version node v20 9 0 bin yarn npm 10 1 0 nvm version node v20 9 0 bin npm pnpm 7 26 3 nvm version node v20 9 0 bin pnpm browser chrome 122 0 6261 112 safari 17 3 1 any additional comment no response |
vuejscore | fail to parse | Duplicate | vue version 3 3 4 link to minimal reproduction enp9kdglajeqhf kms01slfcvsihp1hooakwassoazq7czlef2 t u0lkvwuxe7zvdbw3n i3trwehcgmwdpl d9xj0bfvdmpqtaaz9lqqvxliq3fw5ugohagtw2vrre0xhliacmik8r2wpvrphvebrx0vjyipl xt9wkt8dkiao7oice z2r0d wdlpajuoe1myfdex ggtko0pq iina 1j7zdcbjurrxfeubxlaeorubuviqzkm mc4vcmh6y 6 6uv louavthu7aews step to reproduce n a what be expect should not throw what be actually happen invalid end tag be throw system info no response any additional comment no response |
vuejscore | fix warning stringify args in warn handler | Bug | close 10409 |
vuejscore | vue render option tag with empty value attribute without attribute | Bug | vue version 3 4 20 link to minimal reproduction enp9ktfpwzaqhf k5suglwaaqarigdraaagyvytk2ro4tmwf06aq 52zrzqoqjt977t37 wdv7d23gfgc175xkmlzamgeye07kxxya7mwzqnbo1mxwpci1uhhw6m9pfv0cc0bbmpi6k4jleqsxn50awhs6pgobtjvw5 g vvnwlblwschwrnaileojwz9rqiqqmjqslgjjpan12fskyct6gmsbsfrgr3erafijeiqmpvkmwweqzeqpendzxw9rbgwm nog01pcii84i3prftgxpojf3zbkhk1wimzf041dbrkqjdbal7 qe 8egucvznw4hoq khh7taawv59vmba56nidxqu0wfed bghzgxyw9btxt7hetpn9jhsr359ksbqftpqrg0kmpibafpftyz l c6 ln6hn65omvj0lcwq step to reproduce 1 create select tag 2 create what be expect html what be actually happen html system info shell system os linux 5 15 linux mint 21 2 victoria cpu 12 x64 amd ryzen 5 5600 g with radeon graphic memory 11 49 gb 30 64 gb container yes shell 5 1 16 bin bash binary node 21 4 0 nvm version node v21 4 0 bin node yarn 1 22 21 nvm version node v21 4 0 bin yarn npm 10 4 0 nvm version node v21 4 0 bin npm pnpm 8 15 4 nvm version node v21 4 0 bin pnpm bun 1 0 26 nvm version node v21 4 0 bin bun browser chrome 121 0 6167 184 npmpackage vue 3 4 20 3 4 20 any additional comment no response |
vuejscore | hydration node mismatch warning will lead to error | Bug | vue version 3 2 47 link to minimal reproduction ssr enqnks1owzaqhf9l5qutqfl tivuaoqehaab4ojrznjtaurylu00rvxfnxxslb5qhzsdd2d2 m 6sfbu0nlluyeys9bmtnodhunkx17nrpkdpc7gazsycs64n zuztudhsvi2akzqsz0xdwswchnlil6hzkdqrzppkywt1mzzqvjufkktnl4veqlq9bmw0952y3 fncc junl00rnqronvrk9fwuoyfeoidiry7sjoesuj3sh728vqjx joaadmez1z p5jxx9ktdfgqhocjgazuisbvaasfp7hi8wjvy1ut0sfu6tgmbx3asbmcc30 t 8kyt3iyoz7kprat0jzyg95ynyboum6guqe bxnavdrp psn8 kf yy9jj7mnh8rugzxttsbcgagvb14ecennrviasaxivud8rqjwxyyt7apqoo 4mrr3ptuusf28 ptlqo27s8wgddpgzxn9y9d7rv4b9zq5674fucww6ojoakhccnle1j h oll step to reproduce if you see ssr error just delete the word and repair it then you can see the target error what be expect fix this issue soon what be actually happen in the minimal repo I use ssr without the app config warnhandler I get the warn then I try to use the warnhandler to catch the warn I add but I get the error not the warn because in the function warn 1 of vue be the warn will print differently because of the warnhanlder so without warnhandler it be correct with warnhandler it will directly use the args join which lead to the error in my personal ssr program ssr will return 40 node and the client will adaptively render some of the node accord to the screen size so it lead to the warning but I can not fix it because it be not an actually problem it just a method so I decide to filter it so I use warnhandler to filter it and it just can be config in the client not in the server so I code if process env broswer app config warnhandler function warn vm trace filter the problem console warn vue warn warn vm trace then I run it I get I find the question be because in the function warn there be a symbol comment in the args which can not be implicitly convert to stre the code be in I think the function can not simply connect the args by join because type like symbol could not be implicitly convert to string before use join the args should be convert to string explicitly so I code it it actually work I hope the issue should be fix soon it will really help I a lot system info shell system os macos 14 2 cpu 8 arm64 apple m1 memory 155 42 mb 16 00 gb shell 5 9 bin zsh binarie node 18 16 1 nvm version node v18 16 1 bin node npm 9 5 1 nvm version node v18 16 1 bin npm pnpm 8 14 1 nvm version node v18 16 1 bin pnpm browser chrome 121 0 6167 184 safari 17 2 any additional comment no response |
vuejscore | nest v show ignore outer value and component with v show false be show | Bug | vue version 3 4 19 link to minimal reproduction enqnvntu4jaq zwrx0olsedsy7ij6u6qd11pl rymjcqd dwsspbcuiuf yarpuuq0oiudy5pyz2fv2vaqipky2yyndspk5w2mmgfbypbsan7qstellobnylv6ngvvk0mlgycawtlwociykaqpdehudzn5euthbjxehm7a2mkjyynhvfchclqng2yztkwsqarxsn3hrb nfwv3wtxli 6bw42aien3bwugs7oj83betvdpebvgun5q9aj xzhzaweitme a6iykbuztsh393vd ghlk0uvdt6drgkm6hw3r9ksfizpc1kjpo2omxwfyt5kvaaz34vzaer7hjyru 0hdy33wih uerw9wk1ooae32zuou5ndpyyrel p2mq5yk7iuock0jhk0zhioytvvcypfbybuitkhhbdpoyjl9hoa8yfdv17hlyczi1ewzsekrf p05mxgbnwkdianb8tu5z2kntm99ffv9 l6kdtcvzmu1clm autb icsav5utnput5urs6vwvyhomxqoyyoxf6xx7i920ov4zdmw6dxc5wajr3y 9d4o85s81rub3hd yxwy9pzbmn 1iot7u5cypsuzizucmyfnw6vpyjyrem3qnwyid8ct6r 0b1h404xl8 otqudi bjlgiv2xs2ehbocsserwpbqpatpckduwmkzc6npk8htro8puqd1ztrwtwq2wrj9wfzhezymzcyjfspnkexdtu9ayisnu4 step to reproduce open the link the text of the inner component be immediately show in 3 4 15 and 3 4 17 the text be not show what be expect the text should not be show as the most top level v show have a false value what be actually happen the text be show system info shell reproducable at least in firefox 122 0 firefox developer 123 0b4 and chrome 121 0 6167 161 64bit machine I don t think this be relevant for this bug but who know any additional comment no response |
vuejscore | hydration style mismatch | Bug | vue version 3 4 18 link to minimal reproduction ssr enqnuk1vezeq suwl01qdzchhncsvgvuctgaao572ditxk2 zm ubkx574y9jkqbvdzg897mm3mepx rfdl3wgu jciojywcdv62scp4f5dtwya1o7b1cizdefwqsclzigxqerfsjugt ww2beyygntqnt0qjnctar0yw0rv52ammdbtjdcnp1bykguh4szitw2u862uym5q9nlmdw2 qbaoza4oowyovy5rsvqtieeuqmlwnmqlclpamyfyottltrs2cqenymxasxjjrjoyui3fkbmjo9xm9fqmemllbjyklnt9oln w5kpepeosmsfl mslp2rtblq3swpm2saunjlybwxami6xpej8mkrkxdhk85h6gd62nebee8 ip emmsmokvaskehhp wrang8arvv gxyun0djzkej qz4daltxzpxpl0jv2jsm16e9mo dpqhh f h2djcak0agiemr hdc3vn1n9z7ilcphryffycby8wrt wscrenqenmzht4 g 1lulpkuycvr1obsalfwmuinaftqlykahnblblk k wu6oyjn rkikvbbdwqtdtnbpdxifocigjuqki p3tr9kt7avtl 2tl4rcknd4s step to reproduce you get this error when you use a v bind inside the style tag and at the same time assign a value to the style attribute to a nest element if be the main element that have the attribute this error win t occur ssr should be enable what be expect this error should not occur like when it be the main element that have the style attribute what be actually happen you get this error when any element that be not the main element have the style attribute system info no response any additional comment no response |
vuejscore | the bug in the v show directive of v3 4 16 cause the component to not display | Bug | vue version 3 4 16 link to minimal reproduction element plus playground eyjzcmmvqxbwlnz1zsi6ijx0zw1wbgf0zt5cbiagpgvslxnlbgvjdcb2lw1vzgvspvwidmfsdwvciibwbgfjzwhvbgrlcj1cilnlbgvjdfwiihn0ewxlpvwid2lkdgg6idi0mhb4xci xg4gicagpgvslw9wdglvblxuicagicagdi1mb3i9xcjpdgvtigluig9wdglvbnncilxuicagicagomtlet1ciml0zw0udmfsdwvcilxuicagicagomxhymvspvwiaxrlbs5sywjlbfwixg4gicagica6dmfsdwu9xcjpdgvtlnzhbhvlxcjcbiagicagidpkaxnhymxlzd1ciml0zw0uzglzywjszwrcilxuicagic8 xg4gidwvzwwtc2vszwn0plxupc90zw1wbgf0zt5cblxuphnjcmlwdcbsyw5npvwidhnciibzzxr1cd5cbmltcg9ydcb7ihjlzib9igzyb20gj3z1zsdcblxuy29uc3qgdmfsdwugpsbyzwyojycpxg5jb25zdcbvchrpb25zid0gw1xuicb7xg4gicagdmfsdwu6icdpchrpb24xjyxcbiagicbsywjlbdogj09wdglvbjenlfxuicb9lfxuicb7xg4gicagdmfsdwu6icdpchrpb24yjyxcbiagicbsywjlbdogj09wdglvbjinlfxuicagigrpc2fibgvkoib0cnvllfxuicb9lfxuicb7xg4gicagdmfsdwu6icdpchrpb24zjyxcbiagicbsywjlbdogj09wdglvbjmnlfxuicb9lfxuicb7xg4gicagdmfsdwu6icdpchrpb240jyxcbiagicbsywjlbdogj09wdglvbjqnlfxuicb9lfxuicb7xg4gicagdmfsdwu6icdpchrpb241jyxcbiagicbsywjlbdogj09wdglvbjunlfxuicb9lfxuxvxupc9zy3jpchq xg4ilcjpbxbvcnqtbwfwlmpzb24ioij7xg4gifwiaw1wb3j0c1wioib7fvxufsisinrzy29uzmlnlmpzb24ioij7xg4gifwiy29tcglszxjpchrpb25zxci6ihtcbiagicbcinrhcmdldfwioibcikvttmv4dfwilfxuicagifwiann4xci6ifwichjlc2vydmvciixcbiagicbcim1vzhvszvwioibcikvttmv4dfwilfxuicagifwibw9kdwxlumvzb2x1dglvblwioibcikj1bmrszxjciixcbiagicbcinr5cgvzxci6iftcimvszw1lbnqtcgx1cy9nbg9iywwuzc50c1wixsxcbiagicbcimfsbg93sw1wb3j0aw5nvhnfehrlbnnpb25zxci6ihrydwusxg4gicagxcjhbgxvd0pzxci6ihrydwusxg4gicagxcjjagvja0pzxci6ihrydwvcbiagfsxcbiagxcj2dwvdb21wawxlck9wdglvbnncijoge1xuicagifwidgfyz2v0xci6idmum1xuicb9xg59xg4ilcjfbyi6e319 step to reproduce you can test it at the link above choose element plus version 2 5 5 and vue version 3 4 16 after select you will notice that click the el select dropdown do not display anything check the console it s observe that the popup layer be set to display none cause it not to show switch vue version to 3 4 15 restore normal functionality after investigation it s find that the follow two change under v3 4 16 cause this issue I test locally and directly revert these two change in the code under node module runtime dom dist which restore normal functionality besides el select there be many other component that be not display properly such as el container el menu el scrollbar el overlay etc after examine the code it s notice that these component be all implement use render function component use template seem to display correctly l25 diff update el value oldvalue transition if value oldvalue return if value oldvalue el style display el vshowoldkey return if transition if value transition beforeenter el l41 diff indicate that the display of the element be control by v show so we always keep the current display value regardless of the style value thus hand over control to v show if vshowoldkey in el el vshowoldkey style display style display currentdisplay v3 4 16 element plus element plus 2 5 5 vue 3 4 16 el select display none vue 3 4 15 v3 4 16 node module runtime dom dist el select el container el menu el scrollbar el overlay template what be expect display normally what be actually happen not display system info no response any additional comment no response |
vuejscore | bug report 3 4 11 uncaught in promise typeerror can not read property of null reading parentnode | Bug | vue version 3 4 11 link to minimal reproduction step to reproduce error when use navigation what be expect no error navigate to other page what be actually happen vue warn unhandled error during execution of scheduler flush this be likely a vue internal bug please open an issue at at at at uncaught in promise typeerror can not read property of null reading parentnode at parentnode chunk frwrvs7c js v e55eeb5e 9605 30 at reactiveeffect componentupdatefn as fn chunk frwrvs7c js v e55eeb5e 7513 11 at reactiveeffect run chunk frwrvs7c js v e55eeb5e 421 19 at instance update chunk frwrvs7c js v e55eeb5e 7553 17 at callwitherrorhandle chunk frwrvs7c js v e55eeb5e 1634 32 at flushjob chunk frwrvs7c js v e55eeb5e 1841 9 the error stop the execution of the page and do not let you navigate image system info shell system os window 11 10 0 22631 cpu 32 x64 intel r core tm i9 14900kf memory 36 76 gb 63 85 gb binary node 20 10 0 c program file nodejs node exe npm 9 9 2 node module bin npm cmd browser chrome browser 120 0 0 0 any additional comment reproduction page v3 4 10 work reproduction page v3 4 11 not work |
vuejscore | annotation node under the component root will affect fallthrough attribute | Bug | vue version 3 4 10 link to minimal reproduction step to reproduce you only need to create v if and v else structure in the |
vuejscore | crash on update non resolve async component | Bug | vue version 3 4 5 link to minimal reproduction enqvvvtv2jau itheumqignx7yvbvtb1ydnuwrunzq8zoycbxi5sb1oh vuo7tgkpvs7iaqc 3cun9khi7qotw0g02cmlplvghtqpr5moatqitw8f1unkykqcopecmy97mx7uglujvzhgcsu4nd6oqeulwvxggp8glmxr2erjrw2z3tm1eb70sl4j5o0snzobpnl2kccielab5gia kam6ymsjlkk40sggeazswofgwlvalcyhumbowqdhnt0hdnssqdba6arsaicpe2kxuqnp9dwjyhi1cplejva4vxfxufceg5ftzwtyllmx8ak32oflsc6pipbpftyaoy9ccxskr5ck4qhylzeo2s8bxxsqkqzljjkdfmfhokbvvltwcvaqvfgpslbp 0sri0vnvjayujyozxziws7y6nxtwnkfuawnr0spl5r jvarskhe vko3g3zqsxx0ls kkjl0qs6qdeiwdrwhyk7ao75tgdhl2yglghsfklf9rzwiyatd1a0idrczf7qpvadng2ouxg1wwt jv1l3rpce3ghrkoosgs lmrle78 xnf7yn752xenltkvc jn n6bud0bm9a3hosht fu0hsxba5a26vtc0cn uawqpypqnavhflobvrr hxsqx vhoip6lp9svpxb6veqdzr7 t szmjq5y3mnohdfj1 y5c6 lqbudwo4rxvgbkak9mru0xrru6ib5euw15oqgysnoma8riqvpd02cin6g7udcmys9kwt dafdv5gnxfvozisgqtbmwpric684uqpnmttozep8ooo2pccf3xapc66yk9jihxnutfocuccwrpzgfq0rxslqc2m4 d2 7l9vk52 7 7gg4psy8lxx2qf8uurtl0shbuwywi0zecw nz2dnihjy yp7mwsxpb64bzifnjqvl2fzysvjafl8cdrpeiketdwobvfn96n1xhihpajco3butazvnkmxokszhkm1lzfenvk6sk3jlpplfqxcsi rqin4dv6h6svfvmapq8lukhb1elkt3ujh4 zzjiaqfm5tmgxlz2udh dkptcflu0fk8aeg bnk step to reproduce 1 open the playground what be expect the text be aaa data2 and there be no error message what be actually happen the text be aaa datum and an error be show system info no response any additional comment it use to work in preview of pr 7290 the playground of the commit enq9vetv00aq isjx xiiw7plsqvafua4lhrcsicvve43dretxbxsamo 53zxa9jq6cckjmk5 3n4 mhwjxnbntini8weq14y0cjazvrtpc6kcrae1k3uchzqzxlrwdd4958gltwnyg0tkfhacfo1ztlyi2fnldihpbwnsrlpananbkw1pb9zjhie0majgsygeu1hdibkkzghrgma7whb9zq2rxyyvabf9xwvohuwfbslastdmfawg5hx7ibvhheur4kcac8gitazbasaqnacglxerlpfd1wcimnhmbx1bxamrp0bkyfjmsxp4 vhqoftas65inbfbrsann7syy1zvmkuouqxtcbvfxsri9lucmtngejzytmsn31l9vaqqmovgo3sp0 azmkgkybigzkesairmxjjlsdz8tlflgqlik57zqk 0fi28o1sirqq1w6wfs1oyt juvqi6sdkou0bxbni6npcgxfzb61fhr5bmbzzifbk1rfg8npslk0d2viilzvcvfr6yxqcrr06wdcl2f0j rj6rlolgafig4h6m2gqq0ab765 4jp9n4ba5m3fxn w jnjr61gl3bu1bkbhvg59b cashvd7rmyddgwhnwaduijx fhfv7al 1voj7txskhwfttfw8u qqge7w17yetpfdhxw9hjhlo81l57r5gt twbjrtnh5zjwqxewik5wlnfw87hjm5ybkzby09opdxoxvmwjlkgddck6orh7a8unki8ull4zx ad5ueynxlblzkforitkvptaikezw6hivtrobebzpu1 ospnsecmfx9gu7vjpanvcdgxxgrynhskggioiqdbkxnv1zu 3cfvzedlfjgtl3vrw4a kvucze2bkq3hteo2xnoqzwexfxmxehzy99uowuv nb7ofe4 mf5ez8e71arebwki hrwrf37dw aws2gld show the result correctly probably it be also regress by this commit |
vuejscore | hydration mismatch when use v show and custom style attribute | Bug | vue version 3 4 5 link to minimal reproduction step to reproduce use test in your component and ssr it check the console for hydration error what be expect no hydration error what be actually happen vue warn hydration style mismatch on render on server style display none width auto expect on client style width auto the server output it actually correct though system info no response any additional comment possibly relate |
vuejscore | the job sort in the activepostflushcbs be unstable | Bug | vue version 3 4 5 link to minimal reproduction step to reproduce open the console and you can see similar result 58e67da1 cc24 4f6e 8028 a00075b9fff4 what be expect same output order what be actually happen different output order system info no response any additional comment the new job queue have no be sort when nest flushpostflushcb call image |
vuejscore | suspense out in transition rendere component out of order | Bug | vue version since 3 3 10 3 4 5 link to minimal reproduction enqnu01v2zam suel06bxm6q7uilxdehh 2wdm2pvrg2k6ivjuginrzb vsokd bip5spvgrj4 sovlmtnz3mbtj1nvwgakh1jmruonwaeuwbrespnsre5wpyqkbmfvdqsqk9eupslvr5qjufmimbhcwu4llig1enw6zw8vkuqjsqkcpbiaqaoxpxy71unify9fke9ao1wtcmfggbmd991vrkeqxfd11qsaqsr6snvd5hmxmqfrxikxw 6xalgqarzfybw4iwymrqo4apqzy6lgbae5 akk2uk6q0apu1ekstey1wdkbvjc 0h2nhok4adpb twgj nxmqq v3jonehlyoea1jr9v6gicue43yvmcvmokz9qpvlbw0hljsbs7zhqp44bbalhgqqxc4k35hvdb8sydf wfronefwymrsctodq0zv0v5mfdmqy0y6qmkspwx0osepxc8ythdqwwjudcxbp a6x36ef a07k0m6ltcmqgw9ftbmisbcscyu8cq7o hksb2i9xh w4hjmik3edrwjnt2wvfdd6xk7yerkyiw9xjfax xyzliuclp60yxruepepsppfyznr mtnx2ikslo0a315psmvvmrjs6hjn07ejj6pvdy0xkhkfat8kz7hlai6pbi ajbc9ox63pjv5q77uzoxs2hrw lrlynfnir52qao mx9opnegx qwy2c4voul1euuxf dp7jxo9ntiuhy0p1v2grspbx9 4sv 7w 52xryu4b hn6j07lzgmpatacaln2uf9 t cbswavhobl jn8tukc80ubhywz6 vzp6qe4 km xd3pwbeincwg step to reproduce 1 click on the button 2 see that component be not replace but render below all the other component what be expect the component should be replace in place when the transition be trigger what be actually happen the component be render below out of order system info shell system os macos 13 5 1 cpu 12 arm64 apple m2 max memory 110 55 mb 32 00 gb shell 5 9 bin zsh binarie node 20 9 0 usr local bin node yarn 1 22 19 opt homebrew bin yarn npm 9 8 0 opt homebrew bin npm pnpm 8 5 0 library pnpm pnpm bun 1 0 21 opt homebrew bin bun browser chrome 119 0 6045 105 safari 16 6 repro in sfc playground use macos firefox dev edition 122 0b3 any additional comment as a workaround wrap a div around the transition work fine and replace the component as expect use in out without a wrapper div also work possibly relate issue and prs |
vuejscore | in astro ssg scope slot be break the build | Bug | vue version 3 4 3 link to minimal reproduction step to reproduce open the code sandbox and let run the build task what be expect I believe it should compile properly what be actually happen it be return the follow message 20 08 23 error node scopeids foreach be not a function stack trace at object enter workspace sandbox node modules vue compiler core dist compiler core cjs js 1520 25 system info shell system os macos 14 2 1 cpu 10 arm64 apple m1 max memory 624 19 mb 32 00 gb shell 5 9 bin zsh binarie node 18 17 1 library cache fnm multishell 54301 1704309312457 bin node yarn 1 22 21 library cache fnm multishell 54301 1704309312457 bin yarn npm 9 6 7 library cache fnm multishell 54301 1704309312457 bin npm pnpm 8 14 0 library cache fnm multishell 54301 1704309312457 bin pnpm browser chrome 120 0 6099 129 safari 17 2 1 npmpackage vue 3 4 4 3 4 4 any additional comment it seem to be link to 9867 it do not fail on stackblitz I can continue dig into it |
vuejscore | error when access destructure prop inside definemodel s getter setter | Bug | vue version 3 4 3 link to minimal reproduction enqnustu20am bvil3gawdq4j9v5teuolza2ahvr9qbijlppirvguo4bq 9eau0orvtatxi5fmwmd2vexfisezsvwaagxrrikh0ex9pq3bpj1lxyamgcjyetuhtte3ewwdm0eo8ibznetjyqywruqvbyewwxs9pxll7au9cinxpvxmi2hwgafcrsfpybacsjpmnbjxz7dhwcnoi4er7oxu8wtl wo97k0pwz18xamu qwdymqcorj7r7qnvuz0usud1jbm2dsexvwtytazuycmsuckwk2jvxwlzyt i6nlehu1our4pf2bokh kcuze 4 cukhwinznifk2pytxynjfazot xxvudrj6cpptftbi0qcmsfl7793qyjimdnf55e9rnj7nf2tq78pth5wt7nhs0jxg8 mp ce02wm6zczmdvrlzxrdhxz95snu9h8c9un0fn gv4cfmqxfjxx3zw97apx2qv1 m z5f2nhqa7recfj6fjuszw7k nypd q kj3uswmf4efxo4nkg step to reproduce vue what be expect should compile component without error what be actually happen compiler crash with error error can not split a chunk that have already be edit 6 13 definemodel get return ismulti system info no response any additional comment no response |
vuejscore | import name export | Bug | vue version 3 3 11 link to minimal reproduction step to reproduce 1 export a component from an index ts file with a name export 2 import that component in another component use import as x from some index file ts 3 use the component ts what be expect the component to render what be actually happen app vue 7 uncaught typeerror can not read property of undefined read i d at proxy sfc render app vue 7 24 at rendercomponentroot runtime core esm bundler js 870 16 at reactiveeffect componentupdatefn as fn runtime core esm bundler js 5972 46 at reactiveeffect run reactivity esm bundler js 170 19 at instance update runtime core esm bundler js 6103 16 at setuprendereffect runtime core esm bundler js 6113 5 at mountcomponent runtime core esm bundler js 5881 7 at processcomponent runtime core esm bundler js 5835 9 at patch runtime core esm bundler js 5307 11 at render2 runtime core esm bundler js 6623 7 system info no response any additional comment no response |
vuejscore | ssr slot inside transitiongroup result in hydration mismatch | Bug | vue version 3 2 43 3 3 0 3 4 0 link to minimal reproduction ssr enqnu8fowzam rwtc5dtfeigbqkqqnaabjo45fj1xhtokyhxt6fp 46tbnqb3cspjd z34v7uhq31o5mdyolkfrckuvgkrp7lbwqrxeehy6zfh1mnanhdjssz6hp9ljjksofngns2gxak1jgdx1 su13mrsilmchwtpwgsgfankt4ta8x6xyuh5phame5jwlauxrjpis qbwhhqone1rgikyg flyao0ajugeigvfgokk4bddncpnwgwzk91vunzmoqf8lnpe ta fsovywsxc478van3dth2vt49jymwxsqa0e n3qqitgnn5q 0diwpchnbvntvdhgx0txarejwfzvzv4ua qahgzqvkz8q6f 6rehjswrq49uhll8yps5aqmf79 fcchvv2btjk3f7cpgg3ptncfjs7tt9irtb gi28eyikwlsb9fepkw15ckrgnzfflscgbujly9s3s oo99uq94iwfidzjxs iysrfw6yz i7x7rzqvv1jm1eyktrb8zqisdqj2 d0p2prhguddor7co7at745a qcpg1wp step to reproduce toggle ssr on and off to see hydration mismatch message what be expect not to contain hydration mismatch what be actually happen html render on the server return component s wrap in comment rather then actual wrapper component this be why hydration contain mismatch system info no response any additional comment no response |
vuejscore | Bug | vue version 3 4 0 beta 4 link to minimal reproduction enqvu8tu2zaq bwcz4sq4jxcn0hbpeb7ais0r14ucamw5qvllwmg8l93sdmpzarbexk5mxzndpfp8mnkajec3mgtgu ui7juqydtu9zmhm0i4bowfncsspyia43psj5g3sgvg30m93zqjzkgfn7wqqgt itdya etkywgajklkwzrn49k3wcedyner9a s x6k 5n2pafktiqpuqmsxjdocgcb4 td32pp6bftrji7zb4a3kkmbi8ej9mkmhm3penxtv58ikg3dbb7ee4r8aqoylcxd5wvj6x5 o w dtdqxc pcoaubdvvfjfocpyapqj yzl7qjtypm17e iyawd3qajqg5jvr5jw4hjiemhm9fdrdahenxdanbpojc00rxvk39xhfokavcjowhawqtgq0wodeaxgiejfljwde8xggwnhpbiy5vsypu3wcujryiobaqdtevpvbd8zs2vxa31es82efhermx0vtetbnwivx2iu9xg9n6ja3hrpld8vzpw3s8chxnbyxv3wmrtiop3k3eupl54soz6qnj25 5q5 afjoket step to reproduce open comp vue component select vue 3 4 0 beta 4 and make some edit add a space for example to trigger the compiler then if you replace generic t extend record with generic t extend object the problem disappear remove import foo from foo vue make the error to disappear too what be expect generic should accept any extend what be actually happen generic no long accept to extend another generic type contain a character syntaxerror vue compiler sfc unterminated string constant 1 0 src comp vue 1 at constructor at parser raise at object unterminate at readstringcontent at parser readstre system info shell system os macos 14 0 cpu 10 arm64 apple m2 pro memory 105 67 mb 16 00 gb shell 3 6 1 opt homebrew bin fish binary node 21 4 0 opt homebrew bin node yarn 1 22 21 opt homebrew bin yarn npm 10 2 4 opt homebrew bin npm pnpm 8 5 1 library pnpm pnpm bun 1 0 13 opt homebrew bin bun browser brave browser 120 1 61 104 chrome 120 0 6099 129 npmpackage vue 3 4 0 beta 4 3 4 0 beta 4 any additional comment I try all version of 3 4 and the problem seem to have appear in 3 4 0 alpha 2 use the version selector on top right choose alpha 1 make some edit to recompile add a space anywhere for example problem go choose alpha 2 make some edit problem be back | |
vuejscore | wrong prop parser with generic | Bug | vue version 3 3 13 link to minimal reproduction step to reproduce 1 create some base prop type with generic and 2 prop type extend that type with proper generic export interface ibaseforminput label string require boolean readonly boolean disabled boolean description string value t export interface iformtextinput extend ibaseforminput ibaseforminputwithplaceholder ibaseforminputwithautocomplete export interface iformcheckboxinput extend ibaseforminput ibaseforminputwithautocomplete confirm header string message string accept string reject string 2 create 2 component whose prop extend iformtextinput first component and iformcheckboxinput second component 3 render that component in app with provide generic prop value in example what be expect component be render without error what be actually happen component be render with error sometimes first component textinput render wrong default value pass empty string but render true console say it have boolean true as input prop sometimes first component render correctly but second component checkbox render with warning say boolean be pass as prop but string be expect but generic be boolean system info shell system os macos 14 1 2 cpu 8 x64 intel r core tm i7 8557u cpu 1 70ghz memory 168 85 mb 16 00 gb shell 5 9 bin zsh binarie node 20 9 0 nvm version node v20 9 0 bin node yarn 1 22 19 usr local bin yarn npm 10 1 0 nvm version node v20 9 0 bin npm browser chrome 120 0 6099 109 safari 17 1 2 safari technology preview 17 4 npmpackage vue 3 3 13 3 3 13 any additional comment version 3 3 9 work as expect |
vuejscore | vue 3 4 alpha 4 compiler break nuxt fixture test | Bug | vue version 3 4 alpha 4 link to minimal reproduction step to reproduce start the fixture from nuxt with pnpm nuxi dev test fixture basic go to localhost 3000 island see property t be access during render but be not define on instance in log nuxt fixture test don t pass with pnpm test what be expect not have any error or warn in the console fixture test should also pass what be actually happen the compile result of the sfc have a json stringify setup vfortoarray fall back map t index t ctx t source json stringify vfortoarray fall back map t index t t t shouldn t be prefix with ctx investigation do a nuxt hot reload seem to fix it trigger 5 to 6 time hmr seem to fix it some cache we try to reproduce it on the sfc playground unsuccessfully debug the sfc file transformation the issue seem to be come from vue compiler sfc through vitejs plugin vue code pass to transformmain be always the same the descriptor for the sfc file be not identical at first loading ctx prefix and at nuxt hot reload or hmr look for the vue core commit seem to be the source of this bug additionnal infos sfc source vue vite plugin vue result ts import withasynccontext as withasynccontext definecomponent as definecomponent from vue import vfortoarray as vfortoarray from app component util import getresponseheader from h3 const sfc main pure definecomponent name longasynccomponent prop count type number require true async setup prop expose expose expose let temp restore const evt userequestevent const header getresponseheader evt const datum temp restore withasynccontext usefetch api very long request temp await temp restore temp const return evt header datum get vfortoarray return vfortoarray object defineproperty return isscriptsetup enumerable false value true return return import mergeprop as mergeprop from vue import ssrrenderstyle as ssrrenderstyle ssrrenderattr as ssrrenderattr ssrrenderattrs as ssrrenderattrs ssrinterpolate as ssrinterpolate ssrrenderlist as ssrrenderlist from vue server renderer function sfc ssrrender ctx push parent attrs prop setup datum option push if prop count 2 push count be above 2 else push push ssrinterpolate setup datum ssrinterpolate prop count ssrinterpolate setup header custom head hello world t ctx t ssrrenderlist 3 t index push fallback slot index ssrinterpolate index push t ctx t ssrrenderlist fall back t index push ssrinterpolate t slot index ssrinterpolate index wonderful fallback push import usessrcontext as vite usessrcontext from vue const sfc setup sfc main setup sfc main setup prop ctx const ssrcontext vite usessrcontext ssrcontext module ssrcontext module pure new set add component island longasynccomponent vue return sfc setup sfc setup prop ctx void 0 import export sfc from 0plugin vue export helper export default pure export sfc sfc main ssrrender sfc ssrrender file g repo nuxt test fixture basic component island longasynccomponent vue what it should be ts import withasynccontext as withasynccontext definecomponent as definecomponent from vue import vfortoarray as vfortoarray from app component util import getresponseheader from h3 const sfc main pure definecomponent name longasynccomponent prop count type number require true async setup prop expose expose expose let temp restore const evt userequestevent const header getresponseheader evt const datum temp restore withasynccontext usefetch api very long request temp await temp restore temp const return evt header datum get vfortoarray return vfortoarray object defineproperty return isscriptsetup enumerable false value true return return import mergeprop as mergeprop from vue import ssrrenderstyle as ssrrenderstyle ssrrenderattr as ssrrenderattr ssrrenderattrs as ssrrenderattrs ssrinterpolate as ssrinterpolate ssrrenderlist as ssrrenderlist from vue server renderer function sfc ssrrender ctx push parent attrs prop setup datum option push if prop count 2 push count be above 2 else push push ssrinterpolate setup datum ssrinterpolate prop count ssrinterpolate setup header custom head hello world t ssrrenderlist 3 t index push fallback slot index ssrinterpolate index push t ssrrenderlist fall back t index push ssrinterpolate t slot index ssrinterpolate index wonderful fallback push import usessrcontext as vite usessrcontext from vue const sfc setup sfc main setup sfc main setup prop ctx const ssrcontext vite usessrcontext ssrcontext module ssrcontext module pure new set add component island longasynccomponent vue return sfc setup sfc setup prop ctx void 0 import export sfc from 0plugin vue export helper export default pure export sfc sfc main ssrrender sfc ssrrender file g repo nuxt test fixture basic component island longasynccomponent vue system info no response any additional comment it be really strange that trigger hmr multiple time around 5 time seem to correctly compile the sfc template a reload of nuxt also fix it also not every map t index be prefix with ctx cc danielroe |
vuejscore | nest element with key event modifier do not call listener function | Bug | vue version 3 3 10 link to minimal reproduction step to reproduce sh work npm I vit run fail npm I vit run what be expect the test should pass successfully manual test click on the button to focus it press y key should call remove function which log call but it not happen expect press x log call press y log call actual press x log call twice press y do nothing what be actually happen it require an element and its parent with an event listener to the same method system info no response any additional comment no response |
vuejscore | type for class extend map or set lose method property add in those class after unwrap | Bug | reproduction enp9uu1vwjam stwloceyofbv5a2xggt9qftx1yq1psyninyuzcq vc56vo4teg5xm 287nfxx61tlqplgwzluythvh0xopizbxhzfnotlzwjvbgqqcg88lvls7pd4aedky1mcoc2qoxxbyitxz23jrvvoya8ojqlhbcv ms4ihcqpkibetmlasbbcjz3kiyxfqsyd2x9ihrsuuandiim2n8ppyv45wujj6vy eljxuvqnu2graihshw2giro6qiicvrdtt1a3cycsv eqhvs1uocsrti1vssujtoa6sk1ws7halcfaortcczbt2nwnmlb2x4ywnxvnlxjzxsoogvdhi8fmpfrkxghh2ydciazgzkedyu6eb0vuvn7rwtbjrprdufsf5ivyjhzqozu9elit7pi6qfy6ok0xfdh9mtonsqwg0knzzrt7v7qx lbto1qoxrp8f6anvqq step to reproduce the bug 1 set vue version to 3 3 10 or above 2 set vue version to 3 3 9 expect behavior it should still be work with vue 3 3 10 actual behavior it will throw the follow error when use vue 3 3 10 property hello do not exist on type map ts 2339 |
vuejscore | transition doesn t work well with definemodel | Bug | vue version 3 4 0 beta 2 link to minimal reproduction step to reproduce 1 click on toggle model value 2 check if corresponding value be change it do not 3 click on toggle local value 4 check if corresponding value be change it do 5 click on toggle explicit value 6 check if corresponding value be change it do what be expect when I click on toggle model value it be expect that the value be update inside transition component what be actually happen value inside transition of modelvalue which be define with definemodel be not reactive system info shell system os linux 5 0 undefined cpu 8 x64 intel r core tm i9 9880h cpu 2 30ghz memory 0 byte 0 byte shell 1 0 bin jsh binary node 18 18 0 usr local bin node yarn 1 22 19 usr local bin yarn npm 9 4 2 usr local bin npm pnpm 8 10 5 usr local bin pnpm npmpackage vue 3 4 0 beta 2 3 4 0 beta 2 any additional comment this issue be not happen on stable channel 3 3 x |
vuejscore | break click event listener | Bug | vue version 3 3 11 link to minimal reproduction step to reproduce it seem that the click event listener on an element inside isn t be properly handle step to reproduce 1 open the reproduction 2 click on the semi transparent fullscreen div 3 nothing happen even though it should have set its visibility to false 1 remove appear from the component in fullscreenbackground vue 2 repeat the same step now the click be properly handle what be expect the click event should be handle the same way as it be handle without appear what be actually happen most of the time the click event doesn t fire though there be time where I get it to fire after click for a while system info no response any additional comment this seem to only be an issue when use vue ssr I couldn t reproduce it in client side vue |
vuejscore | custom property from css v bind be not re add when inline style be patch | Bug | vue version 3 3 11 link to minimal reproduction enqnu1fp2zaq itwxlqkjlbhluu7bgxntbtmsl1fmtl4ugyobdlokkr633e2s0k7hnbe7lvv7rv77rjjpmmd9r0kevly2ndtiaxx6xkpeauvcwrdddrksxqjwjjc6kiupayvti4wbqulaezmhjrukmhh5mol vn5zc 59fff 4ukxmkbokgmmqab8owi0qb giearg 3jzj7fusccstpy0h8liky4dmbr6km7mrcoji5kttjjouarwjjhdlmvi24nbk1gep7l4mz0c0x9qr8edvhlx0d19qbhbcc wnxnkkkutep0w7hfgnomgtoygdgbtpqari3efhqgwvykirgytndc0dojspahmq bttlagm9sdhev6hj wsnstraenakjcue xxllxcginezjtjj nnszne82tsrixi20rnd1bjxf1amo5c9gyywmn3oyl499lcuectjmlnzmyxkdw3mqshjw6pqueudnjx1timwoxz9lznp2ixnyn7rnynl0a9wjbznoohqnkzdigo jpct idmdes34udldake gcm v6vgilwrjcbcy4asjzwrvai7axgvh8c84ukgsqj1 czy x0z9r3ud6 y7 06nvxtqkhsiicrzapcdf cxsea73tnq1gndtp4j mglo6frzhcpunvhwupckhayzbolle 7mxagbtptyxv9woefbji rutv5slcu9v3p4fteh3da step to reproduce click rerender button what be expect the custom property of v bind remain on the div element the ul have two column when the component be re render what be actually happen when the component be re render the custom property of v bind be not add to the div element again the ul have only one column system info no response any additional comment no response |
vuejscore | v show do not work when use on a component that be slot into a parent component with custom render function | Bug | vue version 3 3 4 link to minimal reproduction step to reproduce the link stackblitz have a component that have a custom render function that just render its default slot it then have a component that render a text I should not show the app vue then use these two component as below vue what be expect the child component should not be render on ssr render html the text I should not show should not be display at all in any stage of the page load what be actually happen there be a flash of text I should not show which be remove when hydration kick in this do not happen when use v show on a native element instead of a custom component system info shell system os linux 5 0 undefined cpu 8 x64 intel r core tm i9 9880h cpu 2 30ghz memory 0 byte 0 byte shell 1 0 bin jsh binary node 18 18 0 usr local bin node yarn 1 22 19 usr local bin yarn npm 9 4 2 usr local bin npm pnpm 8 10 5 usr local bin pnpm npmpackage vue 3 3 8 3 3 11 any additional comment no response |
vuejscore | type of ref for map with generic in value be abnormal | null | vue version 3 3 10 link to minimal reproduction enp9u8lu2zaq zubl5ebv0asmyob6ojda6qtgvdk abky5ujrbjcfaeg r1duryvjignszztzzufr zfqbrzydkwm0pzzcggdqqauuzmbbomyitc8fzjbeeigrftsrbkwayhh62wlvxr nxnqhtcviievwy1zofycabezybc w 11iuibdedyzuxu0l0pmtrrgw5foamptjsyr5ajjmyxulhlkusyapd 1irlbfibd4dsfmadd5iqgroeq2n15yeydnfrtelhednizfuqxugzclp9szea6ztnb3ls7uyczg 4ytjjpt0k wyrpyjywcs yokvdmzt96g7tb698kk vbdv1optfcbixfu 2cwdnajvna ckwfinc wiifysuvvt9tveeo olqi8ki3lkkesfx08u8rkejktjdxgqe7xilrik9xvsinyoem1civ e84qrupea0tani oezuho0ysrybfvdfekcygvehqp4ortj4tmroftek6dl9abgijafquanhrqpr8pexvkcjwej9yygp74fpnklq0g4ypnszinnaf px1u sx nfhrjqo0f86vfg9s ln9dkis7jaxgzdpi57ugs9rhmdik2wp19i7 0ry8jhqlkvh21omzzzaaniialw8 8udns7gvtwvi wpjhzsycz5jdpvqre20r36b7y9wvelsrszyyfgyu1geafi34f8wuunfpij9qvc2vt2tkev ay cctu step to reproduce 1 create ref with map that use generic const reactivemap ref new map 2 try to assign value from crated map in other place that expect this generic const test t reactivemap value get 1 you can check typescript error on line 14 in app vue file in reproduction link what be expect code work without any typescript error what be actually happen get error argument of type unwraprefsimple be not assignable to parameter of type t type unwraprefsimple be not assignable to type t t could be instantiate with an arbitrary type which could be unrelated to unwraprefsimple system info no response any additional comment this issue happen on 3 3 10 version and work well on 3 3 9 I may assume that issue relate to this change diff 81475b10580b705fb8421b8c430ac63220938646c0e09141be79c85b0ea392ffr499 that be include in late release |
vuejscore | since last update suspense with routerview act weird | Bug | vue version 3 3 10 link to minimal reproduction step to reproduce navigate between viewa and viewb what be expect html element suppose to keep same order navigation routerview footer after navigate between view what be actually happen html element be render in wrong order navigation footer routerview after navigate between sync viewa and async viewb view system info no response any additional comment run into an issue after update vue to 3 3 10 look like it s relate relate to late 3 3 10 release change and be most likely not relate to vue router itself but rather to async component issue persist even if I toggle between component programatically without routerview remove timeout property from suspense give weird delay but footer stay in place wrap suspense in to div make footer to stay in correct order |
vuejscore | width and height attrs problem | Bug | vue version 3 3 10 link to minimal reproduction see below step to reproduce I be use cunstom web component extjs web component inside vue sfc template width and height be pass as null I m vue v3 3 9 work without error what be expect see above what be actually happen see above system info shell see above any additional comment see above |
vuejscore | fix reactivity fix error when use proxy on reactive array | Bug | close 9742 different implementation |
vuejscore | fix reactivity infinite loop when push a variable to a custom proxy of reactive array | Bug | fix 9742 when user add a proxy to a reactive array and use mothed of array such as push pop shift unshift include indexof lastindexof splice the result of toraw proxy will always return proxy and infinitely trigger toraw because receiver isn t the origin proxy create by vue of target so I think when we use the above method it should skip the comparsion between receiver and the origin proxy create by vue of target js create a reactive array const originalarray reactive create a proxy around the reactive array const proxyarray new proxy originalarray push element to the proxy array proxyarray push 1 this will trigger toraw infinitely |
vuejscore | can not push to a reactive array that be wrap in a proxy | Bug | vue version 3 3 9 link to minimal reproduction enp9uktpwzam itwlgxp6gtcxkociqmcyajuhenvtbdikyhxtqgq x0nzsvp3rj d3 o04pz54plrdevj6hyyheepojopfgns56gby9lrwqj0mgltw3smx vwbppjhoymuoi5caqvs fpamscqtwq1qzup nipxuwaphp 1ffnnv1 st9e8ay3wh0 xabtdg6ten rwagxtt20wj2ghta2osufdachm 02 7d24fo75o4mk 1k87d1tdqux0lyedzt9y bmt5fcpck8hozh8emak0n rvyifcfsnozp tzbypugf96uanqy9zafcmnadjduuqydfbglsadamv5uxbwga3h rtqauls2cuqjv3wk2fokkwqkyaxwdnwda qjjjf1kkx5o 4a1qkmxdwjh1yiffumsl8j9fdl q2u bwfg scnbn3ghfi88ausadd8ni59hdetnuvfyfv7yfcrgln2ayvgizml ls8kec7rh9ihtuhgwdnj3opgatiaqt step to reproduce wrap a reactive in a proxy to allow for customize trap etc generally work however if I wrap an array and then try to push onto the array I get a maximum call stack error the reproduction have just a basic proxy with an empty handler for demonstration purpose in actual use the handler would have some trap define what be expect able to push to array what be actually happen maximum call stack error system info no response any additional comment no response |
vuejscore | typeerror can t convert symbol to string bug or limitation | Bug | vue version 3 3 9 link to minimal reproduction step to reproduce click in the button click I to set a new map item what be expect render something like symbol as the map key what be actually happen when I try to set a new map item with a symbol key the template can not render it throw a typerror in console can t convert symbol to string I could not find any information about this limitation in the documentation this be the reason why I m open this issue system info shell system os window 11 10 0 22621 cpu 8 x64 11th gen intel r core tm i5 1135g7 2 40ghz memory 2 36 gb 15 73 gb binary node 18 18 2 c program file nodejs node exe yarn 1 22 21 c program file nodejs yarn cmd npm 9 8 1 c program file nodejs npm cmd pnpm 8 11 0 appdata local pnpm pnpm exe any additional comment no response |
vuejscore | it can not invoke class constructor accurately when use external class | Duplicate | vue version 3 3 4 link to minimal reproduction enqnu01v00aq svdxpjija2qnejabajkwaeqihhzi7hhybb7pd1xeht5vzo7bli3astj63lvz968pz2kt94xuw7fqixjhzqnieidv5nwge8cwrecttbdg5ybcvmnz2g9fkuosmubpbqupzbw2trzsgdibm7t7enkpwrt4iclunk1mb1jnlaznslnoz0qg2dwlbaat0wsfmx6npf6azfliiwllqmn1xuhnwgw22ty1vrvj7dstfole1hpzzmp7o7hplzvl x2euaq6zuc3dy4bjxzgwdi6n7uka7esnjcvl54im6yk1mwfaj4vcugnnxyi qvxzbix0vz1o3la9xf7ujhkurrtbliwhk6s8rgvhfmdvpcfk lrkualwumzv4zuh3eupjggu4kxdvovsnidsm8ihsdmpzv7itr4 kx0asnaxyazgn07axfdrvvmwtfame80hg 5tls38qdnh mdcodhjepd5i fih km8ddt9czivjfankmyqbvj 2yc88pkmcqadfsril bxje53senae9fzhmwpefnthxyzspvv8f5aaonpqsq0u5h5oy 1p1z lstuj1w8prm2ea 5dtxyvp0mqhuvizciif38be4vgiphuxot b9pn170vwepfknc step to reproduce 1 press f12 for develop tool 2 click tag to invoke event callback 3 then dev tool say typeerror class constructor can not be invoke without new what be expect invoke constructor with new what be actually happen it invoke constructor without new system info no response any additional comment no response |
vuejscore | fix runtime core fix errorhandler cause an infinite loop during execution | Bug | fix 9574 in errorhandler if you modify the reactive variable it will trigger the side effect of the render function cause an infinite loop I don t know if this be as expect because I find that warnhandler and onerrorcapture call pausetracke to suspend the trace but errorhandler do not so I add pausetracke here as well |
vuejscore | infinite loop when trigger ref getter then setter in appconfig errorhandler | Bug | vue version commit 2c0414f late at time of write link to minimal reproduction enp9usfoizem rurf1qpsg cwedarzcwlryqcmybdmbtdgsskhhkvkp5d5wmfbaikyfe7 n52c4gfnsvdwnfitinvwg9qurk lzztvmueaywrvqlendspy2kbyulclibetbbdxde6ue lfw2coxdd2cznv3x1migbe262xxecf vznopvv85s9itzifnu5uyggt odngylhzhm7oyvawojc7brky2ohohe vgbtlseus7ps2ah9nzr5sxbriqax5btpckqn1cq3dsmnby74tsuzz01yn4i6tjm04e53wa4mxczx8y nbvrw z0m2gcmetpftshmy cdsvnge aiybtjlnyxjzh0qsraux9ufo7o8ldk2epxrfmt1rj21xeajk2kggwn 7vlfivfiya1m8arb6umb gpsc0yjm4arww6vogckay9pgi urngph8do1ckw wfwfqmzkxucah9sgc8hxnf7wf4wt s xvsenr41ly1m5lj4svdfwv3q rvdy3lc8nj7ynwbhxb3ia step to reproduce upon open the minimal reproduction link the playground should immediately show the follow error maximum recursive update exceed in component this mean you have a reactive effect that be mutate its own dependency and thus recursively trigger itself possible source include component template render function update hook or watcher source function what be expect no error should occur what be actually happen it seem that trigger the ref s getter before the setter inside of config errorhandler cause an infinite loop to occur however if the getter be place after the setter the no such infinite loop be enter system info no response any additional comment the ref can be a global ref not instantiate inside of the component and it seem like the bug still occur in the minimal reproduction playground the ref be create inside |
vuejscore | unable to use new decorator in vue with vite and babel | Bug | vue version 3 3 8 link to minimal reproduction step to reproduce build the give reproduction use npm run build and see this error error during build error vue compiler sfc can not use the decorator and decorator legacy plugin together even though in vite config ts the vue plugin s config list the decorator babel plugin it be not be consider in the follow code vue script babelparserplugin decorator the follow code seem to be the cause of it l167 since it be never check if user have pass the decorator plugin before add the decorator legacy one both the plugin end up be push in the array what be expect no error on build what be actually happen error on build system info shell system os window 10 10 0 19044 cpu 20 x64 12th gen intel r core tm i7 12800h binary node 18 15 0 portable app nvm version node v18 15 0 bin node exe npm 9 5 0 portable app nvm version node v18 15 0 bin npm cmd any additional comment it seem like the plugin array check to see if it include decorator be a mistake since that will always come out to be true it should check in the userplugin array instead |
vuejscore | fix correctly resolve type from relative path on window | Bug | close 8671 close dirname be the safe way to get a directory name from a path string as for this specific bug it s because path posix join anywindowspathusingbackslashe return I m not sure whether there will be unexpected regression if I modify the joinpaths utility so I change the small possible bit of code to fix this |
vuejscore | ssr rendering of select input with slot be break | Bug | vue version 3 3 5 link to minimal reproduction enqnvmlu2zaq rvcf6eajsinejguig2rqwp0qv30uvwgsgobquqs5ehxiejfoyqlm3gtipbfndflm v5sn5rnfudjkskt5urgpkf7prviuwrlue2mambnrknus1bkoviak2hgqpvpe5wgjme2vxecna sknrmjsm6q8ahzls0mu w0yv88wb2u95iywhx0d0yebvt4vfiwvoa2uisw evjclar0yy3fnv8nwwnecc06adwhqkjz7pm1vdc1lktyokblwlhceci0xq1ranzdbivf5kfogszk2ypdj9bry7oos9cnchg8gxey8fayypgzdppwfukmwsrh32py6u7dk0q4gf1vmabvymw9xnhq6exfjdlhbfedvlsmmuho9ysqgl7rl1 tgtsdrtjdwqr2 yc6yd7wwfmnzbrzn74x6sgaoszesozje2vrgugoybgpmtwvpwulsj9b 5v31szajdquthctgbe9guqlwiwzm2n j0zrnox4 eruadg69vduo jxhv7f70nm3a55z1d wzgsy4jv1f9pubnixdc20hmfa72bv04vjcg4folkt7cjps731g6zz 2fv9gjszk05on4a3 t v4 mlrr p0rsjkz7i9ym gvmuxia y6yd0mungyhhszoddfhxw4qt0rdnkut8sjbr0c ccucfie9y46au59yo5hpmpjrjnifzrjbxh7joplw step to reproduce 1 click the selectinput vue tab 2 click the ssr tab 3 see compile error what be expect the component should compile what be actually happen a compile error system info no response any additional comment this have be compile fine early |
vuejscore | memory leak due to key dependency never be remove | Bug | vue version 3 3 4 link to minimal reproduction enqnu01v2zam suclnwqxm7qndk06fbk0ah7wlqjl5pmx psszdkjedg z5kqh3xdyokmestj3ypnh2ix7ro9y3qnd1ybor2xijr9v1ucikarywjj2kacsf2secrxjadc7zalivwrzpsgtwqk6xxdeot movtkequr1yewkh8gqumc0clmk4amvelckqbvwzykisgbm9iyfvjnhcrrpndqsb7n39xspdkhppbzzc3ec1iz9wenccz2fniv6gvlrinvnoxjuajgvv9np8upngd1mskg81mnnqitlfkzaodmpdbcjw pi27wlsyxx 5j1 t teb6mifdjmbomce9rdnl2utxs8cvi1dugdrcsl26bnvehfg5jnyylwjrq3mp3yco8rpgknjmcmra3x4fnzotldo bwc u c 9kevs nvwxyfac5hwkomr24gn4 yaj2kowuuvbi qd4 g wqm69xgj72soczy9wqe1jwgihd3 s9uha2r4pl9qju4dpkw7wwzutn vep9chdwelu4w ybjhejlhghhdbdmi2mo5bddzxgujaqxuym9scs6tusnuezyzxa7rwblx8h4z089ziawbu1owzfkvuqeclbyzne7zw7jn0oaswpixfix2kjamnote0a9d6f4d9x1umq step to reproduce inside the callback of a reactivity hook e g watcheffect compute read a reactive value from a key base data structure e g set have key map get key object key then allow it to rerun an arbitrarily large number of time with different key what be expect I would expect this to not result in arbitrarily large memory usage one solution worth consider be that a dependency should be remove as soon as the callback run the next time and no long use the dependency from its previous run but if this can be demonstrate to necessarily result in other performance drawback e g every key base access become o n rather than the semantically expect o 1 then that solution may not be viable ideally it should additionally be ensure that even if the callback never run again thus never expire the unused dep the memory for the unused dep be eventually free by the time the callback or compute ref be garbage collect but I understand this may not be possible in js at least without very complex compile time behavior what be actually happen in this minimal reproduction one of two thing eventually occur after some time depend on various factor 1 the page run out of memory and crash 2 the follow error occur due to the reactive value have too many dep that be never clean up rangeerror map maximum size exceed at map set at track vue runtime esm browser js 501 15 at proxy have vue runtime esm browser js 821 5 at 26 13 at callwitherrorhandle vue runtime esm browser js 1550 18 at callwithasyncerrorhandle vue runtime esm browser js 1558 17 at reactiveeffect getter as fn vue runtime esm browser js 3092 16 at reactiveeffect run vue runtime esm browser js 428 19 at job vue runtime esm browser js 3134 14 at callwitherrorhandle vue runtime esm browser js 1550 32 system info no response any additional comment as a side note when develop in vue I often find that I have to think about memory leak which I really don t enjoy since how vue s reactivity system manage memory should be an abstracted implementation detail I often manually test if various thing result in memory leak and this be one which do this be one of the few thing I dislike about vue frequently have to reason about implementation detail in this case I have to think about whether reactive value callback and or dependency can be garbage collect after certain condition occur I m not sure if vue can be blame for this problem whether it s a problem inherent to vue s design or to js but I figure it be worth note that I believe it be a problem that have a significant negative impact on vue s dx in my experience I run into this because we generate new ids client side and read they from various reactive set and map our client can easily trigger this by copy and paste a large selection of item in the ui for example generate large amount of new id for the new item which vue internally add as reactive dependency even if they undo their paste the dependency for the new id stay in memory it doesn t help that our application be a spa and even if this happen not to be a significant problem for our particular use case the same can not necessarily be say in general and this be still an issue which fix would reduce the mental model require to use vue s reactivity I don t want to constantly have to think about whether memory leak be a problem just because I m use a reactive key base data structure in vue and not to mention I never want to have to comment why certain code be necessary to avoid these memory leak |
vuejscore | chore simplify setupcomponent condition check in mountcomponent | Invalid | this pr simplifie the condition check in the mountcomponent function in package runtime core src renderer ts the compat check in if compat compatmountinstance be redundant because compatmountinstance be already base on compat this change make the code clean and easy to understand |
vuejscore | chore add search to support html tag | Duplicate | |
vuejscore | fix runtime dom transitiongroup child el may be null | Bug | close 9067 when the child of transitiongroup be component first set the element inside the component to empty through v if afterwards an error will be report when transitiongroup execute the end animation |
vuejscore | weird bug with export default after update to vite plugin vue 4 2 0 | null | vue version 3 3 4 link to minimal reproduction impossible to reproduce step to reproduce unfortunately the bug be so random I haven t manage to narrow the issue but I try different case which will hopefully help with identify the issue error c vue 134 0 error unexpected export plugin vite vue file c vue 134 0 unexpected export 131 132 let comp composer 133 134 export default definecomponent 135 and here s a chunk of code let comp composer export default definecomponent when I modify that chunk like this let comp composer export let aaaaaaaaaaaaa 5 export default definecomponent the error change expect but find sfc main 133 endregion 134 135 let compconst sfc main export let aaaaaaaaaaaaa 5 136 137 export default definecomponent and it look like whitespace matter let comp composer export let aaaaaaaaaaaaa 5 export default definecomponent produce expect but find sfc main 133 endregion 134 135 let comp coconst sfc main export let aaaaaaaaaaaaa 5 136 137 export default definecomponent what be expect no error what be actually happen when I update the plugin my build break unfortunately I didn t manage to narrow the code to minimal reproduction as this bug seem absolutely random but it s clear something be wrong with sfc processing I have two relatively similar component with export default definecomponent but only one of they produce this error and only in version start from 4 2 420 beta0 2023 04 17 as it work perfectly with previous plugin version system info shell system os window 10 10 0 22621 cpu 8 x64 intel r core tm i5 8265u cpu 1 60ghz memory 1 16 gb 7 82 gb binary node 20 5 0 c program file nodejs node exe yarn 1 22 5 appdata roaming npm yarn cmd npm 9 8 0 c program file nodejs npm cmd pnpm 8 6 2 appdata local pnpm pnpm exe browser chrome 116 0 5845 111 edge spartan 44 22621 1992 0 chromium 116 0 1938 54 internet explorer 11 0 22621 1 npmpackage vue 3 3 4 3 3 4 any additional comment no response |
vuejscore | vue3 custom element prop type number be a string in production | Bug | vue version 3 3 4 link to minimal reproduction step to reproduce npm install npm run build npm run dev what be expect we import vue component and the same custom element below the custom element typeof should be number the sum of 5 5 0 5 should be 6 what be actually happen custom element typeof return a string sum be 5 50 5 system info shell system os macos 13 5 cpu 12 x64 apple m2 pro memory 201 20 mb 16 00 gb shell 5 9 bin zsh binarie node 14 20 0 usr local bin node yarn 1 22 19 npm global bin yarn npm 6 14 17 usr local bin npm browser chrome 114 0 5735 289 safari 16 6 npmpackage vue 3 3 4 3 3 4 any additional comment hello vue team I hope you be do well baiwusanyu c could you please take a look at this issue when you have a moment thank you so much guy tara |
vuejscore | structuredclone api will produce an error if argument be reactive object | null | vue version all link to minimal reproduction enqtusto3dau zvbbzijpy4gdtoa1fkktou2ait1gzgikjvb4niwhyeoyr9z42egecnw7ozzsm99joyztbypynas9lwtnodheo2p0lkzxguywwfvb9ljtqcntlbxpoomtjnqqtdg wcdb fk5hfzn1tkwh jvpmhw 4eum m6leycg0qzidr fof5nrclzb5dfbovfdrufjlmm6onsqt6gowz8mw0j8a03qp9pti7ap09jboo39gfhjl2svvg2jnsq9y8mhfokshzzkyghee8r5sezflt0ixxwtfasabz8kfeegw9eiadescj25kzrlytpbmr5eanvvupn0ayuvv6timku1twdatovlbgkd 2jkg1ylgxatgvfns3sxnwvokjwz5jteafiv1tldadfyqdl9skbrzsf0viatobe5 jiwyy2p98lxjfxsav hdjan226fh16ngey5urswwpc ssbznuskkdf6jfip0jtjhpgrexl1a3ffqzlab ndze6 efph4da74qag6adshrbaphp3ij9ke4xp04 2iq2pqbkqywe step to reproduce open the link enqtusto3dau zvbbzijpy4gdtoa1fkktou2ait1gzgikjvb4niwhyeoyr9z42egecnw7ozzsm99joyztbypynas9lwtnodheo2p0lkzxguywwfvb9ljtqcntlbxpoomtjnqqtdg wcdb fk5hfzn1tkwh jvpmhw 4eum m6leycg0qzidr fof5nrclzb5dfbovfdrufjlmm6onsqt6gowz8mw0j8a03qp9pti7ap09jboo39gfhjl2svvg2jnsq9y8mhfokshzzkyghee8r5sezflt0ixxwtfasabz8kfeegw9eiadescj25kzrlytpbmr5eanvvupn0ayuvv6timku1twdatovlbgkd 2jkg1ylgxatgvfns3sxnwvokjwz5jteafiv1tldadfyqdl9skbrzsf0viatobe5 jiwyy2p98lxjfxsav hdjan226fh16ngey5urswwpc ssbznuskkdf6jfip0jtjhpgrexl1a3ffqzlab ndze6 efph4da74qag6adshrbaphp3ij9ke4xp04 2iq2pqbkqywe check the console of devtool what be expect support datum structure like object in reactive variable what be actually happen only basic datum structure like string number in reactive variable be support by structuredclone api here be the example code with error const info1 ref time date now array 1 info name xxx const info2 reactive time date now array 1 info name xxx console log deep info1 structuredclone info1 value console log deep info2 structuredclone info2 system info no response any additional comment no response |
vuejscore | template can not correctly handle chinese variable name | Bug | vue version 3 3 4 link to minimal reproduction enqnukfowzaq mrkl4jukgo3kq1osw9waatcmiesbknax7zsj1sk8hcupko gx wtppqirrxsdy745nzlus21toocmqjftnypnqbrzfrczexktabqzrgcpk5f 62j ceaileegjdirkoqdimgobcxpmf4ezfkuhdaoivmlrf1s 5m4pccxzwpkxz40aqdu8daadiqxm pj743lwzblcxcknt8t0wvo zg5yagujb42kqtqwyeprwietd08ilp8jcdw3yl8zsklxpwq7jbahc5be1mksbkystp3su71dplob5la7lmw4g0gnegwphhq7rnvo5dhs erxt hu78z3o7gxanavy1mfuarj0dbx4umed1r2yqvuuin0d3imtivczg9oslyukfcsr015lwhmxyutrlnyopw2h8ke9s6r5nnexnpem hp3pdiv33fzseobi5npmw step to reproduce click these button and open the f12 console the print text be always the first button rather than the correspond button what be expect print the content correspond to each item what be actually happen the chinese variable name be not handle correctly in the template if the chinese variable name be change to english this issue do not occur system info no response any additional comment no response |
vuejscore | defineprop bug when interface properteis contain two or more colon | Bug | vue version 3 3 link to minimal reproduction enqtu1fv0zaq iuhx9jkoxxslarfgcobejcxir4wmrz4mnk4z8t2uk5r juxpgurnvwblu 57 vo b7curxvvj9tghs5kgizje8qmtuerkjqiuwkuiwlmdq7kkcfggvoyb1cdrm3zuxrwrbwjckfurj4fpypklpjwa9qk3o0hyvnlcp6 m klkq9rf3h6azm5 ug1spjj1ivsqlo3ouwib1e7omctsjuyd6do7tfvksywshfgpzghosuyhu4439xhtugkpz7p9xoeunxyqmv diwpdbqt d7najsudy3rikpk5wtk oo4jhus qlpso9oryofllj9iptkkubjwvb6cjgw9pb9cqvqxl9atu3q3hxfnksbnesbbjuxnf8iy8vf lbdxxzflu545fjta1pnbqij3svhr0trutobi gbt4atszhdbh5skhz2 3naumjw5b7nezr hsfv4rbhpdglgdfsuio9l1somi306vwrbvl9t7lzxrl6cpkdo7nn73guvw9is 1 dipbt8onmlrdxnu2icx7ul3rxtknein4ln04ev1g93r2ovtxuex3f 4ctsm step to reproduce export interface cctableprop editable boolean cachedmode boolean onupdate expand newexpande readonly any void onupdate select newselecte readonly any void defineprop what be expect define prop correctly what be actually happen vite error with tip about miss xxx 2023 08 04 092136 system info no response any additional comment interface property contain one colon nothing wrong two or more colon vite error |
vuejscore | the page have a memory leak when the page have svg component | Bug | vue version 3 3 4 link to minimal reproduction enqnvftv2jau itnfimv2gtcjbbk0vzwaz20rlr3mbcij8hfsspbsvbr vuoewixrmibb t85 kdm7fsa557zyfswkita55bmgilhmrcpncrsyzi00jylffawhy0jlbdolugv2r21uhfmfm7uee7i n6gf k9dfwstpy3xdkddiwsm74quaa7lyyxjixbq pwoamdp2wnxgki8usf3oldamif4w1fpjllhi8plyo h anyk7u3ebr7rood axfthaox9bo98bkc lrye8pynrxsaogj9yvo3iswyqgd9 iigfmvnk fhhlzqnyd9avur 3iz kevcj92q50mjwlpvvejji3d1hlelfzzzgxqx7nl1iiitabbhdyxqlu gpnvbd7s5fek4 u 5k9m42qre9zoujcysq6zc52ibeghlyfc0lkdm7usbglfah juajwhfu1 0iuifarxsp2srlhltm 5mfjuzp9uo6o06wbfapzgbmlqr odr1hyxfjmqp4nndupu4h0pqpjqhw92pdreldhz6p6u tsbgqjjjkupawyyq0df1zm098v6oqrxp6sqd qn30yq0pgavvgkkrlrrgawdkkep3guzzu4ilat9hmfonhuvg h30lgud6o9uwfinsgd8ergxf0qlvaano0lp7rf7fw67rslve6upngcuguaqiha7o tmnxr8mmhut7yuobu6wpezybz0ji0x4rkftcpn2psfwk3gqcgw1hzzt3v0pcsfjf3z4bc77af7vjrat6ju8zhuvu4pyfvfmgiukg step to reproduce switch visible1 and visible2 and observe the number of dom nodes in the performance monitor panel image what be expect unmounted dome nodes be reclaim what be actually happen unmounted dome nodes be reclaim system info no response any additional comment no response |
vuejscore | fix compiler sfc normalize window path when resolve type | Bug | get error when use defineprop and import a type from another file on window for more information and a reproduction repository look at this issue similar to this pull request |
vuejscore | v datum scope tag be miss from child component | Bug | vue version 3 3 4 link to minimal reproduction enrtvmfu2zam rvwgjaoqk1dd kcimv23z7af8eme82yjeh0gihiv4 sndxj0o2way gkflxust1zulfufw4oihegrqvhefagt2mmmpw1hocwwmhf i8hwdfoavkamzorzjy2zplamrchfczxppayhtyr xjv uahyttyomf87nbodhde7ifuo5gimtg22jv9otkjpcd7suxcsdfzaguu0gmlxn1o sq1qu9x5pwungjvgmqhfpkrx42a 3uckgxdtvemcccnom wptd1u2 93y0bcgft5 j6sxvhdeb8ssmq2dd7fifwrruxepqzy5qiej3sshtihyldkquffkoxvx7vlgd3ljp tgqgjbr7bb9zp zt7jvgzbhoyyh23l7cuizsbjpi9ysd4 om4 mry r1x3suu o9cfnhmxlnz965tjxiz7s vdlgew24cg4mb54ks0buw6bajoco09kmnerqbzfsf0xq4ojpnqrsm7zjtlwry 1ese6do0dqi1tysii k on r 0jym e5il cn0yccljetzdduxl1n5ocujz7thgfsiivhcrxxyukgroqteetdsrgn0ekvevxflxzvs xngkswkq1zzv5xxz31ovyrti gj21gusucdk8lhwjd tkflfbzauoqwblgmotsxm0paqy8eqt 2bb15jlr8apv7zna step to reproduce sfc playground enrtvmfu2zam rvwgjaoqk1dd kcimv23z7af8eme82yjeh0gihiv4 sndxj0o2way gkflxust1zulfufw4oihegrqvhefagt2mmmpw1hocwwmhf i8hwdfoavkamzorzjy2zplamrchfczxppayhtyr xjv uahyttyomf87nbodhde7ifuo5gimtg22jv9otkjpcd7suxcsdfzaguu0gmlxn1o sq1qu9x5pwungjvgmqhfpkrx42a 3uckgxdtvemcccnom wptd1u2 93y0bcgft5 j6sxvhdeb8ssmq2dd7fifwrruxepqzy5qiej3sshtihyldkquffkoxvx7vlgd3ljp tgqgjbr7bb9zp zt7jvgzbhoyyh23l7cuizsbjpi9ysd4 om4 mry r1x3suu o9cfnhmxlnz965tjxiz7s vdlgew24cg4mb54ks0buw6bajoco09kmnerqbzfsf0xq4ojpnqrsm7zjtlwry 1ese6do0dqi1tysii k on r 0jym e5il cn0yccljetzdduxl1n5ocujz7thgfsiivhcrxxyukgroqteetdsrgn0ekvevxflxzvs xngkswkq1zzv5xxz31ovyrti gj21gusucdk8lhwjd tkflfbzauoqwblgmotsxm0paqy8eqt 2bb15jlr8apv7zna what be expect when click the switch button the background should be the same color but when I add some comment before v if directive component the bg color will not be effect by the scope class great what be actually happen add the comment before first child component system info shell vue 3 3 4 any additional comment no response |
vuejscore | dev always equal false | Bug | vue version 3 3 2 link to minimal reproduction step to reproduce create project with vue 3 3 2 and test invalid prop type check no warning message in browser console what be expect in develop environment process env node env production should be true what be actually happen I find that this commit cause dev to be transform to process env node env production result in it always be false cleanshot 2023 05 15 at 03 39 37 cleanshot 2023 05 15 at 03 57 09 system info shell system os macos 13 3 1 cpu 12 arm64 apple m2 pro memory 554 94 mb 32 00 gb shell 5 9 bin zsh binarie node 18 16 0 volta tool image node 18 16 0 bin node npm 9 5 1 volta tool image node 18 16 0 bin npm browser edge 113 0 1774 42 safari 16 4 npmpackage vue 3 3 2 3 3 2 any additional comment no response |
vuejscore | error 3 3 2 component as variable error name be not define tsx related | Bug | vue version 3 3 2 step to reproduce this issue be introduce with late vue so be a break change if intentional when import a component into a ts file and pass to another object ts import mycomponent from mycomponent vue later const myobject new someclass el mycomponent use late vite vue this now create the error bash 11 03 31 am vite internal server error name be not define plugin vite vue file www src page ellogo vue at sorttemplate eval at clonesort core node modules pnpm node modules source map js lib quick sort js 2 848 3 107 at clonesort core node modules pnpm node modules source map js lib quick sort js 112 10 at export quicksort core node modules pnpm node modules source map js lib quick sort js 128 19 at basicsourcemapconsumer sourcemapconsumer parsemapping core node modules pnpm node modules source map js lib source map consumer js 604 9 at basicsourcemapconsumer get core node modules pnpm node modules source map js lib source map consumer js 70 12 at basicsourcemapconsumer sourcemapconsumer eachmappe core node modules pnpm node modules source map js lib source map consumer js 136 23 at mapline core node modules pnpm vue node modules vue compiler sfc dist compiler sfc cjs js 3671 18 at docompiletemplate core node modules pnpm vue node modules vue compiler sfc dist compiler sfc cjs js 3643 13 at object compiletemplate core node modules pnpm vue node modules vue compiler sfc dist compiler sfc cjs js 3586 12 at compile file core node modules pnpm vitejs node module vitejs plugin vue dist index mj 163 35 name be not define system info shell node 18 6 mac any additional comment hope for a quick resolution to this issue if there be a debate about this or problem with reproduction I will create one |
vuejscore | definecomponent be no long tree shakeable without pure with rollup since 3 0 0 rc 3 | Bug | vue version 3 3 0 beta 4 link to minimal reproduction rollup repl step to reproduce 1 open the rollup repl I link above 2 see the output include definecomponent code 3 toggle code in the definecomponent function in util js 4 re 3 0 0 rc 3 version and my suggestion version work fine but pre 3 3 0 alpha 6 version and current main branch version doesn t what be expect the definecomponent function be detect as side effect free by rollup as describe in the document definecomponent text note 20this 20is 20not 20necessary 20if 20you 20are 20using 20vite 2c 20because 20rollup 20 the 20underlying 20production 20bundler 20used 20by 20vite 20is 20smart 20enough 20to 20determine 20that 20definecomponent 20is 20 in 20fact 20side 2deffect 2dfree 20without 20the 20need 20for 20manual 20annotations what be actually happen the definecomponent function be not detect as side effect free by rollup it seem the extend call and the property access option name be treat as side effectful relate commit system info no response any additional comment original issue |
vuejscore | miss ref owner context error when use dynamic ref that isn t a string | Bug | vue version 3 2 47 link to minimal reproduction enp9udtkxdaq zuhl6vqnrokqqiyivgtxoe6mdw4zyvcvqx035227ljxeuiym2dmzugky7fev7umtla6rop26uza paujfc4axkbojmwqdwpotmdyocakqe7zwasxnrphqieo9bkwplzqfo0ucdiwblfx8aelgfaxrmw do0ox8euuju kcekotgt01cygdq3mku3lhwlzkmblq9cesgyouf30illwtjde21gktazr8qqee6huiocvprb43wvk mplcu1pyggxvmm8gg0js eovoknmje7r bkjkyu nzotukev2mpkpgvns falwjvdv4txkg3sbkvlzoqiwlaxv1zpmob1cqmpn4n7jxiiubjitpxtcyehdggvbgz kh31 ia8wn6r7n i9v8ad7uv step to reproduce none you can observe the issue go away when the i d s in testdata be convert to a string what be expect I would expect vue to either convert the value it receive to a string if necessary or throw a more useful error message what be actually happen error miss ref owner context ref can not be use on hoist vnode a vnode with ref must be create inside the render function system info no response any additional comment I run into this weird and very specific issue the other day basically it involve use the option api and iterate through an array of object use v for and use one of the object property as a dynamic ref when this property be not a string but a number there s a pretty cryptic error message that take I a lot of trial and error to figure out |
vuejscore | browser autocomplete suggestion prompt generate from datalist show twice | Bug | vue version 3 2 47 link to minimal reproduction enq9vlfv2zyq itxoyaaijlqzmuavzaspqmwof2hncge5j3q0tnmqpecsdknav 3huljlhuvs1pgepj4p7vv 3hh3kn0wdfppsfoeuwm0ly2yna29wwuevurbeebnc5hb0utkojjne5nv6qqr2xd2gccr2nwl7mg82guaeayunjy4g75lgmyuohv4viks9dnb2az4pqejh gh 4lq3gbn2vllys38smm186orj3hf1hypatciav9wkxqwszsf0c fjv7qvlbbtfgnjhn9o3xhwwg5wsklcyxk2asvijq6th45ebtryg7pg smllymwmlrallamkeuicvstsusytfpdw2sjbc6ii1bg3ynqjrrcpik4ewuyxwusqwa7wl9y0vmcxtcfkwodnknwp x1qrsikg0jvoseecz64el 7aham0xnmgyaqldrq96tjnm lc 3ndrguttga1y9 i0soa80ocplmt0disjkjimrijcu7jdtkmwwdjcrnrxfqfammzdrxcwoeg34g96 lj1fzoymufciibgtikcbmpngdbnjzlq5l7pi i74z5jk21l7qzsnodqptd5wampx gg81t2i6p2lzgvmwmogzq skpgw vvjokg7nriomxcg22shwuvksctvkpegwuxdtpxhy2z3o2oy7ezulxujm2oighh641dzts4f3w7rsif2ybxqd6damtgm4pmo27bu afog7uno4cxwfqj3l2t5ihzib3ntuc4wgkprgqlxsse vtlodtfcodnxxq2ulqru33k67xcfqgfc x3tywkae2mgb1smeiwn qa2byf93oeqadqtyyvehgv8saki0z4q3mp3rvqb lqgalsrw8e k argnvk01otozt s6yip4el3fc rfazxfhdxlpn namedhvy53wdtv7kkngo6t4orpd792xduksxpq7kjepcxdctbfbxh020 hlinrf60q7odzh exl7uf 5t6y51nhoxm trar1f3ud7uia8uei0utyvv0yvlpadx 0bkxmibimltogvkpjhk2mg1yy 9fghjsf3tbqzt2kkh0hhku79tbckmktbbiv2s7gyus5xu3vvodkw8snuyhk5wbdx3hq8zyvfxlgvs7onjbllg5yxsb0xee1t1guyidqrq ocsv orssqlawrnmq4al2vu3f5aq80elkwynmuaajdojczuisal qzvbwhs9exv7zu cabjzxw3ztjupb1orj5pdyuhodsnmuf7p8no2z4x3o3sr5eyvtms5xre44aam7vmr5c0c6snb0e2yyll0gvhjv88yg43mlykjn1jxer0b6mkbyqxbd4a6b 6zntai z8pagxtbw1mwrzi u7vupnthzbtkw30vikk1jvf fpwfrdj1ljvtvct9fustsxusz5ddoinrnhcxwikvtwqj9mnvi9sdiypuraluyu2v0dm7njiw step to reproduce 1 click on the input label bug issue 2 the browser should show 3 autocomplete suggestion from the associate datalist 3 select one of the option 4 after select the option the autocomplete suggestion will show up again with the value just select what be expect after select an autocomplete suggestion the box should close and be use as the input value what be actually happen after select an autocomplete suggestion the value be use as the input value but the autocomplete dropdown show again system info shell system os window 10 10 0 19045 cpu 12 x64 intel r core tm i7 9750h cpu 2 60ghz memory 10 77 gb 31 84 gb binary node 14 17 4 c program file nodejs node exe npm 6 14 14 c program file nodejs npm cmd browser edge spartan 44 19041 1266 0 chromium 112 0 1722 68 internet explorer 11 0 19041 1566 any additional comment only affect chrome test chrome firefox safari untested work as expect if the datalist be statically generate with or without v model work as expect if the datalist be dynamically generate but no v model directive error only seem to happen if the datalist option be generate from a v for and the associated input use a v model directive maybe just a chrome relate issue datalist implementation have be know to be buggy in the past |
vuejscore | wrap by break entirely if interrupt before it complete | Bug | vue version 3 2 47 link to minimal reproduction sfc playground enqtk8gom0amhl f4gkrckbwlspk0mb7bu0euuzbkffhzjrj2i2ivpsajgtrclppb2njf zvm3nwmcyzbwzyohcvlybaiq1mxyrzg20jzlbjixx 1mwrvbtdmqafr qsq 8xukpoov3ybxu4qgn1dyhzwh lqrrybeveaxb3qohckgclqkabq7sb3r6ouvjlmywhpisbufsxzspq6aoopxx1agpwqifa252chtupcppbvss1atjt2yhd52jladkkbkdmphh2n74d lxvkn984uoa4kviwgybteu ucalvexqt8z7zyown50gzaug4fnnd37 g4hy76 q41z2zecfl8h 2cq2rqtorbzf6upes8gk5eq8ksv65dwjws6cxtetpqfassv2xg9wthhs jplzpuezvwdnehlfetxx7wskpeouxzrjerx1pqut0jxhrzc1evkd6twnh2duumzto1umyt2k3jji lregehyssr029 zefa1wnz8uwb80o 5ux xb2ftcdoiypjpxyyeduzsng2z8fvgs8ss75pr c3dm0xulwboxfdvq step to reproduce vue click the button mark trigger error this will switch component within the transition on next tick it will switch they back to reproduce it s sufficient to switch they at any point before the transition have finish note that this follow the component order specify in combine with other component what be expect I expect no error what be actually happen the follow error be throw uncaught domexception fail to execute insertbefore on node the node before which the new node be to be insert be not a child of this node in addition the content of the suspense slot be remove and the page remain broken system info no response any additional comment no response |
vuejscore | defineemit type can not use compute key | Bug | vue version 3 3 0 alpha 7 link to minimal reproduction enqnultuwzam bvcsx6wrv11antol3sporg24yqwhhapdwj875wsdo4drrekj4p3uruixxcaoafqoqu msbaycna1lnxoawtfkftaos 1n47ykbrga4w4mk4fmqa2kuzamxrwsafownu1g84pxdtwk0fczkveefjxp2c2zuhrczh7e6hnhtz6n80fufx8pjf4hvf3cqbr wia0ybprx9q3ifrswmdt5ybbvqnmm7nmlvut8hoqof909okumrwit35kbksjr1jckznt6omndnti6nxqbj1 m rfxdgtkxftekq xlgwed0a0amf3f e qd9 pau0usnwwoooy step to reproduce vue what be expect should compile component without error what be actually happen error vue compiler sfc defineemit type can not use compute key app vue 8 9 const emit defineemit 10 update modelvalue value string 11 12 it seem bug be introduce in commit |
vuejscore | wrong merging of prop and emit definition from mixin | Bug | vue version 3 2 47 link to minimal reproduction enq1veul2zaq ivcfhxxllq9grpo3ksplb3ue3ctcakwloqkjyng 72jl6082g7p7ixrjd59m988pgafpsypa2rvvhvo5xnryn1wquoto7odhvcf1z8gij if3zmndwoo11tdibrrxwijcb3k1gmvfnsmnrkmiab0nqbxarxenzloqyxhj0spcllimebx55cw8p4jefr6xa0ivhafgznb9tc1w7phow 143a1xy40ruzludh4xsrbbio knpng5wzd7iqm9ledccyxedwxmudjmhmedvmsza2k22n0bqilldbwxab10ktan4ktxadeuhbn2vfilx0qcqummkhioi8whqpybvqyf6ifmkesmbre0oxbxwfvuguca9gkklmat5mwoz8iexevtm1su7cpkbk3b ewxo7ssg8qckgo3e3wkegihxfebrt4skfdok8v2obomvkx ye32jlrpr2nglo9k5zvpyajdx13pfmivbf1ipi kgpggc65k3pzbpwtl iagzdkv2cd658eha0ghoxouc01fodfpq7vagklafvsftilmv8yjeyemuxk7pogqmxlwxwwqsoylz0a44gxwz1gljbf9v2wwlii1w 3knuehyzv9rko57mmevuydi1yta8d0fyyfmfdrwzmj9ov uswioeqt8 gpepa3 m step to reproduce define prop and emit definition as array in mixin and use multiply mixin in a component the defintion get wrongly merge because the internal mergeoption helper use the wrong merge strategy for these field mergeobjectoption which end up treat array as object both actually have an empty todo behind they I imagine it s about this problem and get forget l1047 l1048 what be expect the field should be correctly merge for prop if one of the encountered prop be an object instead of an array all definition should be convert to object notation and merge js prop one two default two emit one two three four five six what be actually happen the array be be treat as object and their index become object key and override each other js prop 0 one two default two emit 0 five 1 six 2 three 3 four |
vuejscore | v for over reactive regression | Bug | vue version late main branch the late release 3 3 0 alpha 5 doesn t have this problem I believe this be introduce by 5752 link to minimal reproduction enp9km9owzamxl fymwdtdbiwnuitjwe4db1bpexjpgtlepvd8dpnrsbxm1 pv9sf7n4da6aiopanl4j7qj4dne9k6nhzynadirtf sesebpdoqn6zfkknnz41kf0hny 8ik949t6vbrcg4ndlbywqwmzgnloj8vt6xzlglk3sr7oak4uksbkdoa5qinnedw1ocp7c3tlugk0cytlbjqaoz5lchc7hvspjc5cigh8fev3uv3n0wa7n34m72nzvk rozlhlhij7jb5di66uytyqvxj9w1wwfv e1uy89srsqpbodrkx3fjeppvri0si4qiiboesv0y3 kg wrgkze7o4hutghlytmiit0h ox9a83ydmmrszfe52xbg step to reproduce click the button what be expect no error what be actually happen error uncaught in promise typeerror can not read property of undefined read el system info no response any additional comment it seem to be relate to the use of reactive if I switch the example to use ref everything work fine |
vuejscore | fix compiler sfc infer runtime type in defineprop | Bug | relate 4355d2492dccdb175b18d083e20f3ec39a52801f demo dev enqnj9fqwzamrx f gmdpqammtbex 5gh chhlrdmhjbsgrycp73yw0ppu99evf63mnpsz i6 ki1tvahq0ohkgoamy2fb8lb2paw2fi8euzoswxgxpi cob3s6msn16jim4c1ozkgqmhfubqit0g51a8gzzdjrsacgd7ocuwbuyw4szpjlaxp9wtrrq6bn4eebolvgd6ungvufbi6b3bsxdo azxb9u3l4cu c00uxhbpdy71 0q5uqy6azqchq4wjoedrd5rzdyxpxseufg0hzjw |
vuejscore | teleport target change be lose if happen while teleport be disable | Bug | vue version 3 2 47 link to minimal reproduction enqdvm1u2zamfhvwo3gfmnj10xwddbvsaqrs4ot ffutlbmsnc4i o6jjetjlmrdbysakjefp5kfesdfxng9myjjsaebxuydmppp3jscdanubg6g6bzm2co5qikusslk0uihdqy6g2f7 jn5qtmx8fmq3t4l98hbvkqjzvepss3bfunun iz5dqmyslgbcuukyaxokg9h2schqhdyctd0qiowrydbfacppdkwbrmrgppjbxyyl6mv0ri3nbr8uwez842dwfngxt1xsiu4ztml9j6a0ycfvwn1y xgmouxn vk9ghoy8pi32hjwforxxb7sh01bhi0iymelbtabxea70 xehb w7wbzkohov ec4ckmedhphvxj7m5dg7rwwqrmi4xihspheybdvyrkgbqwukrpctb21pauzzw7ihqccddh8ap844r1ermkve2esfsuhrje7kliqwusbxvwbk5lx6dydmvm llzsowyn6hj hajoopqlkkgh2szge3cdgs3 czldgbtuifv202two9ha4qx6e7ucpzxnhzasundtchokq5 ylkjglxwtayhxnlybcyfharazj 0fedyvfwqivx5gyuqa71sbbyu2hr 2olkid hhgdkcwm3hpnoymk6oumrdoyulg yq2t9bt1vxglg pc7lp4xjbsds7fp7v41kgs4bjdwqv1pxqzwux7uuuhwpjvfyoeusg7uxd7hyrv2s3phr52mqt41d2a96lvwx4mmtjmhyqndud6tayxdnfqkx5oeei8vlxesrhgrlfvv w zd9qlxws6lmmn8g2rmhzg step to reproduce 1 set the initial the teleport component target to target1 1 disable the teleport component disabled true 1 change the teleport target to target2 1 enable the teleport again when the teleport be re enable the content be still teleport to the old target target1 even though the to property of the teleport component have be update to target2 what be expect change to the target of the teleport component the to property even if happen while the teleport be disable should still be honor when the teleport be re enable what be actually happen change to the target of the teleport component the to property be ignore if they be make while the teleport be disabled system info no response any additional comment look like vue can indeed handle the teleport target change but vue only handle it while the teleport be enable |
vuejscore | unescape character in css variable name when use css v bind during ssr dev | Bug | vue version 3 2 47 link to minimal reproduction step to reproduce load the application what be expect the paragraph be always red what be actually happen the paragraph be unstyle no background color and become red when hydration occur system info no response any additional comment the problem come from the fact that the v bind expression contain a character which be not be escape during ssr the css variable name be 938b83b0 style color and become 938b83b0 style color during hydration |
vuejscore | teleport child don t trigger unmounted hook when teleport be disable | Bug | vue version v3 2 47 link to minimal reproduction enqvuk2pmzaq ssjlirqao22uqu0ivl13fpvg5cejkdxeczbkk4q 71j85gesph2hmfevpfmdv3wxam4btdybjultrini4duauzkl0pxqw0k6ptdwi u7vkqhtaqlvs0sfquatpao4ghbsrsfvlknm4ccwfrdqpg2erkmwpkty20vjn r8j5dfuunlwz3bidzp t9zmnlgtnvj4goeaf8 szlpsefr inprgimzqxxcywr cgzuuqde6yxiwjqsrubypaqsqrfg3xwyafzi9namv6zsrjvbestgd8ne5otm dtzlpsfgzarjlovfscvf2lphrcopnbd3fd8nbvnf76etb0mplg kpvifyfcdm2lkgy5pkgxa0zogmyc6zccdffunlpzgyrkjalec1p3tnv43gsqfify3duhk gykns3wldkodge0ygf7 jfmmshad7tb9swwyyruzy53bn2jd8pr39mqwagbvarwf go5xar sobquowfzbmamezlld7 n3s88wizqk4r gjk8t48uhrsmdbbgk67gtt07duprldkmsspvwxgzrnlkxqlzsfvjlfn9 by xl ckrg3tdjnhv01nq1qfkxdtz35akxw9srrpmjrv1ubif9efz0 hn1mnz5puj aawwip4 step to reproduce use component and add some component to it set the disabled attribute to true what be expect the child component should trigger the unmounted hook what be actually happen the child component don t trigger unmounted hook when the disabled attribute be set to false the event trigger as expect system info no response any additional comment no response |
vuejscore | vue 3 sfc compiler function call with semicolon bug | Bug | vue version 3 2 47 link to minimal reproduction step to reproduce npm I npm run dev open in a browser mine be ff late see the console at first glance it be a sfc compiler stuff if it be a vite s issue I d open it there and close here though what be expect clean console compo vue output with its hello what be actually happen it be crash because the compiler remove semicolon and move window after a function call image system info shell ff111 0b3 win10x64 intel 12100 w 32gbddr43200 node v19 2 0 any additional comment |
vuejscore | usecssvar be call without current active component instance | Bug | vue version 3 2 47 link to minimal reproduction enqnunfqwzam bxhmdjce3evwvryfxigm6iju8q2lpmysv59clo2sshok xt6u66i3jzvphgfkwoqa7grycmo4de23anrcql9mbwlks4qmajail39m5wdg6ajiezv2wvrz2lcaddf7tbjbab3zw4ygi22vrzsi4gey4jdr7xebkgqbozqd1romsifnkypzxkrmllo3pf8bnpxzp2hi5p mya2jxwst0 8yiahzq2i9 argyr5b4iw90bjuz5wdhm9qotfz0 5baf2iglnxzqvjirs5zk1ujdghxguvgnjnnkfyw6gd2vutkxtvmfqhchlvwvybtrdfggdfkhudnhygelnncaksejqx7qnhgw kf5i phn8nytboyvwc8erq4 step to reproduce vue what be expect usecssvar work well what be actually happen usecssvar not effective 123 system info no response any additional comment no response |
vuejscore | current instance be not unset after error in datum on ssr | Bug | vue version 3 2 47 link to minimal reproduction step to reproduce click trigger error in datum it will try to load a component where there be a js error inside the data function on the component then click click here to see stale instance it will perform a hard reload call getcurrentinstance on the server and reveal that the instance be not unset what be expect I expect the current component instance to be unset if there be an error inside datum what be actually happen the current component instance be not unset system info no response any additional comment this be very similar to which have already be fix the difference be that the error happen in datum instead of during render I have some trouble with our ssr setup and pinia use the wrong instance after an error pinia look for getcurrentinstance and use that instance to inject the current pinia instance |
vuejscore | type boolean be not assignable type boolean when use withdefault with a factory function | Bug | vue version 3 2 47 link to minimal reproduction step to reproduce type boolean be not assignable to type boolean prop readonly expand boolean hwacceleration boolean false prop readonly true undefined type boolean be not assignable to type prop readonly expand boolean hwacceleration boolean false not sure why there be a type error on hwacceleration but not duration if it s invalid ts export interface prop expand boolean duration number hwacceleration boolean const prop withdefault defineprop expand false duration inject plugin key duration 300 hwacceleration inject plugin key hwacceleration false change the interface to this solve the type error but it seem wrong the type of the value be still boolean the fact that vue need a factory function in withdefault doesn t change the nature of the value be this a bug with withdefault ts export interface prop expand boolean duration number hwacceleration boolean what be expect it shouldn t be require from the vue documentation reference default prop value when use type declaration ts export interface prop msg string label string const prop withdefault defineprop msg hello label one two what be actually happen type boolean be not assignable to type boolean prop readonly expand boolean hwacceleration boolean false prop readonly true undefined type boolean be not assignable to type prop readonly expand boolean hwacceleration boolean false system info no response any additional comment no response |
vuejscore | watcheffect within effectscope stop work after navigate away from then back to component | Bug | reproduction playground sfc enp9vm2omzaqfhwlsxjtglf9uaqk2tuuvs9vq7bvl1wigqjdsjftyfbzvhvhnizapiqd7fn95pthzt5jxftta97acxrudzko2mamkobqtcqteyk3szfmkl7gnlggqmb1o4j6w4pt7flb7jf2vfedlciuot hodhc79r5l8kespjx0eu2er5e5uccfansi8uf jigamreatu fhdfyhgz994quxfzofdab xgu6aiqbwrojqalak7ormspqiiqrlq5ewezorcmsermknszl963twt1frusj6h4po brmzldojgxqxgx1rrkqdc1qf1gy3slylz4ouqqt2 0jokpyzrifufihqtyxeyzc8fsderlqt15q2rh49 imv6apqqgiykipyhxj18nh 4h 6jbrjnzt7ikvvxvatfoazy285ce5r2ijycwahecd m2xio0o40d0k1tkvmbsgavkt5yujlq jx5jtotk8o8isg1qtczgzsnkn0 7orwtkxcvxbe46nt7hzqtogpaqgjpsshhqufmzzs0xlueii3pjsuaaqhgs9yc2krbsnu vqyr9b9fmozgzh2mfy dn1nvqtwuvws 5ct6lxn7sqvk0cx9fwufzwlpo1idejrjj uqjncmczi5dz8fpvro3wgvspvsvrtyjgdu jvfkgnbwcsdjgnqyvuz91ozdfqrlyau74hsquysiv01klnn5u rwjcb6alquuzvdam13bdn3ogv54gpwvxbctbjte6jyxyqmp3fe5xxj3jlkel4radvbttbjulyd47b0vt73zsxvubn8dv1wnncezv882gb6gxyrzrbc7lozrhicquo3nmxjp9k dt hcklomnzuczpi0wvzu8jd6t03sih 3ea2lwt5kjzf qohuyz haxsgbfdhv93yfsn hymojakqpxvyj z3p8tozbieerwiaajuxrzedqctknz1aruc4drfrlfvcs 8sff7a step to reproduce the bug 1 navigate to the testview component in the browser 2 click the button testdata count property be incremente 3 navigate away from it stay in the spa 4 navigate back to testview expect behavior the button should cause testdata count to be incremente even after re mount the component actual behavior after navigate back to the component click the button update the refresher but not testdata teststore js t 1675088280233 17 refresher 0 05272026601141877 teststore js t 1675088280233 11 watch effect run 0 05272026601141877 teststore js t 1675088280233 17 refresher 0 937791768731258 teststore js t 1675088280233 11 watch effect run 0 937791768731258 navigate away logg js 197 router beforeeach pass logg js 197 router aftereach pass then back logg js 197 router beforeeach test logg js 197 router aftereach test teststore js t 1675088280233 17 refresher 0 558079237843816 teststore js t 1675088280233 17 refresher 0 31739197899941574 |
vuejscore | watcher no long fire in the order they re define from v3 2 38 | Bug | vue version v3 2 38 v3 2 45 link to minimal reproduction enqvkctowzaqrx9l8czbsui wkaqrcokpgcjjtdpmm0cfsl2uqeo 84krvupeqill2bupb6jmz49wzt1lbivy33pghvay2jtruhgwemc9obwn8cxcguna ydurareqktdgm0d6d8adajly5eueodb8bj6i66hy303wuj0lqhju9hvyfeabirrctkiwqk9mxmtftewyqeepjpzrmjntjjsizwgy6zrmimzsewbo6dyoqe6ah8j1no6mzm6w5nhkj9znj wi8tloqaysoiifuaet3f9p20xwhiovvtt9g2ddclylqo14krlhhjot tlggnk6wqsnm7n5ruoa0ivguv2oo02tijs421yhui1q84b7x9ogsluxxlgnetdnsrtdjqu8ww2fkrv40pl 0mvup3zhw9okoulln4nfozq5c61bu6dh gxxl bf5pv0lhziewy4yvndjsbg step to reproduce observe the console output what be expect the console output be this be the output for v3 2 37 1st 2nd 3rd 4th what be actually happen the console output be 1st 4th 3rd 2nd system info shell system os linux 6 1 undefined cpu 16 x64 amd ryzen 7 6800hs creator edition memory 841 05 mb 27 10 gb container yes shell 5 9 usr bin zsh binarie node 16 13 1 asdf install nodejs 16 13 1 bin node npm 8 1 2 asdf install nodejs 16 13 1 bin npm browser chromium 109 0 5414 119 firefox 109 0 npmpackage vue 3 2 45 3 2 45 any additional comment no response |
vuejscore | typescript import ref can t be use as template ref in development | Bug | vue version 3 2 39 but also reproducible in late as the time of write 3 2 45 link to minimal reproduction dev enp9uctowzaq jwvl2mlxjboizbw5ydeas6ioy8h2bab cf7kyjv xfspgpdktjuzm7menxij9byvkows8jxrreehqmzg6kbzy0joag2qfdtg 5ggj0zchiucd1x8onuhzieqrigqmxbkjbmaexd9obwt5bsaiizimawwek8yli2hwwqtpztgx3oouudesa8zdmmsmtcvxgw7ebkfs5ep 3xnldgiw3ghos0nqqz2qjtit x1b2og09znknx2yczr48ujeqwzsxfaht0mundo0p3b9jn7q ag 5pamwcpb5caec w8mvvyfiujiwvb0uvyfa5ch2jn jumw0p khraoqeh5 fxmawm1ioqpgn8v1m4xfetabqdroy1rkrdkvkplbx7ydqnuo9r7rpelnsxzkovewzmmp snkpa step to reproduce open the browser s console in every step check how the message elementref value change from the watcher in test ts be display change between production and development you will see that it work as expect and the message be still display when reload the page add lang ts to the |
vuejscore | transitiongroup be miss the style scope attribute on ssr | Bug | vue version edge link to minimal reproduction ssr enp9kmfugzamhl f8rkqaufgku2 r8ifglvsqhlzgalcvpscuk1vk5vtbp 92mv bljou efdajxjg0ifbw21qnbry45iivthymckk5fvjs3gwr2qer0yqps7jp1sgx8taxx8a6cea8vkm0uta116pbfncwrib9miyodgtqr0323tlny6i2awrnfeoe bbe ze7ektecqrp zsdgvxps6l3i la0nugkdze6jzhquxybsg2digr f vubfm 2by4w7dgaonymxiezbg9wabs5fbbmkx uny1kpm2mkfuptkgdm2 djnkqofjl5knnxyi5uky3hg8c3ecra4u2mybc7ebzpviilfmr kt9zfjvzcfwcsia2c step to reproduce open the link what be expect all text should be red what be actually happen text within the transition group isn t system info shell na any additional comment this appear to be a regression of the div be miss be style scope i d |
vuejscore | typo cause warning for native svg fedistantlight tag | Bug | vue version 3 2 5 link to minimal reproduction enptuk1pwzam stroaasa7fxczgkegkjczeuvytobtpsjeqcdzj233gyrvtgvdr z3l trzmz9zmywb8xgueziqb8frqxgq bnhkzrf9lpl0pc45a0e2le7svfviuuuf4jice gd7on4ftw8yrooht7jqakbjjvvfzjgknhzwrayil0hpqioq2izaelp5apkkooiwlus4uc51 yoncztjn5lf5lxh2gvfcwfshpb3ucg37vk 9ki7sdzi ms8bhh0i2dnx7mt cdhblgghoyphboytsbnp79mha5ocgihbk wm7pyhdbbbiqxksp0qc9welxkwdrrbqo6nuifnyrnvmuo5hvexkhndh1dxlbd3t5pxqpclooiop8wbl wyvdm8nrj2y28ebtrq3tivsel mmjsrithixl3mlap0sz31dxt1c my4jqcoc0gj7cad340 nvl5ccs8hx9t6g3f ah0f9uk step to reproduce see the log output and note the vue warn fail to resolve component fedistantlight message what be expect the fedistantlight should be recognize as a native svg tag what be actually happen the fedistantlight seem to be mistake as a component system info shell system os linux 6 1 arch linux cpu 12 x64 amd ryzen 5 pro 4650u with radeon graphic memory 10 55 gb 30 58 gb container yes shell 5 9 bin zsh binarie node 18 13 0 usr bin node yarn 1 22 19 usr bin yarn npm 8 19 2 usr bin npm browser chromium 109 0 5414 74 firefox 108 0 2 npmpackage vue 3 2 45 3 2 45 any additional comment I believe the problem originate in the domtagconfig ts which contain an svg tag call fedistancelight instead of fedistantlight distance vs distant I m not aware of a fedistancelight svg tag and believe this be a simple typo |
vuejscore | fix reactivity triggerref work with toref from reactive | Bug | triggerref allow force update the ref create by ref and shallowref but not the one from toref for example ts const foo ref 1 watcheffect console log update foo foo value triggerref foo trigger ts const state reactive foo 1 const foo toref state foo watcheffect console log update foo foo value triggerref foo do not trigger it s because the ref create by toref do not forward the dep attribute this pr fix it playground before enp9ku1ugzaqha8y8gaiegi7rcrsr1b16q2bisentju2tbly3ts2ju1bqrvwvhn pd zedymn0yupahsq71xyngn5ibvpxhndmyg7dl 1i3rj8yg0ymzhbyzooppj6sxkhc6 hr une eqmphekbemynuknvagwz7wqhsl r0hk6rut4bl9zpsywi ls6m8gys1ha8bqavsoxar16copzlem1tci03qd wpmwrhv5fn9hrg226aqt0oqvljiuouypfq7ul 93wzkfryfa1usq nxcebwmfcumcoaqu2naxdtwjzhoryviqddkqnp2rzzszveq2rpery2cer42qz qrirrsawveyg2uqxqxvvltynvxjwckygjwg8 hblcxbo2liobneefv9srulu8cknfrofmec77i6k3y0sg6xi7hgfixpsjlc1sej mx9z 3ad1vp4hp8emttcta playground after enqlucfowzam rurl3wiaqejiu1ler aoobste4wajpistumqv o09ex4millz9f3nu2r hsxdb0kdai8bvpf8bj6n1wgd05swfgigxs prv0aomunno9qhrfalp r7pjfadnx8gp8krrt5hgozsbyvwximjtgwnz 1qbosni1oyqmptbu5gwi8cbpgx6yuzp4uvyysmacykyvymzejncvujsyuj8svkkqzhaqtjzmxvsqfse4sbm4gqj0omop5hzwimzzyprl9 d5swn2mrwutnpfg6uajyuzydcwvq1hrycpgnjomcapqkpgkxzu9qjs 98zjtbik 2l6tyydwv174rx5rfqk430v2pcvevdv8utmf mp4jvgyihhj9cdaiumizm yvebx2pn0hipgo3x8uh2uklnsn5vkj9oeoeudgqytbk5z6vzo7yw4oo4wq9 jhdmjr2j7jdirp5zbauksmhoj6f ovwt uefziu8hpk8bzpfk |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.