repository stringclasses 156 values | issue title stringlengths 1 1.01k ⌀ | labels stringclasses 8 values | body stringlengths 1 270k ⌀ |
|---|---|---|---|
vuejscore | optional boolean prop give type ref which should be ref | Bug | vue version 3 2 45 link to minimal reproduction enp9kn1qwzamhv9f kybnda7dw7h2avsaxytpkqtev8goy0j n0npz9shfto50j6zj1zfiqgtxokwujy0hasrext2bo32oapwqyehwtoyftycevqxvr0nlx9qyoojc5rduexhevcg8ymissavcwofmt1l4i1ubar2wr5jn7xd bsbq6faeqni1m83lk0ex1kidzkxa4tq49rejoofkmaxbossoy22pe ryqgg7h xvbsnpaqqrdhqnrgfgj9xy3ybfzmu25bpeyky mogypkmxx 611memihcbvyyzc4 cpkl3fg3p fa9h5p2ldmebty vzzpu37twvc5azvmaifqf03c3tilv bp9 apuhswm step to reproduce here we get show type as ref however in vs code it be ref image 1 check the type of the boolean in autosuggestion as show in image what be expect it should have property type as ref accord to this prop validation the boolean absent prop will be cast to false you can change this by set a default for it I e default undefined to behave as a non boolean prop what be actually happen it be get type as ref where undefined be invalid system info shell system os macos 12 5 1 cpu 8 arm64 apple m1 memory 101 03 mb 8 00 gb shell 5 8 1 bin zsh binarie node 16 16 0 nvm version node v16 16 0 bin node yarn 1 22 19 nvm version node v16 16 0 bin yarn npm 8 11 0 nvm version node v16 16 0 bin npm browser chrome 105 0 5195 102 safari 15 6 1 npmpackage vue 3 2 45 3 2 45 any additional comment original issue |
vuejscore | variable declaration after defineprop be ignore | Bug | vue version 3 2 45 link to minimal reproduction dev enqdkutrg0aqx7 ksje0en27qbb66shq3rs9wb0tg tgdjuh8bt3vi2klbsqpf3n9zvhtulgxdookdkrb9surwkwygc vongts7mk9uoztj3tldiaqlvlabzamzpcs3p5q2htv9t5wj4diodvjinrg5ecy522lkksibbshqusgw04krkrnzaxyq9wjmtxbn04q3hgafywg0bjmawekjvqc9ynenwpppst3wexnxq6srzptsy0glm0evkg zvizfyif0nq7jzreoityoe9bfzr ovbstoysy8ytek x99mtalwzxhhdahlncfvlagayxdodmu0gdbgxwl6 zd225x794f92ungpd9phypl9 yv4e5tm9dg step to reproduce hallo should be show after world if you move defineprop after test hallo should be visible const test hallo hello defineprop hello seem like the compiler be ignore any declaration after defineprop what be expect hallo should be show after world what be actually happen hallo be not show system info no response any additional comment original issue nuxt nuxt nuxt js 12497 no response |
vuejscore | select box with v model update lazy when mount the component | Bug | vue version 3 2 45 link to minimal reproduction ssr enqtvu1v2zam suel0mb2m7xj4pnbot62mlao tki2ptitpbeiq5avdkv4 sytdpkyadeppex0fysaregzspo2wlqrkkbhtz5wangqdis7aeos61nmrbibjjguevbc5i5sxldbk2osqadgodk2yw8nqixmhj40mak32lhbixitfzke1oh7hgwszei2fycqaxfanpb lmxoipshzk6xyfsbowelxiwwshptus jksd2nst4 gvhhu5wm4k8ldf8clsu qkzqmqv9hanh2he7t4eexypncpjhgm5hmybyjbuwai5orozri5xt2vjrrlicki7djaz8mlupr9cj6nilczrgwg8dyiqy3r1huhctxiv6ly9bscmzsyecnub0tlrklpx hfohfx7rvpuhmwtqkiy2c jmtelb s8mdyjnigwjqfeztvwm14zui6qcfz khl5mawwum4ifzvhbvjs241ae7xn9 12cv2fhknfeuvhztphrrroyyi jh706o6lyn5hvipg6vxonxmopcmwlao2kl1nsclko79vgjhtlwcgor2eclramjmqij7xnpoe1ogo7vbxb1kahho6vrgah2ydoavfwe8pyio6sdvapa9q1sruzr c2r0vnsiopiftwi vyzw07w3yy8vmejpoj1568qf2cle4gs66tulh vccrlbnkmkrcj1dv ei 4bzhyrrruy8nuii6bbgzpbfasgodwg7kjget8wldgzovoofivcwzn4ekzrceuly4kj62m9rydc439g6kt6whucgo4ev3htkognrcmacn35d7tednnw4rc84df9vhk8vowqtof6zzplzybnopiaezz qe7d4lfszincsxrgr70z7rskh5tktitdywbiputthtyqvrexewna84amspjapqis9r2r 4moc76ades0s1bylnpypomay step to reproduce open link to minimal reproduction reload page what be expect the select box should show option c directly from the beginning what be actually happen v model be behave weirdly when a value be already set while mount the component in the following example the select box initially show option a then the component re render and show the correct option c however the select ref be set to 3 from the beginning accord to the output in the console when I m log the select ref vue when use the v bind directive and change everything work fine vue moreover this error occur only when use a select box other type of input field checkbox radio button text input work also when do the same in plain vue 3 it work 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 binarie node 16 14 2 usr local bin node yarn 1 22 19 usr local bin yarn npm 7 17 0 usr local bin npm npmpackage vue 3 2 25 3 2 45 any additional comment I also create this nuxt issue relate to this topic |
vuejscore | when keepalive cache more item than its max prop allow reactivate component may be erroneously mark as be unmounted | Bug | vue version 3 2 45 link to minimal reproduction step to reproduce follow direction on reproduction site click on create new page then click on the button in the blue box notice that it respond by show click do this 4 more time so that there be 5 page make sure you do the final click now click on render page 4 notice the click event do not get emit all the way to the onclicke handler in page vue click on render page 3 and the button work again what be expect emit should work what be actually happen emit do not work system info shell system os macos 12 6 cpu 12 x64 intel r core tm i7 8850h cpu 2 60ghz memory 20 04 mb 32 00 gb shell 5 8 1 bin zsh binarie node 16 13 1 nvm version node v16 13 1 bin node yarn 1 22 0 usr local bin yarn npm 8 1 2 nvm version node v16 13 1 bin npm browser chrome 108 0 5359 98 edge 108 0 1462 46 firefox 106 0 3 safari 16 2 npmpackage vue 3 2 41 3 2 41 any additional comment this be break by this commit if I remove the 2 line add if instance isunmounte return then it work once again |
vuejscore | defineprop doesn t support type prop with extract a native typescript s feature | Bug | vue version 3 2 44 link to minimal reproduction enqvus1u2zamfhvcf29ait8910dadeiaasuwwy66udbtklupqwksdznffztdom566suwsx0 qsl2nmvt0duhsozrz ujjuhgple3rnro0ji6gyivb2qgconutujigljqh3t3rpvlfkkjcxlvqkumjbbehyohz0mnfwc4yhaq1zqgegnahajzhrnmzxmixdhepzaqaw6hwuvd9grnossdmceb8jfwnxjpsfitvf7zh lpi9dk1gpubvq57ls4uhsr9qyx 1jcoeiqyinshstoukkryxdhwe4bo2purdlnv5zmmlxucw5 pgjm6z30yxs6 ehqus hmhbww1kuwz qxy7f ylwndymcjh4lzszrmdk8cfs qpiffljxfuxzcnqyunrxw7q huufyqtdjokqgrw4jkgm4c1rdq7deec51ies9waihiw7aar7tqr5sc16mfddbbvbypefx2wfb6fyyz3jpa2mjtih7bfj2 hw8ygidvqj ythq4wx5d8j8rahkgxtvu xp8 rbqok mqwihq step to reproduce 1 create new vue 3 project with npm create vue 3 command 2 create a component src component hicomponent vue with the follow code vue 3 replace code in src app vue file with the follow code vue 4 start project with npm run dev command 5 go to app s address the default be what be expect app run without any warning what be actually happen the follow warning appear in console vue warn invalid prop type check fail for prop secondletter expect object get string with value b at at system info shell system os window 10 10 0 22621 cpu 16 x64 amd ryzen 7 5800h with radeon graphic memory 11 73 gb 27 86 gb binary node 18 12 1 c program file nodejs node exe npm 8 19 2 c program file nodejs npm cmd browser edge spartan 44 22621 900 0 chromium 108 0 1462 46 internet explorer 11 0 22621 1 npmpackage vue 3 2 45 3 2 45 any additional comment typescript s extract suppose to return a new type which be a subset of type pass to extract as the first generic parameter it feel like for some reason defineprop doesn t treat it correctly |
vuejscore | root comment in a component will break transition | Bug | vue version 3 x link to minimal reproduction ignore step to reproduce when I add commentary in componenta like it it will not work what be expect it work what be actually happen not work system info shell system os macos 12 3 cpu 8 x64 apple m1 memory 46 70 mb 16 00 gb shell 5 8 bin zsh binarie node 16 13 1 nvm version node v16 13 1 bin node npm 6 14 10 usr local bin npm browser chrome 108 0 5359 98 chrome canary 110 0 5474 0 safari 15 4 any additional comment the link be enqtk8uo2zamrx f1sytenuz6cz1ayt9hs610crmq4etcrltjgjy76ue8eqx6kqayyvs5aesxp3f1rl6nlc0ogt7rx1tpngjs57ghx3dfg7ejrcqmxrf6eposlst7ipagjwmsy8hnq0ez2ka9qywbg2ffs4zvy6qyzokekxq85csbvbikzfxcedtsc8y9qnswiohufxcvcqpv jpmuvxocac3aaiy0tdof5x4gfm6brxewgdhh6xwqtewylgrkbb48azdwxjmhqmqe2fpdjanpk65p36hwvsyohdu4gfxpmgsvsdro1rffa9cm6kcmqnqrth3lkh5dsh1egjopuuwts5rpnegye65vyitrfonmrhhetwnis ylbuyp4cum1yjnmdasg2yj3aazrbs 01akqa31lb7onrvg88splv8lt4yync77qlsrbzmdwoxp0wrgfbpwxzfoiubl18mfkwv2msxw8if9qmcyd9npbbqk3 1fco9pmhpwknyaxevf0t0dnyimtxwmh4cuydezq9evt yj5in7hxe ovlbcu3s2bdnb plxv8xisqhz1ei69xpp69wveumlg4az7 sz9ifqm ey6 aw4c3h0 no response |
vuejscore | watcheffect within effectscope be remove when component be unmounted | Bug | vue version edge link to minimal reproduction enqfve vmzam yoel1kjknthq03brrtuu3ghqwl5lyrreto39fhd5ytao1r6exj2yvvnf7hvyxet82uhytyphlzava73pqqots0vukis3zujvyb lzmgifejdefa du4yo7qruzgumnvcqvd2ou60uvz udzac2qiwqolzlk wmrcbeeghpa ucuwt8wtchcuwdbjsbfkddiaj8pkuumfvrvsfk dltcnnqbrddpeju8k7qziamm1co4uipbgnqojwphruvzfz1kh56ingfh5ie2ypfpa5ask2njg09m57fszzpck6hg0xuijmmsclppk52 wcwp heftzkikkothbt r d xcyx57tdmmzr7n2 2fyzmymun510tys52nzznopgcrjwmwqzdeaxvzqbg kebs1nmavvj1wp25eyp1ssl0pulouwl2mgt8rxy0b 1tvylwegeubk47lo hni1fncogfeyxopbwg47ir3jzlqwfzrkbanpujxsvzndwmwwfmarjnysoeisk2j9p19hsnujvlzbqoar2pk4lv92ivy31pu56 g dsxsyepvdv9zvo g0vwjziu6p6uzxkbczyhk10pqnngkh gmofvkgfwx vpmya1fsieuad1qhaqc8cy8ont38igfbsdvj2hczrmvp20 yds6yjctmjg9h5ynl2o u cyheg800cfshv39aqwc a8z8yndoyco2f0jyugv1koq0e edptoydfwdmwk7xswecdcosw41gbuejvax5jznbttal qdgusmwgsvp xp3dxw step to reproduce click the negate button see multiple log untick the checkbox and tick it again trigger unmount mount of component click the negate button again see only one log what be expect watcheffect should trigger because it s inside of a detach effectscope what be actually happen watcheffect isn t run anymore after the wrapping component unmount system info shell na any additional comment from |
vuejscore | defineasynccomponent custom element emit not fire | Bug | vue version 3 2 45 link to minimal reproduction step to reproduce pull project locally npm install this install the late vue version npm run preview what be expect dist index html for both button to trigger console log what be actually happen a button that use defineasynccomponent be not fire console log system info shell system os macos 12 6 cpu 16 x64 intel r core tm i9 9880h cpu 2 30ghz memory 1 05 gb 16 00 gb shell 5 8 1 bin zsh binarie node 14 20 0 usr local bin node yarn 1 22 17 npm global bin yarn npm 6 14 17 usr local bin npm browser chrome 108 0 5359 94 safari 16 1 any additional comment this be intend for break large library into small file instead of load one giant file |
vuejscore | ts error 4058 in generically type composable contain ref with array of generic type | Bug | vue version 3 2 45 link to minimal reproduction step to reproduce the ts error present itself inside the usefilter ts composable inside the composable folder what be expect I m try to create a composable with a generic type t which inside the function create a ref contain an array of object of the generic type t this be the composable ts export function usefilter const datum ref return datum what be actually happen it throw the follow ts error as see in the reproduction link return type of export function have or be use name rawsymbol from external module stackblitz node modules vue reactivity dist reactivity but can not be name 4058 after a discussion on discord we find that the follow rewrite of the composable fix the issue but in a very verbose and unwanted way ts export function usefilter datum ref const datum ref return datum needless to say this would get very annoying when the composable have many more return property perhaps important to debug this issue remove declaration true from the tsconfig json file also get rid of the ts error but as this composable be part of a library that s not an option for I remove the default empty array value for the ref prevent the issue as well system info shell system os macos 13 0 cpu 10 arm64 apple m1 pro memory 77 06 mb 16 00 gb shell 5 8 1 bin zsh binarie node 17 0 1 nvm version node v17 0 1 bin node npm 8 13 1 nvm version node v17 0 1 bin npm browser chrome 107 0 5304 121 safari 16 1 any additional comment no response |
vuejscore | fix compiler runtime dom firefox do not support regexp flag s | Bug | fix 7267 relate to 6808 3917 playground enqljr1ow0aqhf9lucyg5xycaldkrkljdwiumfy6mbqf1d7zkwx53vk7cceokwdmd76z1qtroq6o9qpkdfeuiwee6ghd7ylyhhkyo1ig4 ihknpcbhuagfign05wwppb4hwdi aw2bu3xz0nlbnwszgijj5cnveuqhw p87z9rwslrg1ux2gicoofwzrhays3cqjkvp9rxbqukr7msqpfipsntdv xukq awoasna1dt1tlnsntjwiqxj02my48x ftw ky1xonunvoy04njenoyyhz9n5u1kzg45chk3mojyet3jpeelhirdj9irswrwtogfhn5 rfhx ok3yxyvhlj2y3nyi |
vuejscore | for statement in inline handler | Bug | js workaround html let x for x of state list log x output 1 2 3 click sfc playground enp9uf1vgzam ctwxkolsrttddfq x3lhlpmolpiisewsij fqza9ixvtzn7fhfxof68z oova6kufltgqjy53fg1q13xdaa4b7kukeiujfrysx8lbhgls4g4foeebyllrmmbwjqwdm8pqtwmmltm7fx b0yno4yzwverkfjcz2bi60axty3iioiodh0zm7cc9nu5xlrvlkg7q4mk2tvjiczl gqjlrnizy itjfbjrflccfwmyy8antkdupouqm8rpfnojztk1xyhtbv32sk4kzec3mx1eizkb 5gydfgbnqhsw 51qeqx8ufquboqowvuwe5bjhd0g4o5d4dkggblf7q0nlsktae9h0j6z7mh o 3fmznqr4bynjqkq originally post by jetlua in |
vuejscore | bug vue 3 hmr do not work inside a default slot use primevue | Duplicate | vue version 3 2 45 link to minimal reproduction step to reproduce I don t know if this be an issue with vue or vite or primevue but since it have to do with hmr I figure it must be a vue issue here be the step to reproduce the bug 1 clone and run the project shell git clone martinszeltin vue hmr not work slot git cd vue hmr not work slot npm install npm run dev 2 now open app vue and change the default slot of tabpanel line 9 then save the app vue file and look at the browser hmr do not work unless you manually reload the page all I do be take the vite starter template and add primevue shell npm create vite late my vue app template vue cd my vue app npm install npm install primevue 3 save npm install primeicon save then I add primevue to main js like this js import createapp from vue import style css import app from app vue import primevue from primevue config import appmodal from primevue dialog const app createapp app app use primevue app component appmodal appmodal app mount app and then I add the component in app vue as you can see from the reproduction repo I didn t change anything else something be wrong what be expect I be expect hmr to work and auto refresh the content inside the default slot but it be not work unless I reload the whole page what be actually happen hmr be not work as expect system info shell system os linux 5 15 ubuntu 20 04 5 lts focal fossa cpu 8 x64 intel r core tm i5 10300h cpu 2 50ghz memory 9 56 gb 31 26 gb container yes shell 5 8 usr bin zsh binarie node 18 12 1 nvm version node v18 12 1 bin node yarn 1 22 19 usr bin yarn npm 8 19 2 nvm version node v18 12 1 bin npm browser chrome 107 0 5304 121 firefox 107 0 npmpackage vue 3 2 41 3 2 45 primevue 3 20 0 vite 3 2 3 any additional comment no response |
vuejscore | ssr suspense the fallback slot be not hide after hydration | Bug | vue version 3 2 45 link to minimal reproduction or dev ssr enqvu01vm0aq svt7qes2wclzculvqr00lulvj1x2cdypyfztlvytsz e2exj4ctuoopfso8etpz5newn s6ojqonikxwnwltlhncsdji4n aphyilkvgwrlgwrbuxmcgywb3ebirfa0357pkheony4bbzvefcqtxqpbhdb53pgaysdyoklv2lturfprzzk zapvc9zjprrjipmpiqybjn7gx7mflih2siwfzfy05xiepfsnnkwseuh7kiom4hgfv3sl8bdnboezjkot6aj2exrvrbqflg13begd4pi49xi07qcfnvyvbhyyymqo03wpko5jdz0gpyr pkzx6pi4plu5 er8tycphixdna1pswepgexw6db g7rnhs4gqkbimp303hdu6jagpgownzoyv 3o7hpy7d12kidzaesnxasbfwj64nyjt u1o pizsnoep3cz8glvrrnqv043xulxvj08q0qwue jsj2uqdj 4rjxbh7klhmf6fil7w12crxq xtpmkd4nvoxboh59zvrqr7d9fn9pgwl23s9h2eplo9anu0qlljkvobpxnmlw ovxopr436arml7kzhre5f00emfmbilguf degcrd10hf 9zcukvb8xtr9rvh5zmv zjfytb 8s6o0j8ouvsipsrbaeirv3kuwgiyajsopolfcczp2qlbh dwa wijn voct5n jebzmeyungo6uk2r8aml9o step to reproduce open the prepared sfc vuejs org link or clone prepare github repo run yarn install yarn dev and open url in the browser what be expect application root component will be render on the server to dynamic client only value value I m content and will not change after client hydration what be actually happen application root component render on the server to dynamic client only value value I m content and then replace on client during hydration with dynamic client only value value I m content content loading as you can see suspense s fallback slot content for some reason it still show up system info shell system os macos 13 0 1 cpu 16 x64 intel r core tm i9 9980hk cpu 2 40ghz memory 1 19 gb 32 00 gb shell 5 9 usr local bin zsh binarie node 16 17 1 usr local opt node 16 bin node yarn 1 22 17 usr local bin yarn npm 8 15 0 usr local opt node 16 bin npm browser chrome 107 0 5304 110 firefox 106 0 5 safari 16 1 any additional comment 1 client only render if not html markup provide from ssr work as expect ssr rendering also work as expect the only appear during client hydration 2 an important condition for reproduce the bug be the presence of a dynamicvalue reactive variable that change the root component template locate outside the suspension tag in my project the variable affect the name of the class that I add to the container depend on the width of the current window but for the example I replace this with display the value of the variable in the template and I change the variable itself inside settimeout if you comment out line dynamicvalue value value then the hydration start work as expect |
vuejscore | don t suport ts4 7 0 instantiation expression feature | Bug | vue version 3 2 31 link to minimal reproduction enp9kcfugzamhl fy4vwkqbdguxatn2asrvkwqhp6ygtoyftqrz7dixq2qtmfmf 8x5m6hn55k q5wp3ffcuaaeq eglem81yp4rqpndqxkuqwqxuxnfixg0asy rltmipjk6zru91rfrplymp3xisbvbfdlsx4jhgwl4ylnxw5henpddlsibrmu0h6lsufzudsfawi1guws0j0mqnxlooagwsyowzrijknrdo9n5a i10um iabwvh1xj7eoi2mvj0cucek0va49oyofqa ewxgibzpi55ktv82pdravsxssdsjszpz2nl6c2tdmqzkzals67ekiq9j6f ghjwtmajlcw71vpdqna s1nfv9p xh1i zzklugoqmmwqw in7yfhlnawu1 mvi57jfjrjohi99j ph 405y afrjd jf8c6 step to reproduce just type follow code example in www typescriptlang org instantiation expression instantiation expression typescript interface box value t function makebox value t return value type hammer hammer const makehammerbox makebox what be expect compile successfully what be actually happen throw error syntaxerror vue compiler sfc unexpected token 9 37 app vue 7 8 type hammer hammer 9 const makehammerbox makebox 10 11 import ref from vue at de raise at de raisewithdata at de raise system info system os macos 13 0 cpu 8 x64 apple m1 pro memory 17 38 mb 16 00 gb shell 5 8 1 bin zsh binarie node 14 19 1 usr local bin node yarn 1 22 19 usr local bin yarn npm 6 14 16 usr local bin npm browser chrome 107 0 5304 110 firefox 100 0 safari 16 1 npmpackage vue 3 2 41 3 2 41 any additional comment doc for typescript4 7 0 instantiation expression instantiation expression instantiation expression and in my project there be error throw by vue loader too error in xxxxx vue vue type script lang ts setup true node module quasar app lib webpack loader js transform quasar import js node module ts loader index js clonedruleset 3 use 0 node module quasar app lib webpack loader vue auto import quasar js ruleset 0 use 0 node modules vue loader dist index js ruleset 0 use 1 xxx vue vue type script lang ts setup true module error from node modules vue loader dist index js vue compiler sfc miss semicolon 38 26 user hezhuohang workspace broctagon crm admin portal src page customer customerdetail customerbankcard form vue 61 62 const dynamicformref ref 63 type test typeof crmform 64 const f crmform 65 const formref ref error in xxx vue vue type script lang ts setup true node module quasar app lib webpack loader js transform quasar import js node module ts loader index js clonedruleset 3 use 0 node module quasar app lib webpack loader vue auto import quasar js ruleset 0 use 0 node modules vue loader dist index js ruleset 0 use 1 xxxvue vue type script lang ts setup true module build fail from node modules vue loader dist index js typeerror can not read property content of null select js 23 selectblock broctagon crm admin portal vue loader dist select js 23 45 index js 67 object loader broctagon crm admin portal vue loader dist index js 67 41 |
vuejscore | when use the deep mode of watch watchcallback will be trigger even if the value do not change | Bug | vue version all v3 2 16 link to minimal reproduction enp9uktugzaqvcrumxcvqkvuihkpiir1ajw68ybcjbdhj2xdfoi7d4xpg4lslfhm 4wf07nxrzourbzlms1mrr1ydk3ec1klryydhgwey7jkrqhikjtqrcmsbjgajwbf3bwxxbzkwgfcnmdncdhqhztgwacytfmwws8gh6ywbpvriqi17pa kxr502liqb trzhflcsthlqrhzrj4in6ovsi6smdbjfj4nhkgkpwenycsqzfgt8blxwciazwfgslzrqiawlkauir8qolq6gb3chdallqed 3y0tdkkv0g6s au64exsnt0ogwj0xacgxzygdxiwuvnhbghykpp5lzy0pr g2qpxy7dgjc84mz5fxhjsiay55yric4ot 4y3dje6yoonn6e dwczchm1erpozvzi2rfdypjusz1syk75g6 tvnfxoabtnu3ss h6ebalmkawvxjbjltbbkzzfrl0s y4zqcrxgikvozqbg7jeg y zrvoqtfl0usgnnwd2owypa step to reproduce 1 open link to minimal reproduction 2 enter some space and watch the counter change what be expect do not call watchcallback if the value have not change for example if watch be listen for change to an object in compute and the object s value be undefined for the next few change then watchcallback should not be trigger the current behavior of watch in the above case lead to some hidden vulnerability that be hard to debug what be actually happen when use the deep mode of watch watchcallback will be trigger even if the value do not change system info no response any additional comment no response |
vuejscore | fix hmr fix the page not update when use compute value as slot | Bug | 7155 fix 7155 I find that there be component library e g here l335 l349 that render component slot by compute wrapping and then render they dynamically in the template this can lead to a situation where hmr do not cause the page to update when the user change the template content |
vuejscore | when edit static node use in v for hmr doesn t work well | Duplicate | vue version 3 2 45 link to minimal reproduction step to reproduce 1 open reproduction 2 run npm I and npm run dev 3 replace good blog about in x vue with good blog abouta what be expect the follow content to be show good blog abouta changemechangemechangeme good blog abouta changemechangemechangeme what be actually happen the follow content be show good blog about changemechangemechangeme good blog abouta changemechangemechangeme good blog abouta changemechangemechangeme system info no response any additional comment if you replace x vue with the follow code and re run npm dev vue when you replace good blog about with good blog abouta only the second good blog about be replace original issue |
vuejscore | fix compiler sfc never skip function prop type | Bug | close 7111 |
vuejscore | proxy not contain a compoennt value on the prod env dev be ok | Bug | vue version 3 2 37 link to minimal reproduction dev enq1u0tu1eaqvurhjt1i7fymc6srpqrlawt2sgx6y yasch9uxd7clj8ec7cnbgc1w7hmcwgiijl5 r0e1wvnofondbzscdog w2mq12ynh1esdlk7qydgywuf dad1tbwxk90fav8okyys9uqjieh4v7vxtdvxvxmlycd0dtvsknokwbyg8abk x65t8fmzrn4vr7jmwzib2clwkhrxoqqiig udsmwpr7hnfe0zvupewfhvkgau4jhvodrkaxqxt7pqmmclzdrogodp6lu2verjckw hd8llgebwhk bwt4gmenc5pu2wsl rbiauuydduy6axrhwy1krcxgeb7ponq1vrtvmzwpf meq7ruompfqfgdnkhtgkjhcnbs0 yc56hxge1s5ipefi5ugcpnzmyesr vhrjlj egd9bzvpdxsp9mrizqk0jnzbb6byzobg4sydtlavpcevcyocxnjwjyfmtzca3 umtw uyy5ksonh5kcqoo8arqep 7rumzbfewxyj5rynnvxfums7qzdgq1yr5mmcwwr3amij7n5melycejhgackvkuubm0laub1mntokcvpaaam38rpi oihlqf9qohwnfmw1wv4nnkgqck73sh7vki5t850ure3zgv6yvm8x5xayfwdnibpsg step to reproduce common js import getcurrentinstance from vue export function usechild const proxy getcurrentinstance function fun name console log have msg msg in proxy proxy msg name return fun app vue child1 vue what be expect in prod env the proxy contain msg what be actually happen in prod env the proxy not contain msg system info no response any additional comment no response |
vuejscore | loop context be lose when render nest slot in v for use external component in ssr | Bug | vue version 3 2 44 link to minimal reproduction step to reproduce 1 open stackblitz example 2 navigate to page break ssr see it work in csr 3 reload page to force render in ssr 4 property row be access during render but be not define on instance what be expect ssr should behave as csr what be actually happen ssr cause app crash 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 16 14 2 usr local bin node yarn 1 22 19 usr local bin yarn npm 7 17 0 usr local bin npm npmpackage vue 3 2 25 3 2 44 any additional comment this be a weird one it be probably easy to understand look at the reproduction example when define slot content template in a v for loop the current loop element be undefined in that slot however this only occur in very specific case 1 page be render in ssr 2 slot template be define in v for 3 content reference the loop element be use an external component that be also use slot it work perfectly fine on client side or if the component use to render the content be internal part of the same project not pre build from a library additional context we come across this issue when start to extract a component library from our project prototype we have a dynamic table list component use to render a list of object base on a column configuration this component also provide dynamic scope slot for every column in case we want to customize the rendering under the hood it use our basic table component to render table row and cell after we move those table component to our new component library the dynamic listing suddenly break in ssr however I make the reproduction example as simple as I could and use a random ui library instead of our own code to make sure the same error happen |
vuejscore | fix compiler sfc analyze export default by ast | Bug | close 7038 close 7041 close 7078 vite plugin pr thank to btea |
vuejscore | keepalive with dynamic component setup hmr error | Bug | vue version 3 2 37 link to minimal reproduction step to reproduce npm install npm run dev editor src component helloworld vue const aa ref 1234 to const aa ref hello what be expect no error what be actually happen runtime core esm bundler js 38 vue warn unhandled error during execution of scheduler flush this be likely a vue internal bug please open an issue at at at at runtime core esm bundler js 6070 uncaught in promise typeerror parentcomponent ctx deactivate be not a function at unmount runtime core esm bundler js 6070 33 at patch runtime core esm bundler js 5054 13 at sharedcontext activate runtime core esm bundler js 2435 13 at processcomponent runtime core esm bundler js 5480 37 at patch runtime core esm bundler js 5085 21 at reactiveeffect componentupdatefn as fn runtime core esm bundler js 5695 17 at reactiveeffect run reactivity esm bundler js 187 25 at instance update runtime core esm bundler js 5729 56 at callwitherrorhandle runtime core esm bundler js 155 36 at flushjob runtime core esm bundler js 388 17 system info shell system os window 10 10 0 17763 cpu 16 x64 intel r core tm i7 10700 cpu 2 90ghz memory 5 56 gb 15 86 gb binary node 16 15 1 c program file nodejs node exe yarn 1 22 17 appdata roam npm yarn cmd npm 8 5 0 appdata roaming npm npm cmd browser internet explorer 11 0 17763 771 npmpackage vue 3 2 37 3 2 41 any additional comment I see this error mention but it be close please focus on it |
vuejscore | receive uncaught referenceerror sfc main be not define when use export and default string in one line | Bug | vue version 3 2 41 link to minimal reproduction step to reproduce bug description I receive error message in browser uncaught referenceerror sfc main be not define when I try to use component like this component mycomponent vue file in app vue file but when I replace default word in component mycomponent vue file with anything else for example component mycomponent vue file then all be compile properly and I don t receive any error this be happen due to this reg ex in node module vue compiler sfc dist compiler sfc cjs js const nameddefaultexportre n s export as s default s it give false positive when line contain any default sub string in it error go from vite code it do not add const sfc main to compile file in genscriptcode function of node module vitejs plugin vue dist index cjs file but it seem the root of the problem go from vue script step to reproduce npm create vite late vitejs vite jtwu7b template vue cd vitejs vite jtwu7b npm I touch src component mycomponent vue echo src component mycomponent vue echo src app vue npm run dev now check web browser what be expect default substre in string in line of code after export substring should not be parse as reserve word it should stay string what be actually happen it be parse as default reserve word system info shell system os macos 13 0 cpu 16 x64 intel r core tm i9 9980hk cpu 2 40ghz memory 11 93 gb 32 00 gb shell 5 8 1 bin zsh binarie node 16 13 2 usr local bin node yarn 1 22 17 usr local bin yarn npm 8 19 3 usr local bin npm browser chrome 107 0 5304 87 firefox 106 0 5 safari 16 1 npmpackage vitejs plugin vue 3 2 0 3 2 0 vite 3 2 0 3 2 2 any additional comment I first report this issue to vite maintenance team it seem they confirm the bug but ask to repost it to vue team since it seem that the issue on your side |
vuejscore | watch run while the component be be unmounte | Bug | vue version 3 2 41 link to minimal reproduction sfc playground enqvvm1um0aqfpxjxkwkymtlztlumyps20mbpal64ujhddjlltpdhesw9 ad8k55hc7uaizj4zqn2pnm55vvw9izd3u93tbi5myhu1xwbjsapl7foqxqqqzsqee6hfrjbzkhtlbwsoij1uygni yqrv4nlih25lgvaptwmg85whl2ygwqshthikskxg86fhgfjyr2mccuprpnugnru7g51i0sej4bboptmkuhhovir8j7uahg1xne4n0alj8aoyrat6nvexvlzebm4jzyvdyrd7nl7jl5h6hcv8ss8ijj2dnpivaab1tcbeni1niejvefbgug0xnchejsysqdjfwlu ucf2y5lnhms8eiu761jquy3bdcryyp2ck7bwuposykeltymdglocyadskxcw5hq cajeycmc68aaovqohoofbv9thcjwe8k7bza6i4xzmptj5d2cmn5dmwu pehzi2rxzokv2uqawmc81 wunxgysxc dczq91ropfohknsjg9ssbv2x8x5lsi7jnymuetfyrn m4p9z 1ovseazcglixch u 9ahydt4aucmu2hpu3rzg59nudncy8iws9v 3y xtrsdp7oichkqrte0bf3m042wggr282nmzsk5qm 1kylmzoaemcxcnfriyvynefbxtmd09h xjd7zgdmsukpakssdzhkvo hw5fevukp3aaxk1tgv ah4jsruyzn6tivg ibukm x eyussnyg325myh0v5qlajnblx8zuh5wq5dwp9a9n567orkdtx8bzlpqww step to reproduce 1 click user b button 2 click user button 3 check the console will show the i d undefine what be expect the behavior should be the same as user b to about simply destroy the component without trigger watch what be actually happen the behavior be the same as user b to user a to reuse component instance and then trigger watch trigger watch again before destroy the component instance 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 bytes shell 1 0 bin jsh binary node 16 14 2 usr local bin node yarn 1 22 19 usr local bin yarn npm 7 17 0 usr local bin npm npmpackage vue 3 2 41 3 2 41 any additional comment be this expect behavior it seem annoying to need to add a condition of undefined to the watch callback not sure 2291 have fix the problem I will be grateful for any help any can provide |
vuejscore | template ref with conflict name work in dev but not in prod | Bug | vue version 3 2 41 link to minimal reproduction enp9uctowzaq bxll4lu2apwikjvhiq4inh1jtsbb8qprz0ifoxfwsehkkh05t2z3vnpdpzboxhsgwc89wdsxwaequ92yrtawqzs0wrhkrsabysmrarvlmnlzccmfqg064oavdgwtzpa1 ekp1mr c6fjgnm5ynjt3ywshthxlu3ho4y4rxaak94xqzo7jfsrbvvqna k7i37qmwb6vlnjcjvqmthqs0en8rbsrdksvwh o ak tn7sfhpaufd elzfupaimckyeblwotul elxhf0sj5qjmsab8 pm qndqni4jdbbr2hx1rp4qev81wqqmx2yknw5ynhrwnbuywejx rdynhmeten3hd13dyfc3050sand1cejer5pkpx2vw26srs8ruspmwx step to reproduce create a component with a template name the same as a prop vue run the app in dev build the app and run in prod what be expect it should work or not but it should have same behavior between dev and prod mode what be actually happen it work in dev mode it doesn t work in prod with an error msg be not define make it a bit difficult to debug system info no response any additional comment no response |
vuejscore | transition appear flag doesn t work in ssr | Bug | vue version 3 2 25 link to minimal reproduction playground without router ssr enp9u01p3daq ssjxwcjxnuqhypdufcvkpeqvcxrfydmgmliw7ytdrxa 95xhlwlcg4znjdvvp73bgntoy3ikrb2jvm2gmcw2muh1wcnc3brbotwmqhosh6dcd l4u1txpdjs cssaf ipvepp3ffg4lmigeboz2ax4ygmruaa5owoex2evetanugjiagum6hs8vyc80hnpksfyjuvjcxuid0guepqe5yak42f4gja9gfa m2sczhkmg3u9nr5p v4klaojd383gmifaaqeeoye1v3mz0lqulofmcjmnqzqnvtyiymcplpxik1riqac1p muxb92fttlqsaodiwkpux4ob 0kcdcxtjcqmatwfjzqlcdtx5qevw2b wekd7hlceyxlhkvbbkkbtipql2ydjji0ha8tebtakzc8qs8ijvisw 0y2jl9hdcnzxnpu2idj49kvxhserdkmoihsffihqz548oiiwjbrlhjwej2ryob5hh 4jzlfqn7yrlmy60cjpsqyz3ghkkepd00sft9j2uc06iog6k2rswff5tskflaqiw2uoqtlqkjoytoucaav2w3wbuyu 5gsa29 budp5ufnwrdcplqx8gszuk 5v8vf p6w00dujp xrnhooezwh2hkvyy step to reproduce no step just load the attach live example and reload the result frame if need what be expect there should be a transition when the component be render for the first time what be actually happen there be no animation the component just appear system info no response any additional comment no response |
vuejscore | v bind css variable crash during ssr dev | Bug | vue version 3 2 41 link to minimal reproduction step to reproduce yarn install yarn webpack yarn watch visit localhost 8080 and server crash with vue warn unhandled error during execution of watcher callback at vue warn unhandled error during execution of setup function at referenceerror can not access paddingtop before initialization at home stephen project vue ssr css bind dist server js 14760 73 at setvar home stephen project vue ssr css bind dist server js 12565 58 at callwitherrorhandle home stephen project vue ssr css bind dist server js 6047 18 at callwithasyncerrorhandle home stephen project vue ssr css bind dist server js 6055 17 at getter home stephen project vue ssr css bind dist server js 7266 16 at dowatch home stephen project vue ssr css bind dist server js 7286 7 at watchposteffect home stephen project vue ssr css bind dist server js 7207 10 at usecssvar home stephen project vue ssr css bind dist server js 12566 69 at setup home stephen project vue ssr css bind dist server js 14759 52 at callwitherrorhandle home stephen project vue ssr css bind dist server js 6047 18 what be expect no crash what be actually happen the generate setup function seem to be reference paddingtop variable before it be declare js harmony default export const webpack default export name app setup prop expose expose 0 vue webpack import module 0 usecssvar ctx 7ba5bd90 paddingtop 0 vue webpack import module 0 unref paddingtop const paddingtop 0 vue webpack import module 0 compute 100px const return paddingtop compute vue webpack import module 0 compute object defineproperty return isscriptsetup enumerable false value true return return system info shell system os linux 5 10 ubuntu 20 04 5 lts focal fossa cpu 12 x64 amd ryzen 5 2600 six core processor memory 12 60 gb 15 60 gb container yes shell 5 0 17 bin bash binary node 16 15 0 usr local bin node yarn 1 22 19 yarn bin yarn npm 8 17 0 usr local bin npm npmpackage vue 3 2 41 3 2 41 any additional comment work fine without ssr workaround in the |
vuejscore | prop definition mutate reference object by add array index | Bug | vue version 3 2 41 link to minimal reproduction step to reproduce look at the console of the codesandbox to see the log and what prop have do to the prop object create a component in the script tag create variable and assign an object to it in that object specify your prop in your component option api for prop reference the variable console log the variable and notice that vue have modify the object and add array index to it now this object be useless because it can not be use in other component for define prop what be expect vue not to mutate object because this stop it be use elsewhere what be actually happen vue be mutate an object which it should not be do system info no response any additional comment no response |
vuejscore | inconsistent behaviour between update modelvalue and update model value | Bug | vue version 3 2 41 link to minimal reproduction dev enqvvflr20aq iudcjectktspslosb9a6etbagkfqkjka osoz3yxskjrv 9s7osfmtuqsdwxn9c3 wmeqd12jysyqo5xrquhvjmgn1tsc60mg5 mfjrzudekafxmvwyd4php2 s2x2uungj26jphufxdrh2p8f 5dlxlkhxhwq3geiulbqixfldwfxomgy8vzac5rct8rn xxovbcu68wqrbosdsewt3uuh51nodbtcwtgh69ixladmfw pa adbx4pwjtnaeojclookszyuylz2s04tepenlsuioedfth5ys0wk8fzguthic 0u6eqvqnijwfqsxvfp4vlhsr uzekbqvjw1jyih9wcnnwyqhc 3wxstsi6gp3yvqkzia7tfp5swzllz6yf5umkrfpwngzxboil3aau4xrotx8u ybt50uupqf7erhy ekl4v5dwsivufzuixoegwgtewp07vvejljoy96a0jhsf0uiusll4vowtnsissaqr9x6vkj7bztmwmk44jnkyvu36rx6dtlrny6xx3krjgujhqyyoc1whozevamls0zu8nkxqwzf0x24lux8md2kqnpicptcaa7t3xkimndad9uviuk3xpjamthnigceb kfym wpdse16k0qy4ndqlc7hiyjaspq o6d20vkrrgmiynbwbt4zbamij hrnhxcqmol bhtdyaknfxecz6xles9pizy0s1agz53dpx4gq2pewqjdzqdlqsibrgmt2zh dcnlnbq8falupw7 v6lttzjxrl vemued2pqexrs8jn nyz4f4xsv6lppvs hdyoaxqygbolvfa6hsigck3ibqihg1zfhgvzekpmaa1wyd3yet677rtli4robbmmxrhdert8r8mrfoze6pq3rtijgsix95ig1fy5hwnkt7q te43ozdzaa step to reproduce the link provide demonstrate the break behaviour the blue wrap input element do not have its value bind whatever you type in will not update the bind variable to fix this in wrapper vue change the update modelvalue reference to update model value now the input field will have the value correctly bind and you can update the value from the blue text input what be expect wrapper vue be pass back slot property one of which be update modelvalue however in app vue when the slot property key be dump out it can be see that this be translate for some reason to on update modelvalue which appear to be meaningless as it never trigger it ought to be convert to onupdate modelvalue but there appear to be some kind of specific conversion go on that only affect this string the proof be that we can circumvent it by replace it with update model value which correctly get convert to onupdate modelvalue and get bind register activate properly all other event property be correctly convert to onevent equivalent I e click convert to onclick etc what be actually happen there appear to be a specific replacement happen for update modelvalue to convert it to on update modelvalue which vue then ignore it never trigger system info no response any additional comment I be attempt to render some input element via a wrapper the wrapper accept a field and various other parameter and generate lovely html for display as well as provide v slot property back so they can be pass into the input component itself which be pass in as a slot part of the slot prop be pass back be workaround for implement v model I e modelvalue and update modelvalue however when you look at the property name be return in app vue we see on update modelvalue instead of onupdate modelvalue and also the update event never get catch when this be change in wrapper vue to update model value it s correctly pass back as onupdate modelvalue and work nicely properly incidentally I discover this when I be convert my app to use webpack preprocessing prior to this I have all my vue component accessible in a public directly and import on the fly via this library I e so the browser would directly request transpile and import each component individually this code work perfectly with that it s only in preprocesse via webpack and or vite and sfc playground that this issue come up |
vuejscore | resolvedef function access prop but it be undefined | Bug | vue version 3 2 40 link to minimal reproduction step to reproduce 1 npm run dev 2 check console will receive error uncaught typeerror can not read property of undefined read datav7a7a37b1 at resolve2 vue js v f51652de 7665 28 I be not sure vue version be 3 2 37 I console log the varible in debuuger what be expect webcomponent can success render what be actually happen in runtime dom esm bundler js resolvedef function prop be undefined system info shell system os window 10 10 0 19044 cpu 12 x64 intel r core tm i5 10600kf cpu 4 10ghz memory 4 34 gb 15 91 gb binary node 16 13 1 c program file nodejs node exe yarn 1 22 10 appdata roam npm yarn cmd npm 8 1 2 c program file nodejs npm cmd browser edge spartan 44 19041 1266 0 chromium 106 0 1370 42 internet explorer 11 0 19041 1566 npmpackage vue 3 2 38 3 2 41 any additional comment no response |
vuejscore | keepalive root text node fail to execute insertbefore on node | Bug | vue version 3 2 40 link to minimal reproduction enp9uu1vwjam stelh0sbe6otjt23o1jlqw4jdb8kenljtt pqfpggnst4nt52c vyt7s7yyemqbvvrasrvay jti9bswemcxmfhaym0zijicjrdsh9f70fzhezswec48heiqojaae mr3obber5dq7hvayupi2jqrqevlaralieuo77eiyg17qt9xkr2nz ff bjgzazrrthxoep4bufea0edxjizfr5mfnizfnzcyy8atnf alv23c1izjzfvli5m3mm50nwtnbs ybqzmzjhogat2dmh6dee qemltr4wrux0k1yvg1ryoff53pmlr0fegq3vodglb3s5q31ah26j8wh6jzfsjkkpjoxomkeroat0s3ejepzt 3u04geyhc2y1zkbo0lsu0pt 0awkhpalk6l etc3dgfzum31mzivq step to reproduce 1 type something in the 2 click the toggle button 3 observe error what be expect no error what be actually happen error in console render update fail fail to execute insertbefore on node parameter 1 be not of type node system info no response any additional comment happen in both dev and production mode seem to have be a problem for a while it isn t new in 3 2 40 the root text node in the child seem to be require to cause the problem if you don t type anything in the everything seem to be toggle fine I assume some internal state be get change by the first re render that break the second re render |
vuejscore | fix compiler core keep whitespace with newline between interpolation and comment | Bug | fix 6352 track 1c0a2c6 playground enqtu8uo2zam bwulmmbly30ucwcb4deeumtqc 6kbadulaeeomkgef l23naxrb9le9werqnblahnshlipjj2qjkqpzmxgiuu9be1qfymyyigmdizq5elhj6coee oyimhthp4n m3qi3zdhc8xd 5h9daeqlzassmjgh3qlkneabulg7znjfiznqs faf2ns93rzfud1rd5wpcdrt4eq7gmbnyaqoqw3r7cynshjdvkqeskk6zcqna64xqtueoo0v0bnq rmfundf8ososhobz2jhkmn0vpcectdhfkpodqtt71spaz tckfuconqpgag2psebiwyzvt2j4rnimdohndjg5ipjnwaoaotqh4 orhoabi5f6xeh yw7ptimwzrrrx ncmrzwilrtof jejl2f2uoyd4mf jp9rzvflmy79is239f3x3g38ojcqvo2seltljmpvu gvypathuayc0bgbwdotdnz3sk26sccafowdlmxzzplplz40u f3j1plvwamlolx3mfyx9cezc7tjkxnqvs4cl3gvupbzlxuxxphfnojzqi5dgnavwo4ezqdw |
vuejscore | return value of ref import from other path isn t setup ref | Bug | vue version 3 2 40 link to minimal reproduction enp9km1qwzaqhf9l0cujxbjpb8y29d10sd2142d9of2nben378oopbsqm3z29lezi3qlud9nvjwqqutjzcdkobbwjy6gxlbawh5w6fnwugjdskyzcuu74inb0qbn9hyouxqm1fmydriqpty7voaymlo4xrhlaqiv53zznsc61kambp xqjpatyjdjeobbs9hlvmjfsziqgo2jwusis9wxzkjvczq3 von9ihduzeos2er4cayzxvkxwsjgfbdfrfmclemzuj qcmtm yf6z ubm7wr9kledtegg tl739nk3dryo0lrqnf9ec7v a9njiki step to reproduce open reproduction and make sure it s in production mode the page be empty then switch to dev mode it show 123 and we could see analyze binding ref setup maybe ref msg setup ref it should be setup maybe ref what be expect msg be setup maybe ref what be actually happen msg be setup ref system info shell n a any additional comment no response |
vuejscore | wrong ref return value type without initial value | Bug | vue version 3 2 40 link to minimal reproduction code jywwdg9gtglgbabzlapgmzgxzmqerwdkabgk4qecwaukjlinacsoba75fkod0iahggm8azyruaphnab20aqbtk6goigyr8nbahwavmrqaetvgaya5gd4afaepj0um7iawakdwf3abk6ezdowcaa ckqyacbo5ijhvjsq6iiqcigadaoqfjbaekne arkqtaqamr 5ll2dtrslvx1hs4a8gbgafyogvdaincqiilarqoankrhkwjr4yspngbmakwazas18bxsqeiwwmtamop braucajgvct fd6zkx adb2jg1nprv7kabqd8b cmum9kly4abacgbnqazjpdjzw5qyplcqwew1oond6eqay5m4ahk6fbqpbqeqagjgrvinzucf6oqiurkmtgp3ccaa7safeoucbdhyzhbsetgakoge9iauo8cfuakiadzaxxgpzfzogac44g1ot1gx0bkmruncjnwte5otvusaea step to reproduce open the reproduction what be expect const bar ref bar be reactivevariable undefined what be actually happen const bar ref bar be reactivevariable system info shell n a any additional comment no response |
vuejscore | unicode variable name in v bind of style will be convert to | Bug | vue version 3 2 40 link to minimal reproduction enptku1oheaqha9s6q0zicaegrpv0rt mpme0d pajatwgi3hkdjfvwy9yyupqrgc9gnamyju6r6hvr7er251tpqg0yskmjhulaazdb6hkoutdiwojcsgh4qowqethpqswwhjfpgcl9zpmdoazabywww wvf72 fzw rabxex fjvh8ch6dvqwuy fmscbygatx7do7cypnqdwaz32xa8hakokpcuzjrersrwl9rpl t pxdmai91x4eyfv56vwaukhamqtamoey3cw5t9drca66zs6triv os64n0jojsgvmssiraajiyrpsprs0qugjqkshilx1fidkoo1gpm4xqrw1r4xumyfuykyjbrcsiihchoj7paz92nklpd70v8anvrauq step to reproduce 1 declare responsive variable in script with unicode variable name 2 use in style via v bind what be expect js and css variable name both support unicode variable name so there be no problem compile directly into unicode css variable name css var 472cff63 english var 472cff63 var 472cff63 var 472cff63 fran ais what be actually happen unicode js variable name use in style via v bind will be replace with when compile into css code then variable name with the same number of digit will be convert to the same css var 472cff63 english var 472cff63 var 472cff63 var 472cff63 fran ais system info no response any additional comment no response |
vuejscore | dynamic v on and static v on should be merge first be overriden | Bug | vue version 3 2 39 link to minimal reproduction enp1ustuwjaq jwtlwejyvwkaupdlfof7ahuisqbcpjltpmeovx71wklhiqbd3zmvk opvubtg2ydct84wobwgno7e7owlnjantgsiiekmcujernhba6mnohup4a25hfjo8opyfp42t5kcwnsh6c80tqhayw ku2bgoljwx3ealgyirnyzfe3jkf5f3kigsfuopksr nmtej5wldobwahx5siqfrjp0zb3nzl3natxz1oa sqrlvvaolubt9lgowgcnlsytzt7pprmqfm 7 htmsokrojhmffwllyscgmpkiliekb0fd103lkhvm07rgnbanttyel rcivysadbcfcmrekicsh imvtnlyxga zml6h3kyywcvoslwmlrh9mvflxwzfxrtzq9ymj280xdbqsjgnslizhxaxuqcyc3ymwfon574q4j2efgrcgdmrdy0otciuvvrvnfnx6mhysnwvbyewrbd2qet0so3c97yh vontjt4nvw u9cxqg step to reproduce add a static v on follow by a dynamic v on vue what be expect onblur be call even if validateevent blur what be actually happen onblur be not call system info no response any additional comment no response |
vuejscore | different behavior in development vs production build | Bug | vue version 3 2 39 link to minimal reproduction step to reproduce navigate to first page and see a element render click on the link to second page in the page header and then click on the link to first page in the page header what be expect only one element be render what be actually happen in a development build only one element be render which be the behavior I expect it be also the behavior in vue 2 with option api see the option api branch in the minimal reproduction in a production build however all previously render element remain visible system info shell system os linux 5 15 kde neon 5 25 cpu 4 x64 intel r core tm i5 4590 cpu 3 30ghz memory 10 73 gb 15 54 gb container yes shell 5 0 17 bin bash binary node 16 17 0 volta tool image node 16 17 0 bin node yarn 1 22 19 volta tool image yarn 1 22 19 bin yarn npm 8 15 0 volta tool image node 16 17 0 bin npm browser chrome 105 0 5195 102 firefox 104 0 firefox nightly 106 0a1 npmpackage vue 3 2 37 3 2 39 any additional comment x ref |
vuejscore | v for ref behave differently under production and development | Bug | vue version 3 2 29 link to minimal reproduction dev enp9uj1v2zaq sshlpybixtiqa4cpeohau3steygsmexlb9ausog6l nsmwjkwbzhpt67 huawzfvoftioza2tgh5rnetkmh3dnzubiujbutvhnvqoizap5qcpahg23coybegt wamiqlbowwck4axsi3ugrbe9stkavfy4zxv26qeg2hv3v7utbjtq 8rqvi2vvwaeqtnc8g1lagmh1o0gbedcmxyckvhm1wgzvxjtf02fwd3ztwxugij6foj0ij16rhqtdfbp9njslauhe lsg08y1gtcgnjqnxltzdxnmylrwcy2z2 0ozjytwi9ij6oepr3ueligmm8x9llkvb11qvokfuznyqw6d54bzct7jcvhecpmyleiizjburmsxmqhtcrnvhtevjyls5qt9jwm8 xfdjbmlssrc2kq8egyrmrkxm4l 5usjwchruv nzk5le6pjwjzogw2gzp3e37l95 eqk 9rnompvkt3epeqiqs1vfkgor0szqb7yabw4dib2zfcb7pvrmt9pavbhkevnz6na step to reproduce 1 click anywhere on the preview 2 time 2 change to production and click again 2 time anywhere on the preview what be expect on each click one element be remove from the list the itemref variable should also be update with the correspond number of element what be actually happen under production everything work as expect under development the ref array be lag behind after one click the list have 2 element and the ref array still 3 after a second click the list have 1 element and the ref array have now 2 system info no response any additional comment every 2 second the itemref variable be print on the console there you can see that it be actually update correctly after each click in both dev and prod scenario |
vuejscore | onbeforeunmount not trigger callback | Bug | vue version 3 2 39 link to minimal reproduction enqnustu2zaq jutl5kbsesbuw1zcb8o0hvaky62tljziw w4tqw9o9dio7qkkgrmzs7njndnqv7zex5dsjwrpiozbdzwdckonoh77wcbtui9rrpmnehw4anqx mj4qnhtt8rusd50l01cjct hepvzyqlb8hpd xwuf8edqb0oikezbdxew2mmivdusmjkuzawjo eljz rl5ubgtvq5tzmircjnlm3avdrra q9ykmsobzfvziu7 m po gef 9w0cngqpz5lvmdyx5ketoll cvrsuiymmnqquyevehthyf 8bdvteudxnqzntowy15fuqcruufxkltsvtffmhvp io h8lv6ik8xe6kehlhqbdnddzgk8oy0sqg4t2v klxr evzuxohgtvresat4xvzlojj6o53zqmpqwaapigjdr4r4gk0nqvj4gjgxwcirthttqolzicipawjskh7d8nasapuze23xr3r em4uij uqdmaknsztng1nmozugrrqcyd4 antbq7obbtdbn2gg1khvc3lpk4ginwkjnsypsfunina9xxkjoxmx8u43yvssjgg7qq 18ras3ebyapwpg72namft5qurgdfel3slpuikjqpgnfwdsdwiu step to reproduce import a function from another file in a component and pass it to onbeforeunmount hook directly without create an anonymous function what be expect every time the component be unmounted it should call the import function what be actually happen it s only call the import function the first time the component be unmounted system info no response any additional comment in the reproducible example there be a comment line show what I need to do for it to work create an anonymous function onbeforeunmount myfunc onbeforeunmount myfunc |
vuejscore | referenceerror be not define in production build while mix | Bug | vue version 3 2 39 link to minimal reproduction step to reproduce yarn serve mode production open in your browser open the browser dev tool console tab try to change something in any form field what be expect the underlying form datum should be update without any console error what be actually happen the underlying form datum isn t update and a console error appear referenceerror thing be not define system info shell system os linux 5 19 arch linux cpu 8 x64 intel r core tm i7 8550u cpu 1 80ghz memory 9 15 gb 15 37 gb container yes shell 5 1 16 bin bash binary node 18 9 0 usr bin node yarn 1 22 19 usr bin yarn npm 8 19 2 usr bin npm browser firefox 104 0 2 npmpackage vue 3 2 33 3 2 39 any additional comment the issue occur only in production build everything work as expect in development build the key here be the |
vuejscore | watcheffect should not have side effect on the response in emit | Bug | vue version 3 2 39 link to minimal reproduction enp9u8go2jaq zwplwlqikf7kg2iqklqoycekvxiszazglujbdkoqel59x07lgrziztn3sw8z pzmx03jj 2yfascjwvxond35unuliz2no4g8ugbmis7ich0uqk dcduerzhoiwiwchkq2ch87tyr3a0 qntq2gv9q29adkfkpk919v0psq8lir0comanfjnc7glbtat6owdrish8u2x5aqt6x0opaev4lwokwtrdfhyn9kh7r3qc1guvgszsqbt166xu38gzzcduivfnyydqxai9gxhikcka7lzfkcfxigglmus1kz3snx3uka27vghas2qlglbfw2a4gtjqsdtrevoukcx6lyxkyp511p8n9ok3qhulu4ae6w1ahgyjg8irbs4l1xk857zv72obhylwhc9sqtdvnad9un ev 9jxx0vlppkfxzz tpjm0xchynhnokxleo7eoarroh5ld1b4jvmm kazoeogbbhjzzsmh1thihbtoepcfp2vwkn112dunvv7om6p1mntsq08602i7eb6 08wftdk6jphkcepgjhnf9wud6bvp9nhfpuddlnmt5q3ep8lduzlduc5ty1o84kq8fiprezo8cuzz7z39l23vyuqfbdzdxdtgkfghslnww iltyl9fgy8 m dwcqswyko step to reproduce click the error loop button and you will see that the program enter a dead loop which will loop once per second because I add the delay I m have a problem use emit in watcheffect and the program go into a dead loop the watcheffect collect the dependency in the emit and the dead loop be trigger as a result I would like to know if this be a bug or a feature what be expect personally I think it be a bug because responsiveness between component should be isolate by prop and emit otherwise it would be very complicated to troubleshoot what be actually happen which cause the program to enter a dead loop to be more clear this discussion have nothing to do with recursion the topic of this issue be question about whether watcheffect should listen for response in the emit event subscriber function |
vuejscore | fix ssr avoid ast helper duplication | Bug | fix it be introduce in out of scope of this pr but should we consider do some unique normalization for it to reduce maintenance burden or even directly change it to set |
vuejscore | uncaught in promise typeerror oldbinding I be undefined | Bug | vue version v3 2 38 link to minimal reproduction step to reproduce not sure happen as a result of navigate via vue router this be the stack trace uncaught in promise typeerror oldbinding I be undefined invokedirectivehook runtime core esm bundler js 2779 patchelement runtime core esm bundler js 5349 flushpostflushcb runtime core esm bundler js 339 flushjob runtime core esm bundler js 393 promise callback queueflush runtime core esm bundler js 280 queuejob runtime core esm bundler js 274 scheduler runtime core esm bundler js 1803 triggereffect reactivity esm bundler js 394 triggereffect reactivity esm bundler js 384 triggerrefvalue reactivity esm bundler js 1000 effect reactivity esm bundler js 1134 triggereffect reactivity esm bundler js 394 triggereffect reactivity esm bundler js 379 triggerrefvalue reactivity esm bundler js 1000 set value reactivity esm bundler js 1045 poll vimg tsx 166 pollforsize vimg tsx 176 init vimg tsx 136 promise callback nexttick runtime core esm bundler js 242 init vimg tsx 126 observer index ts 54 mount index ts 33 callwitherrorhandle runtime core esm bundler js 155 callwithasyncerrorhandle runtime core esm bundler js 164 invokedirectivehook runtime core esm bundler js 2786 mountelement runtime core esm bundler js 5222 flushpostflushcb runtime core esm bundler js 339 flushjob runtime core esm bundler js 393 promise callback queueflush runtime core esm bundler js 280 queuepostflushcb runtime core esm bundler js 302 queueeffectwithsuspense runtime core esm bundler js 1574 scheduler runtime core esm bundler js 1796 triggereffect reactivity esm bundler js 394 triggereffect reactivity esm bundler js 384 triggerrefvalue reactivity esm bundler js 1000 effect reactivity esm bundler js 1134 triggereffect reactivity esm bundler js 394 triggereffect reactivity esm bundler js 379 triggerrefvalue reactivity esm bundler js 1000 effect reactivity esm bundler js 1134 triggereffect reactivity esm bundler js 394 triggereffect reactivity esm bundler js 379 triggerrefvalue reactivity esm bundler js 1000 set value reactivity esm bundler js 1045 finalizenavigation vue router mjs 3324 pushwithredirect vue router mjs 3197 promise callback pushwithredirect vue router mjs 3164 push vue router mjs 3089 navigate vue router mjs 2182 callwitherrorhandle runtime core esm bundler js 155 callwithasyncerrorhandle runtime core esm bundler js 164 runtime core esm bundler js 2779 12 invokedirectivehook runtime core esm bundler js 2779 patchelement runtime core esm bundler js 5349 flushpostflushcb runtime core esm bundler js 339 flushjob runtime core esm bundler js 393 async promise callback queueflush runtime core esm bundler js 280 queuejob runtime core esm bundler js 274 scheduler runtime core esm bundler js 1803 triggereffect reactivity esm bundler js 394 triggereffect reactivity esm bundler js 384 triggerrefvalue reactivity esm bundler js 1000 effect reactivity esm bundler js 1134 triggereffect reactivity esm bundler js 394 triggereffect reactivity esm bundler js 379 triggerrefvalue reactivity esm bundler js 1000 set value reactivity esm bundler js 1045 poll vimg tsx 166 pollforsize vimg tsx 176 init vimg tsx 136 async promise callback nexttick runtime core esm bundler js 242 init vimg tsx 126 observer index ts 54 async intersectioncallback mount index ts 33 callwitherrorhandle runtime core esm bundler js 155 callwithasyncerrorhandle runtime core esm bundler js 164 invokedirectivehook runtime core esm bundler js 2786 mountelement runtime core esm bundler js 5222 flushpostflushcb runtime core esm bundler js 339 flushjob runtime core esm bundler js 393 async promise callback queueflush runtime core esm bundler js 280 queuepostflushcb runtime core esm bundler js 302 queueeffectwithsuspense runtime core esm bundler js 1574 scheduler runtime core esm bundler js 1796 triggereffect reactivity esm bundler js 394 triggereffect reactivity esm bundler js 384 triggerrefvalue reactivity esm bundler js 1000 effect reactivity esm bundler js 1134 triggereffect reactivity esm bundler js 394 triggereffect reactivity esm bundler js 379 triggerrefvalue reactivity esm bundler js 1000 effect reactivity esm bundler js 1134 triggereffect reactivity esm bundler js 394 triggereffect reactivity esm bundler js 379 triggerrefvalue reactivity esm bundler js 1000 set value reactivity esm bundler js 1045 finalizenavigation vue router mjs 3324 pushwithredirect vue router mjs 3197 async promise callback pushwithredirect vue router mjs 3164 push vue router mjs 3089 navigate vue router mjs 2182 callwitherrorhandle runtime core esm bundler js 155 callwithasyncerrorhandle runtime core esm bundler js 164 what be expect no typeerror what be actually happen you tell I system info shell lsb release a no lsb module be available distributor i d debian description debian gnu linux 10 buster release 10 codename buster firefox version mozilla firefox 91 13 0esr any additional comment do not happen in v3 2 37 |
vuejscore | 3 2 38 regression error for multi branch dynamic slot | Bug | vue version 3 2 38 3 2 39 above commit 00036bb52c4e641b2be7fa55c39ced9448163b0f link to minimal reproduction enqfustowzaq bxlhhppbimeqaiq4jd8cckgdpfd6004rpl31klapuxaztszoxopm8rngnxqgzzkmtvoi4ke1mcn462laummaqevk2gxolfj6e5cvqqxv1zppgqnpku9wlejdwqudhubt0kuwtafdf0ycvcht bjdivth40k7mhiwcyr srhlz3oevy xm6fyccnlvdyuu hqqg uvbcxjhhruqy8ihmjgn8xzwb u4u01hr3sfpn1uhp0 maew9wqdfe9zpoo7v4ue3ntewv5bc8yrhkwfyoph7jblmcaasehwdcphn2i32kvcg xgamyfjjy7 g hj5n9guxl03djhxmbpawlcouos1eo6zh5vxtd1fvs13 gz sne7 step to reproduce build the project with ssr what be expect the build should pass what be actually happen typeerror can not set property of undefined set key at slot system info shell system os window 10 10 0 19044 cpu 8 x64 intel r core tm i7 7700hq cpu 2 80ghz memory 12 46 gb 23 84 gb binary node 16 15 1 c program file nodejs node exe yarn 1 22 15 appdata roaming npm yarn cmd npm 8 11 0 c program file nodejs npm cmd browser chrome 105 0 5195 102 edge spartan 44 19041 1266 0 chromium 105 0 1343 33 internet explorer 11 0 19041 1566 any additional comment diff 38ca58cc499824842d1f7106fb614647e756cbdc1982bc04cd3c10fb379893c1r33 r36 re may be undefined add a nullable check may help if this change be acceptable I be willing to provide a pr diff const re slot fn args if re return res attach branch key so each conditional branch be consider a different fragment re as any key slot key return re |
vuejscore | weird ssr hydration error for no good reason | Bug | vue version 3 2 39 link to minimal reproduction step to reproduce 1 npm install 2 npm run dev 3 go to open devtool 4 note the hydration error 5 comment the wtf element in src app vue on line 6 6 refresh the page 7 note that the hydration error be go 8 wtf what be expect no hydration error what be actually happen runtime core esm bundler js 38 vue warn hydration node mismatch client vnode symbol static server render dom start of fragment at warn2 runtime core esm bundler js 38 runtime core esm bundler js 4593 hydration complete but contain mismatch system info shell system os macos 12 5 cpu 10 arm64 apple m1 pro memory 133 70 mb 16 00 gb shell 5 8 1 bin zsh binarie node 16 17 0 volta tool image node 16 17 0 bin node npm 8 15 0 volta tool image node 16 17 0 bin npm browser chrome 105 0 5195 102 safari 15 6 npmpackage vue 3 2 39 3 2 39 any additional comment no response |
vuejscore | duplicate key be generate when compile vue sfc to js | Bug | vue version 3 2 37 link to minimal reproduction enp9u8gomzaq zvzlhapglanciwptntpparqovivvhgwxlv22lkdrkkif yhmbmpeua9rzxm5n3zdl5sry4hkrsjrvfogkdebeodsdqamtcgdm40ceantmaukpngtjsdpoa2vewjxiw hbkgfhnngof0hxdtxmhiylabkgt4khqdmczf9ydz phydiutbujeu0hwdhxphvqyxlcwulqprydttbjpatcc1u8eipu9zmezlfas6scmrjj1g3cs2qfgvvvwfquido mk4vqrv4q4ypbaf8dqvnxnzwhexsylfwhcgkr 58zfe1zuzfmeeuowvp5xs2susmkbek hz8stetqvuieixc7qxrfgrgxjp2h7nbs ej01pdysedqabgtlsl tkelhc xiv 9w6qbk7lwxrt8i1bgilf5yxmbexmtqxbzatylud7fwckvdbsezxehi0ofwwyzrco8cyg4z4otkxnc7rpnzqmscrla6nhqcrwh72vvyspycr39a mvzukpbk1fyl1zjzml7iz6km1nx y hgpdnqbkmhib snixbgpanuknfpkrazccbl9bh55jljtkxui9bvzdvbd98cgxoojkngjnyrg8ojjwkumv5hv5ncboty7k1xjbaew zzzvryazp4furaprv3l2dyrsxtcpvyt39csn 7o1dtg step to reproduce 1 open the playground by click on link 2 view the generate js output of navlink vue 3 notice on line 40 41 duplicate key be generate what be expect there s be an unexpected key 0 generate it shouldn t generate that unwanted key what be actually happen another key key 0 be generate system info shell system os macos 12 5 1 cpu 8 arm64 apple m1 memory 101 03 mb 8 00 gb shell 5 8 1 bin zsh binarie node 16 16 0 nvm version node v16 16 0 bin node yarn 1 22 19 nvm version node v16 16 0 bin yarn npm 8 11 0 nvm version node v16 16 0 bin npm browser chrome 105 0 5195 102 safari 15 6 1 npmpackage vue 3 2 37 3 2 37 any additional comment I have to use as wrapper so I have to add key to this dynamic component moreover this isn t result in any warning while development however in build it show this warning vite v3 1 0 building for production transform 1223 node module float ui dom dist float ui dom esm js plugin vite esbuild duplicate key key in object literal 50 withdirective openblock createblock resolvedynamiccomponent unref config app enablei18n i18n t span mergeprop 51 key 0 52 key badge 53 class nav item badge prop item badgeclass 54 unref dynamici18nprop prop item badgecontent span |
vuejscore | style attribute with numeric value be not render on server side | Bug | vue version 3 2 38 link to minimal reproduction step to reproduce 1 npm generate js what be expect foobar to get the exact same style attribute in the dom in the server side render version so the ui be not break or jump by load hydrate a ssr page what be actually happen foobar its about the empty style attribute in the first paragraph this issue only occure in the ssr process by render the exact same component in the browser the style attribute with numeric value be render fine system info shell system os linux 5 0 undefined cpu 4 x64 intel r core tm i9 9880h cpu 2 30ghz memory 0 byte 0 byte shell 1 0 bin jsh binary node 16 14 2 usr local bin node yarn 1 22 10 usr local bin yarn npm 7 17 0 usr local bin npm npmpackage vue 3 2 38 3 2 38 any additional comment no response |
vuejscore | stringifystatic get wrong attribute | Bug | vue version 3 2 36 link to minimal reproduction open this link sfc playground enrtuctkxdau zvrnlwyjjcci9ip484 cjnn29yo1bxibuui9n9npiljcpodbi6cb fapqt79j7pe7kk1bepoyeisjnvpb2nd4fggyadrdaez6bi1kjaaxtni4gjjzhk bz4qq0dplug1u1xj20ttrgulach8boltaig7iyiz6fsy2w7jeog2ddqiji1adnti82y2du4n7xi9x afpfv37ndmzbsdst56 r2btycrz9clgycs5m5tk2guv2qurjjcrk duj986iy9jemcynbkvlzpge7 n ifvguuq5rln2wb1hdklrst1fuejkjkemabugdl wxxm fv5pp0pz5yrtytypkor1rq step to reproduce open what be expect button not disabled what be actually happen button be disabled system info no response any additional comment look like we need to check the type of value here l285 |
vuejscore | a memory leak occur when switch between component | Bug | version 4 1 5 reproduction link github com have router sfc playground enrlvmgo0zaq zvrolqrnxhpforcw8qbaxihdohtlmnipqajbdlol6rqv ocngmyu0lcuusemtfz gbguqsfty5onq iyguzi7sjmpxfogmctqky3nv6k0hrawucxshtla4dz2dk j6utdeqogkkthrq97tg39kzqt0tgrg7y3pdov8q7c4 2cn7zw2yyh0tmyeujkekouq bx aptalkuq6dyfoljy1p xiwk9pwib0cd938 l8qrg3e3n1btmlrwvgyikkkuip90bwg8ol8zyid3qn4fyjewpsnucujb7otytqrljbvytdclzszep4u2qvi1nzwhfxower26wu2dg3v1ebbjsfjbfilaip1ct52ymj21isljigd8fwwevcwpyvg3ddto5c mnucnls 5mpupmy3iyxy49ns5pyzccfm9cfwxszopexflhyt3bivrunzke74rbkdftlkokfa5kswwdbfbdlva d9nyshjztnmaslvpyrndhtogxu0snkh7mqto rovo8qnuwtf0r9xw4c6oj8sngjngnijo4dxba7qtc8pnx8meyueez2ivsd0nonffa8zl7x yi ftvqbwd04diznfxuojp3cvdckchcs xbhoh27zq4f6frlsdsvnv7jocifb1 ukwdehru7lrqocw9qc 5nat 3 8a4gxw0xs0pniws4u3h0vuzv9w sodfogy r3g8bt38swwl ct1pks flgka07kdjh7k6jf36pps4hbnvcog7huvwfup3qhvqq step to reproduce toggle between page multiple time check memory usage after gc what be expect stable memory usage what be actually happen a large number of node be not reclaim and memory keep grow |
vuejscore | can not read property of undefined reading value with 3 2 38 work in 3 2 37 | Bug | vue version 3 2 38 link to minimal reproduction step to reproduce create a v img item and get an error uncaught in promise typeerror can not read property of undefined reading value at invokedirectivehook vue global js 4323 49 at array vue global js 6833 27 at flushpostflushcbs vue global js 1916 49 at flushjob vue global js 1969 11 what be expect to not have a error in the console what be actually happen I get one system info no response any additional comment be work in 3 2 37 kael from discord think it s relate to this commit relate message on the vuetify discord |
vuejscore | vue s h function switch render innerhtml and innertext exception | Bug | vue version 3 2 12 link to minimal reproduction step to reproduce 1 the second parameter of the h function be innerhtml this be innerhtml 2 change the second parameter of the h function to innertext this be innertext what be expect expect after switch the page can render this be innertext what be actually happen actually happen after switch the page be render as empty system info shell system os window 10 10 0 22000 cpu 8 x64 11th gen intel r core tm i5 1155g7 2 50ghz memory 5 30 gb 15 79 gb binary node 14 16 0 d tool nodejs node exe npm 6 14 11 d tool nodejs npm cmd browser edge spartan 44 22000 120 0 chromium 104 0 1293 70 internet explorer 11 0 22000 120 npmpackage vue 3 2 2 3 2 37 any additional comment |
vuejscore | vnode type definition cause error in typescript 4 8 | Bug | vue version 3 2 37 link to minimal reproduction step to reproduce 1 create a project that use vue and typescript 2 add typescript code to this project that import the vnode type from vue 3 upgrade typescript to 4 8 2 which be release yesterday what be expect thing should continue to work what be actually happen typescript fail with the follow error due to an incorrect type definition in the vnode type node modules vue runtime core dist runtime core d ts 1846 33 error ts2344 type hostelement do not satisfy the constraint rendererelement 1846 transition transitionhook null node modules vue runtime core dist runtime core d ts 1828 57 1828 export declare interface vnode |
vuejscore | ssr generate wrong code | Bug | vue version 3 2 37 link to minimal reproduction step to reproduce 1 run yarn build server 2 open dist server entry server js 3 search for resolvecomponent nest test line 34 4 compare call of ssrrenderslot line 43 js ssrrenderslot ctx slot name null push2 parent2 scopeid wrong it should not be name but ctx name instead 5 with call of renderslot line 48 js renderslot ctx slot ctx name what be expect both call should refer to variable name but actually the second renderer refer to ctx name which be different what be actually happen it do not work as expect because the variable be undefined system info shell system os macos 11 4 cpu 8 arm64 apple m1 memory 93 53 mb 16 00 gb shell 3 5 1 opt homebrew bin fish binary node 16 15 0 nvm version node v16 15 0 bin node yarn 3 2 2 nvm version node v16 15 0 bin yarn npm 8 5 5 nvm version node v16 15 0 bin npm browser chrome 104 0 5112 101 firefox 100 0 1 safari 14 1 1 npmpackage vue 3 2 37 3 2 37 any additional comment I downgrade to as the low possible compatible version with the vite plugin but even there it didn t work |
vuejscore | fix ssr forward helper provide by css v bind | Bug | during ssr build the unref helper provide by inject css binding be not forward to the main ast cause unref be not define error on ssr fix nuxt framework 6201 fix close nuxt nuxt js 14452 as an alternative reproduction with vite |
vuejscore | script setup class constructor class can not be invoke without new | Bug | vue version 3 2 37 link to minimal reproduction enp9kmtow0amrx fgiglldrmvgre1q0fwhi26csblmxdhqcfrfl3naelaond f7psa97ty8xp3eodqpilprikjc7 gh842ighh4iaxigpuagk9bsar1g4knbprsyuwzr7kjkp5tdg1 ogso4krhdbetgqqcky8ccpdzztrhvd0bdowt4lbnpscg24phym2k1xhs1fqr4xryne0ppenelmb3q1ubnc25dgwwr4cvdp abxuhg7wbsrk0yjbvrb8wx7brotr1vckp5ofctr5w6z43dhjpbhilcepkajdrcmlsiz6qtoa qkp5j mr9wx2xg gdrlk9qetaj n0fdzl1zjmduyr6hcck301p7lbj6bocqdv hr0mzl8arwjrgw step to reproduce 1 open link to sfc playground 2 click the button 3 an error class constructor class can not be invoke without new be raise what be expect no error should be visible in |
vuejscore | keepalive suspense this be likely a vue internal bug | Bug | vue version vue 3 2 31 link to minimal reproduction step to reproduce change tab during component loading get back to the first one what be expect see loading progress what be actually happen error in console not stackblitz app be break system info shell system os linux 5 18 arch linux cpu 32 x64 amd ryzen 9 5950x 16 core processor memory 41 99 gb 62 71 gb container yes shell 5 1 16 bin bash binary node 18 7 0 usr bin node yarn 1 22 19 usr bin yarn npm 8 16 0 usr bin npm browser chromium 104 0 5112 79 any additional comment |
vuejscore | window handle result in hydration error in dev | Bug | vue version 3 2 37 link to minimal reproduction step to reproduce 1 git clone on a windows machine 2 pnpm I 3 pnpm dev 4 visit what be expect no hydration error what be actually happen you will see a hydration error the issue be r n on server not match n on client cleanshot 2022 08 05 at 11 43 34 system info no response any additional comment no response |
vuejscore | text interpolation doesn t support arrow function return type in typescript | Bug | vue version 3 2 37 link to minimal reproduction enp9us1owzamfhwts1ejtwlh0k1w4w245bi6r8vu chxb6jqu n23to2ra5rpvuz tl2j169z44tikkusqrae0sk1kojbl2wgqiug2m18s4qdbbwbz3sgjoqcfgirbqa0lborglcl3qc9caqiwvt680i0vapc9wee2kspl9zvzdckuzyqhndiplvyn2b q2bxsg7c832iumllfntcyyyaahxjsjkbhzkrt5otwba pagokqmxahnqbgu8dla2bdafnybwjw7woxuqjgymsjlan5j1nvt430 lcrnwn upsp4xx8lxey5elkast pep8v6rx9p2x1p6zml78jhsvpukujfhaizviudonujwevqagjzbdx1acsxz7ixylp464anugqmxfqnf9zac1pgxlgs wi7jni4mqngsykf 0psyfkia step to reproduce what be expect arrow function return type should be correct parse in vue template what be actually happen in the demo code above when annotate the return type in the arrow function the dist build result in an empty function ts input e any any text1 e target value with return type oninput cache 1 cache 1 event e text1 value e target value without return type oninput cache 0 cache 0 e text1 value e target value system info no response any additional comment no response |
vuejscore | toref be not available unless ref be also use | Bug | vue version 3 2 37 link to minimal reproduction eno9unfqwkaq jxlkerbk qapkkpby1yfztch 4l6hojyd1xu9dsqv69l6t1bwdnbm9mwvfkbfzluaqio6orlamhe7tu mg0mvhnlmejnpbcadz1aniqddbqmciwafcpxrte2vw6ni2roc98zsleb0hulaivhgiohrngabb1sndtpzvoeljjtcwl5c8snvizh xrrsjkvbifqr6fvdztt6upzxkp4tgz157wfkzdotxptk r6un bwsdvz5isw kegiguvhg4ccsgaogkaewnryugamcyc6lzdsor7suswlq5tejmimqscbxvclsfcwjq3fdceqpicvutsgrmu2xehdms2ms0pny132l2lgycvpsvoaqwripmr c sz04bas w2j7hcdw4ut step to reproduce 1 write a new component that make use of toref but do not use ref 2 you ll see the follow error toref be not define what be expect transform kick in when toref be use what be actually happen transformation of toref do not happen unless the same file use ref it do not seem to matter whether ref be use in a comment line of code system info no response any additional comment relate discussion discussioncomment 3204419 |
vuejscore | the onunmounted callback be not trigger when use teleport | Bug | vue version 3 2 37 link to minimal reproduction dev enq1ve1v2kaq stbqxjgiu1cdq0cijlmxkls6c2hlpzgtvf ahdmipd e2dt4xgioqzsfwhn872zfewhudcm3tuqpmecqzqki9xmksnfixz0ypsnjmssa0stmmn9bcssknywqkvwlftm2rfz yyl2f1eifyjoluuigoe6keecdkbtlng6jthg89iehhq5p4f5lum e6uhauhzabipmn8xeeczpxdmpmlmivkdansf4knyvhpam alzdlrhonkbyrqmboiwreiwtd7gkxasecx1dqkosdnwzusdjf29hqsbw5vggkv3xn5ktflahnqd556z8cad5dcf5 kc7 lulxtejgolmll1thkdna2pbhyjbegvnysiztrjzsqgkd3ayxey8uhce9k0k 9mqe m7kc8jg47cl7xpueovgekwyltxgjqsdpjawfuvdpkwpw96ygx nl4t3vkp92ecz1fj5uona6ykrocmdsw7ix04r qo19vkfcfmqdh29j7h7mxsnafyajluyt2wca5ncusyxtuihisq0vluo5 h1z9qqw7e biejtdxpdiwhzshvqhlczh3yynjowij9e ws9wtwlpyk1gpsmhpawnndnl00j89le8xrs23pmtkcwp2xpjkx m0fqsrtm1jw5hfnn2 t g96umfbfnk0scn 8qwrnnoiwvbxeiszq4 jyc9gibd 9ffbqkdbcq5dgyn6gfao87mvqmaffa0 bm7u3lu d sf teonqkpwnqxkta3uwvbfhb6hricudbk dhkp 3hoqcwer ni9r5wnnebpyacc10gfqfnh pce0w step to reproduce click the button to switch navigation and the onunmounted callback of the sub component will not be trigger what be expect the onunmounted callback can be trigger normally what be actually happen the onunmounted callback can not be trigger system info no response any additional comment in my project create via npm init vue late the same code also cause memory leak in development mode the memory usage keep go up when I switch the navigation but this problem can not be reproduce in sfc playground image |
vuejscore | reactivity transform break the original semantic | Bug | vue version v3 2 37 link to minimal reproduction eno9tjsowjamvupkdqajerfworibh8hskpe2aj6yxriq3p2kicb7ffz8vrilpf8lqg2woxqtkezzuuocc10mliruvvwe efydkgqdpshnv zbrocps2tyezk2ehs3hgeozv5k9a dccyfyokz98mpxem e1ajtxpyae12pnc5v4foxheetfgcn vshprse tn01lkngjrvbnb8u3i vgbyvic2gd7qp4uu0c step to reproduce open the reproduction link there s an error on sfc playground can not access r before initialization the code ts const r ref 1 r be transform to js const r ref 1 r we can see that be remove and only bracket remain it will break the original semantic it s actually only one line code const r ref 1 r what be expect js const r ref 1 r format to const r ref 1 r what be actually happen js const r ref 1 r format to const r ref 1 r system info shell n a any additional comment imho the bracket should be remove to avoid change the semantic when use function |
vuejscore | transition not work with custom transition class in vue 3 migration build | Bug | vue version 3 2 37 migration build link to minimal reproduction step to reproduce 1 clone the repro project git clone jamisuomalainen vue 3 migration build transition bug git 2 run yarn install in the project folder 3 run yarn serve in the project folder 4 open the run app in any browser 5 click the toggle text button 6 see error in browser console 7 see src app vue for the define transition and transition class what be expect on the first button click the visible text should fade out in half a second on the second button click the viisble text should fade in in half a second subsequent button click repeat this cycle as it toggle the text visibility what be actually happen on the first button click no transition happen and the text stay visible additionally two warning and one error be show in chrome s console warn 1 vue warn unhandled error during execution of transition hook at at at at warn 2 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 error uncaught in promise typeerror can not read property of undefined reading split at addtransitionclass vue runtime esm bundler js fe26 12154 1 at onleave vue runtime esm bundler js fe26 12073 1 at callwitherrorhandle vue runtime esm bundler js fe26 1563 1 at callwithasyncerrorhandle vue runtime esm bundler js fe26 1563 1 at callhook vue runtime esm bundler js fe26 4136 1 at callasynchook vue runtime esm bundler js fe26 4136 1 at leave vue runtime esm bundler js fe26 4178 1 at performleave vue runtime esm bundler js fe26 9325 1 at remove vue runtime esm bundler js fe26 9325 1 at unmount vue runtime esm bundler js fe26 9325 1 on subsequent button click no transition happen and the text stay visible additionally one warning and one error be show in chrome s console warn 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 error uncaught in promise typeerror can not read property of null reading parentnode at parentnode vue runtime esm bundler js fe26 11208 1 at reactiveeffect componentupdatefn as fn vue runtime esm bundler js fe26 8920 1 at reactiveeffect run vue runtime esm bundler js fe26 495 1 at instance update vue runtime esm bundler js fe26 8953 1 at callwitherrorhandle vue runtime esm bundler js fe26 1563 1 at flushjob vue runtime esm bundler js fe26 1909 1 system info shell system os macos 12 4 cpu 4 x64 intel r core tm i5 7267u cpu 3 10ghz memory 23 81 mb 8 00 gb shell 5 8 1 bin zsh binarie node 16 10 0 nvm version node v16 10 0 bin node yarn 1 22 17 yarn bin yarn npm 7 24 0 nvm version node v16 10 0 bin npm watchman 2022 02 14 00 usr local bin watchman browser chrome 103 0 5060 114 firefox developer edition 103 0 safari 15 5 npmpackage vue 3 1 0 3 2 37 any additional comment encounter this bug as we be currently in the progress of add the vue 3 migration build to our vue 2 6 14 vue cli 5 0 8 app I could not reproduce this issue on stackblitz because if I understand correctly it do not run the app via the vue cli service webpack and thus do not seem to use the migration build please let I know if I can be of any more assistance or provide any more information regard the subject |
vuejscore | fail to render component that extend a runtime template component | Bug | vue version 3 2 37 link to minimal reproduction step to reproduce 1 run the app 2 notice that nothing be render 3 comment out helloworld vue line 13 and uncomment helloworld vue line 14 4 notice that I m an sfc now render what be expect I have create a component extendedcomponent that have the key extend to extend a compnent that use a runtime template javascript const basecomponentruntimetemplate template I m a component const extendedcomponent extend basecomponentruntimetemplate and I be try to render it with I expect that this would render basecomponentruntimetemplate s template in the app what be actually happen nothing render system info no response any additional comment it seem to work fine when the base component be an sfc but if the base component use a runtime template it do not work I create the reproduction link on stackblitz because I need to enable runtime compilation of template |
vuejscore | definition in | Bug | vue version 3 2 37 link to minimal reproduction enp9ke1ugzaqha8y9yzecljdupkqu96gg28odihifxobwgn57h0giajw6sb2 m f59gzm8ez9my0oslgfhgyfiwac unzwxhhewyg7cbbr85axl8zzzvtna0rtdjdcff32ttq7eddkw6fsr2yldxwdgir0xhdr2qfupxpp3lem1oqjku1olg rphy41ruryxyv4ktsj50s7xzafb7jdhiv4 aoy41aongg7hd7w8fgngpodjsbklfs5fns8vfxz2voiht8tzuvrgez3k3k0hdjabeeumrwrtztbj9jd6uuoauwtz6cywjs rxqzxnmfhgmpknua axgaldg8mycujkse0lrlsf8xfx 9wrymlkx4ach j6q step to reproduce use |
vuejscore | v bind not work with compute property in ssr | Bug | vue version 8edf4b3 link to minimal reproduction ssr enp9km1uhdamhf fyovfwsgdavjfoedcwojtwzef2ygqqrx7haiqvsv1lhl7pnmyqzcy63vb1aiwr5piasa0xn74ycvactyyg4tlqgs73ck4kgs mn74mxhomp4dqfezdrmu0pvqenqinl7vj1eiihk6oa8jrqg0dlphnafmzih5g3xyak9oj7kwu6xwp8vecvqcexgmea04dczsoxcc0sba3szvl4cqm8 4 tgk53p1vwe1yg2xfndwuv6im 8bg9wcwoxj26ynek8pcqm138f8zq ua71pedw0 dq5rjfddapwwugcnur6xnbirkgvobdisp8xf63 4wasnnrv gwkxprz step to reproduce open link make sure its on prod with ssr on near line 20 in ssr tab we have an unref call but it isn t import first what be expect for build to succeed unref to be import from vue prior to its call what be actually happen referenceerror unref be not define system info no response any additional comment skirtle code observe that it s not just compute anything deem setup maybe ref will fall into the same problem ssr enp9ue1rhtaq ctllio8zv1u6f oqydcflq2pjqju9fsxp etezh0uipgczszozhov68r ynva0ahmj2arjd5jtj59u7cnaa4qqntorwyesagwvs4cwh2bjfoiw8glalsjwjhlmcwnj4lthgfkeiiuk8mlbrvynpisdg6pc occazpx3gjaeutvk kylguavx1txqgrv6cebqa5fcwipzumotbvjjmhivwvyy tsxzwhms7odqzboq9tn3xtwq69rx7srfwj2c1pgy2qr8diyq0inuojbm 11jwn8yyprhy9a lvtnkwr1ghr wd3ccjsbbrt6cmlesovblaeqnpv8xf0j 5mvy2otx5dxtjnx4 |
vuejscore | web component without prop definition break when pass custom attribute like datum v xxxxxxx | Bug | vue version 3 2 37 link to minimal reproduction step to reproduce in the web component element generate after the definecustomelement be define in the vue file if the style tag in the vue file contain the scope attribute the web component element will fail to resolve error runtime dom esm bundler js 547 uncaught typeerror can not read property of undefined reading datav671062ce after remove the scope attribute of the style tag in the vue file the web component be successfully parse app vue be an example of successful parsing hasscope vue file be an example of parse failure what be expect the scope style tag in the vue file do not affect the use of web component property what be actually happen the scope style tag in the vue file affect the use of webcomponent property system info no response any additional comment no response |
vuejscore | fix watch should work normal w sync flush in ssr | Bug | close 6013 |
vuejscore | in operator not work correctly with component instance exposeproxy | Bug | vue version 3 2 37 link to minimal reproduction step to reproduce 1 create a component which use expose in the setup function 2 use this component in another vue component and use a template ref to access its instance 3 access templateref value in the mount hook what be expect js templateref value el should evaluate to the html node correctly js el in templateref value should be true what be actually happen js templateref value el evaluate to the html node correctly js el in templateref value be false system info no response any additional comment l934 l949 I suspect that the exposeproxy which use the get handler need to implement the same logic in the proxy s have handler to fallback to check if the check property be define in publicpropertiesmap key instance |
vuejscore | current instance be not unset after render error on ssr | Bug | vue version 3 2 37 link to minimal reproduction step to reproduce click trigger error it will try to load a component where there be a js error 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 a render error what be actually happen when there be a vue render error the current component instance be not unset system info no response any additional comment in nuxt we be rely on getcurrentinstance to return null if call outside of a vue lifecycle see |
vuejscore | when clear a reactive array object in effect function the array length be not 0 all way have a element in it | Bug | vue version 3 2 22 link to minimal reproduction step to reproduce just copy the code to html file load page in browser html reactivity test image store value splice 0 trigger effect callback run again but in the effect callback store value length be not 0 do I use vue reactivity it in the right way what be expect when clear store value the store value length 0 what be actually happen clear reactive array store but the store value length 1 not 0 system info shell 5 0 window not 10 0 win64 x64 applewebkit 537 36 khtml like gecko chrome 101 0 4951 64 safari 537 36 edg 101 0 1210 53 any additional comment maybe I use it in the wrong way |
vuejscore | two rapid sequential transition display wrong | Bug | vue version 3 2 35 link to minimal reproduction step to reproduce when you click the button you can see that both a and b show the catalyst to this behavior be the settimeout in the file without it thing function normally what be expect only b should show what be actually happen both a and b continue to show system info seem that this behavior start on 3 2 34 doesn t happen on 3 2 33 any additional comment no response |
vuejscore | v model lazy do not update dom element when it have focus after vue model change | Bug | version 3 2 33 reproduction link sfc vuejs org eyjbchaudnvlijoiphnjcmlwdcbzzxr1cd5cbmltcg9ydcb7ihjlziwgb25nb3vudgvkih0gznjvbsandnvlj1xuxg5jb25zdcbszxzlbca9ihjlzig1mclcblxub25nb3vudgvkkcgpid0 ihtcbiagicbzzxruaw1lb3v0kcgpid0 ihtcbiagicagicagbgv2zwwudmfsdwugpsawo1xuicagih0siduwmdapo1xuxg59kvxupc9zy3jpchq xg5cbjx0zw1wbgf0zt5cbnt7bgv2zwx9ftxpbnb1dcb0exblpvwicmfuz2vciibtaw49xcixxcigbwf4pvwiotlciib2lw1vzgvslmxhenk9xcjszxzlbfwiplxupc90zw1wbgf0zt5cbiisimltcg9ydc1tyxauannvbii6intcbiagxcjpbxbvcnrzxci6ihtcbiagicbcinz1zvwioibcimh0dhbzoi8vdw5wa2cuy29tl0b2dwuvcnvudgltzs1kb21amy4yljmzl2rpc3qvcnvudgltzs1kb20uzxntlwjyb3dzzxiuanncilxuicb9xg59in0 step to reproduce within 5 second of the page load move the slider to any non zero value which make sure the slider have dom focus after 5 second timer will internally change the ref level to 0 what be expect both the text to the left and the slider go to 0 after 5 second what be actually happen the text to the left go to 0 but the slider remain where it be last drag to if the slider doesn t have focus e g we don t move in in the 5 second window after page load the slider also correctly go to 0 I have trace the bug to line 10436 of the if lazy return section |
vuejscore | toref type be wrong when use defineprop with optional boolean prop | Bug | version 3 2 26 reproduction link stackblitz com step to reproduce import toref from vue const prop defineprop islive boolean const islive toref prop what be expect accord to fix runtime core ensure declare prop key be always present type of islive should be ref what be actually happen the type of islive actually be ref undefined islive couldn t be undefined in no case |
vuejscore | mean mount run too early | Bug | version 3 2 33 reproduction link stackblitz com sfc playground enrnusuo2zam bvfkjas0fj3wfn0gr72uptqhhxx2rrxw sbiu5qbp73krzsj0gxwn56i6xhkbzowx4ootgoiheythu0auuchmkjdkiyg3xe8dxb8mobako3yl2onhpz g52opkbgouzxsdau0t8l 7edhvxiuk7wtjag3almttty0oqbogrhgmmsjhhkadweud0tnyqe1p 2mu5kk1yqgxgcnhwxdddrlrz6yxoecuxdboic5ufogpvr8xc oyzp dwucuy8ueqarg0z5tfltict6zdpiewdy9izy5b6bpc qk72litk83bq3n9uv0vrx6us zbw4xinxlh5zszwoeppovotc 8rhfgxmsxxjb2sqw25ro8pslhtlfuxmghsvbastvn6e8jihfryrsjdio1vdr7w245c e6kdrozzdbenlcyw6yl2jgzkpmgr0oamijb6zezb7b95d40ab0pwq8bxgwwhrqf4rqcov x ajzr72a98yxv2uoj20qyhm89uyb3e3xmk9uqgufrqcfx37e4mvp lqye dufoyqlmozf9wkz gevt3jn step to reproduce click the toggle component button in the reproduction and observe that a template ref be null rather than define what be expect I expect the behaviour with suspense to be the same as the behaviour without suspense what be actually happen mean that the mount hook run before the element be present in the dom |
vuejscore | compiler crash in some situation when the word zoom be present | Bug | version 3 2 33 reproduction link sfc vuejs org eyjbchaudnvlijoiphnjcmlwdcbsyw5npvwidhncij5cbmludgvyzmfjzsbqcm9wcyb7xg4gic8vihpvb20 xg4gige oibzdhjpbmc7xg59xg48l3njcmlwdd5cblxuphnjcmlwdcbzzxr1ccbsyw5npvwidhncij5cbmnvbnn0ihbyb3bzid0gd2l0aerlzmf1bhrzkgrlzmluzvbyb3bzpfbyb3bzpigplcb7xg4gige6ifwiyvwilfxufsk7xg48l3njcmlwdd5cbiisimltcg9ydc1tyxauannvbii6intcbiagxcjpbxbvcnrzxci6ihtcbiagicbcinz1zvwioibcimh0dhbzoi8vc2zjlnz1zwpzlm9yzy92dwuucnvudgltzs5lc20tynjvd3nlci5qc1wixg4gih1cbn0ifq step to reproduce the component see the link make the compiler crash it have something to do with the zoom even it s a comment const prop what be expect the compiler compile what be actually happen the compiler crash |
vuejscore | vue ssr scope datum attribute aren t pass down to functional component | Bug | version 3 2 25 reproduction link stackblitz com step to reproduce create a component with a scope style parent create a regular component with a template tag child create a functional component that use h child the regular child inherit the data attribute from the parent the functional child doesn t inherit the data attribute from the parent what be expect the child functional component should receive the datum attribute as if it be a template component what be actually happen functional and regular component behave differently in this instance initially open there use script setup doesn t happen on non ssr |
vuejscore | typescript error for set with v model | Bug | version 3 2 33 reproduction link github com step to reproduce 1 open project 2 run vue tsc noemit what be expect no typescript error what be actually happen there be a typescript error src app vue 9 38 error ts2322 type set be not assignable to type any booleanish undefined type set be miss the follow property from type any length pop push concat and 23 more 9 node module vue runtime dom dist runtime dom d ts 628 3 628 check booleanish any for ide v model multi checkbox support the expect type come from property check which be declare here on type elementattrs src app vue 13 38 error ts2322 type set be not assignable to type any booleanish undefined 13 node module vue runtime dom dist runtime dom d ts 628 3 628 check booleanish any for ide v model multi checkbox support the expect type come from property check which be declare here on type elementattrs find 2 error accord to documentation checkbox we can use set with input type checkbox the code work but vue tsc alert error here be the minimum code to reproduce vue |
vuejscore | use v model on in client orient render function in ssr doesn t work if type attribute be dynamic | Bug | version 3 2 33 reproduction link stackblitz com step to reproduce 1 in a component template use an that have a dynamic type attribute and use v model 2 compile this component to a client orient render function 3 use this compile component in an ssr app pass in foo text bar hello what be expect the input should render as what be actually happen the input render without a value this happen because vmodeldynamic in src directive vmodel ts doesn t have an ssr equivalent even though it would be possible to implement one |
vuejscore | fix hmr force full diff prop for nest component come from npm fix 5767 | Bug | fix 5767 I m not sure if ishmrupdate can be use here so follow the previous logic |
vuejscore | prop of hydrated slot component be not update on production build | Bug | version 3 2 33 reproduction link github com step to reproduce with my minimal reproduction repo npm install npm prod go to click move to a button what be expect slot prop c change to slot prop a what be actually happen prop of slot component be not update summary of the problem basically the sample app have follow structure pagewithwrapper define with render app vue slot page vue pagewithwrapper pass prop path a to app vue and it pass the same prop to slot so that page vue can receive it when prop pass to app be change I expect page vue get update but when page vue be render on server side update do not work reproduce condition as far as I experiment this problem have 3 condition to reproduce 1 html be render on server and then hydration createssrapp be execute on client side if same component be render only on client side it work as expect 2 slot be use to render the component if you directly include component in template it work as expect 3 this occur only on production mode in development build it work as expect background I run into this when I try vite plugin ssr s vue sample in this sample plugin s route functionality be use and it be implement by change slot of root component use render l22 |
vuejscore | v model modifier can break emit an update event if some parameter be not a string | Bug | version 3 2 33 reproduction link sfc vuejs org eyjbchaudnvlijoiphnjcmlwdcbzzxr1cd5cbmltcg9ydcbuzxn0igzyb20gjy4vvgvzdc52dwunxg5cbmxldcb2ywx1zsa9icryzwyoj2luaxrpywwnkvxupc9zy3jpchq xg5cbjx0zw1wbgf0zt5cbiagpggxpnt7ieptt04uc3ryaw5nawz5khzhbhvlksb9ftwvade xg4gidxuzxn0ihytbw9kzwwudhjpbt1cinzhbhvlxciglz5cbjwvdgvtcgxhdgu iiwiaw1wb3j0lw1hcc5qc29uijoie1xuicbcimltcg9ydhncijoge1xuicagifwidnvlxci6ifwiahr0chm6ly9zzmmudnvlanmub3jnl3z1zs5ydw50aw1llmvzbs1icm93c2vylmpzxcjcbiagfvxufsisilrlc3qudnvlijoiphnjcmlwdd5cbiblehbvcnqgzgvmyxvsdcb7xg4gicblbwl0oibbj3vwzgf0ztptb2rlbfzhbhvlj10sxg4gicbpbmhlcml0qxr0cnm6igzhbhnllfxuih1cbjwvc2nyaxb0plxuxg48dgvtcgxhdgu xg4gidxidxr0b24gqgnsawnrpvwijgvtaxqoj3vwzgf0ztptb2rlbfzhbhvljywgjybmb28gjylciib0exblpvwiynv0dg5cij5cbiagicb1cgrhdgvcbiagpc9idxr0b24 xg4gidxidxr0b24gqgnsawnrpvwijgvtaxqoj3vwzgf0ztptb2rlbfzhbhvljywgjybiyxigjywgeybuyw1loianzmllbgroyw1ljyb9kvwiihr5cgu9xcjidxr0blwiplxuicagihvwzgf0zsb3axroigv4dhjhigrhdgfcbiagpc9idxr0b24 xg48l3rlbxbsyxrlpij9 step to reproduce click update button no error click update with extra datum error a trim be not a function what be expect I would like to pass any type of value to update xxx event what be actually happen if v model be use with build in modifier e g trim or number then I can not emit the update xxx event if pass some parameter be not a string let s say I have custom input component where I would like to pass additional datum to update modelvalue event e g an object with field name but currently as show in the demo if I use trim modifier emit such an event be not possible look like the issue be in these line of code componentemit ts l124 l124 |
vuejscore | fix runtime dom should not update style if its not change | Bug | open the link eyjbchaudnvlijoiphnjcmlwdcbzzxr1cd5cbmltcg9ydcb7ihjlziwgcmvhy3rpdmugfsbmcm9ticd2dwunxg5cbmnvbnn0igxpc3qgpsbyzwfjdgl2zshbxg4gihtuyw1loianyscsigxlznq6iccxmhb4j30sxg5dksbcbmnvbnn0igfkzca9icgpid0 ihtcbiagbglzdc5wdxnokhtcbiagicbuyw1loianyicsxg4gicagbgvmddogjzewmhb4j1xuicb9kvxufvxuy29uc3qgbw92zsa9icgpid0 ihtcbibcdgnvbnn0igvscya9igrvy3vtzw50lnf1zxj5u2vszwn0b3jbbgwojy50zxh0jylcbiagqxjyyxkuznjvbshlbhmplmzvckvhy2goaxrlbsa9pib7xg4gicagaxrlbs5zdhlszs5szwz0id0gcgfyc2vjbnqoaxrlbs5zdhlszs5szwz0ksaridewicsgj3b4j1xuicb9kvxufvxupc9zy3jpchq xg5cbjx0zw1wbgf0zt5cbiagpgj1dhrvbibay2xpy2s9xcjtb3zlxci bw92ztwvynv0dg9upjxidxr0b24gqgnsawnrpvwiywrkxci ywrkpc9idxr0b24 xg4gidxkaxygy2xhc3m9xcj0zxh0xcigdi1mb3i9xcjpdgvtigluigxpc3rciia6a2v5pvwiaxrlbs5uyw1lxcigonn0ewxlpvwie2xlznq6igl0zw0ubgvmdh1cij57e2l0zw0ubmftzx19pc9kaxy xg48l3rlbxbsyxrlplxuphn0ewxlplxuicaudgv4dcb7xg4gicagcg9zaxrpb246ihjlbgf0axzlo1xuicb9xg48l3n0ewxlpiisimltcg9ydc1tyxauannvbii6intcbiagxcjpbxbvcnrzxci6ihtcbiagicbcinz1zvwioibcimh0dhbzoi8vdw5wa2cuy29tl0b2dwuvcnvudgltzs1kb21amy4yljmzl2rpc3qvcnvudgltzs1kb20uzxntlwjyb3dzzxiuanncilxuicb9xg59in0 and follow the step below 1 click the move button and the left value of div tag will become 20px 2 click the add button the left value of the first div tag should also be 20px fix 5772 border and border be set at the same time the browser and unit test rendering result be inconsistent refer to the follow figure rel |
vuejscore | bug ssr slot tag without default value will render different result between server and client | Bug | version 3 2 33 reproduction link github com step to reproduce 1 git clone 2 pnpm I pnpm start vite what be expect hydrate succeed what be actually happen runtime core esm bundler js 4072 hydration complete but contain mismatch if I have a slot component hope render fallback value if parent don t provide any slot content js but if parent don t provide prop title to slot will cause hydrate error js with debug in source code when hydrate dom the server side node be regard as fragment but in the client side the slot vue will be compile text node which cause mismatch ref l108 |
vuejscore | object defineproperty on componentpublicinstance proxy can not read property of undefined read accesscache | Bug | version 3 2 32 reproduction link stackblitz com step to reproduce make sure the terminal run npm run build npm run preview open developer console inspect error what be expect app vue should render properly and without an error what be actually happen app vue do throw an exception when render probably cause by this change discussion r849260064 relate |
vuejscore | reactivity transform break variable shadow | Bug | version 3 2 32 reproduction link sfc vuejs org eyjbchaudnvlijoiphnjcmlwdcbzzxr1cd5cblxubgv0ihnoywrvd2vkrxjyb3igpsakcmvmkcdobyblcnjvcienkvxubgv0igfjdhvhbevycm9yid0gjhjlzignkdepie5vbmugewv0li4ujylcblxubgv0igfjdhvhbevycm9ymia9icryzwyojygyksbob25lihlldc4ulicpxg5cbmz1bmn0aw9uihryevnvbwv0agluzygpihtcbiagly8grg9lcybub3qgd29yay5cbiagdhj5ihtcbiagicb0ahjvdybuzxcgrxjyb3iojygxksbj4oczbsbhbiblcnjvcienkvxuicb9ignhdgnoichzagfkb3dlzevycm9yksb7xg5cdfx0ly8gumvzdwx0cybpbibgdw5kzwzpbmvkycbizwluzybwcmludgvkihrvihrozsbjb25zb2xlllxuicagignvbnnvbguubg9nkhnoywrvd2vkrxjyb3ipxg5cdfx0ly8gywn0dwfsrxjyb3igbm93ignhcnjpzxmgdghlihzhbhvligb1bmrlzmluzwrgllxuicagigfjdhvhbevycm9yid0gc2hhzg93zwrfcnjvclxuicb9xg4gifxuxhqvlybxb3jrcybhcyblehbly3rlzc5cbiagdhj5ihtcbiagicb0ahjvdybuzxcgrxjyb3iojygyksbj4oczbsbhbiblcnjvcienkvxuicb9ignhdgnoichlcnjvcikge1xuicagignvbnnvbguubg9nkgvycm9ykvxuicagigfjdhvhbevycm9ymia9igvycm9yxg4gih1cbn1cbjwvc2nyaxb0plxuxg48dgvtcgxhdgu xg4gidxomt5qcm9ibgvtoib7eybzagfkb3dlzevycm9yih19pc9omt5cbiagpggzpkvycm9yoib7eybhy3r1ywxfcnjvcia pyanxfw8dw5kzwzpbmvkxfw jyb9ftwvadm xg4gidxomz5fcnjvciayoib7eybhy3r1ywxfcnjvcjigpz8gj1xcphvuzgvmaw5lzfxcpicgfx08l2gzplxuica8ynv0dg9uiebjbgljaz1cinryevnvbwv0agluzygpxci vhj5igl0itwvynv0dg9uplxupc90zw1wbgf0zt4ilcjpbxbvcnqtbwfwlmpzb24ioij7xg4gifwiaw1wb3j0c1wioib7xg4gicagxcj2dwvcijogxcjodhrwczovl3nmyy52dwvqcy5vcmcvdnvllnj1bnrpbwuuzxntlwjyb3dzzxiuanncilxuicb9xg59in0 step to reproduce while work with promise and async await I notice that sometimes my error in a try catch go miss I eventually determine the issue to be variable shadow error shadow by catch error in combination with the experimental reactivity transform I know this be 100 on I both in term of shadow and use experimental feature but I d still like to report the problem please finde a minimal reproduction in the attached sfc playground link to reproduce 1 create a reactive variable with ref e g let error ref 2 in an inner block shadow that variable with a non reactive one e g catch error 3 try to use the shadow variable e g console log error what be expect I want to see and use the shadow variable in a non reactive way that mean without vue compile each assignment and access to variable value what be actually happen in the compile code the variable end up be call as variable value end up as undefined if variable have no field value while inspect my code and the compile output of it I notice somewhere in the toolchain the shadowing be recognize correctly and deal with by rename the variable in question from error to error2 however at the same time each access also have value append to it error2 value here be two snippet 1 my code js let error ref error reset error try await session login credential redirect to path visit before automatic redirection to login page or home router push route redirectedfrom path catch error console log error 2 compile result js let error ref error value try await session login credential value router push route redirectedfrom path catch error2 console log error2 value problem here |
vuejscore | fix runtime core ensure custom event be not emit anymore after unmount fix 5674 | Bug | this change ensure that call emit after the component have unmounted will no long call any of the register custom event listener consideration be it possible realistic that we have implementation out there that rely on the current behavior where this event would still be trigger if so how do we approach this close 5674 |
vuejscore | comment inside transition be consider as a node | Bug | version 3 2 31 reproduction link sfc vuejs org eyjbchaudnvlijoiphnjcmlwdcbzzxr1cd5cbmltcg9ydcb7ihjlzib9igzyb20gj3z1zsdcblxuy29uc3qgzg9ju3rhdgugpsbyzwyoj3nhdmvkjylcbjwvc2nyaxb0plxuxg48dgvtcgxhdgu xg5cddxzcgfuihn0ewxlpvwibwfyz2lulxjpz2h0oiaymhb4xci q2xpy2sgdg8gy3ljbgugdghyb3vnacbzdgf0zxm6pc9zcgfuplxuica8zgl2ignsyxnzpvwiynrulwnvbnrhaw5lclwiplxuxhrcddxucmfuc2l0aw9uig5hbwu9xcjzbglkzs11cfwiplxuicagicagidwhls0grwrpdcatlt5cbiagicagidxidxr0b24gdi1pzj1cimrvy1n0yxrlid09psanc2f2zwqnxcjcbiagicagicagicagicagqgnsawnrpvwizg9ju3rhdgugpsanzwrpdgvkj1wipkvkaxq8l2j1dhrvbj5cbiagicagica8is0tifnhdmugls0 xg4gicagica8ynv0dg9uihytzwxzzs1pzj1cimrvy1n0yxrlid09psanzwrpdgvkj1wixg4gicagicagicagicagiebjbgljaz1cimrvy1n0yxrlid0gj2vkaxrpbmcnxci u2f2ztwvynv0dg9uplxuicagicagidwhls0gq2fuy2vsic0tplxuicagicagpgj1dhrvbib2lwvsc2utawy9xcjkb2ntdgf0zsa9pt0gj2vkaxrpbmcnxcjcbiagicagicagicagicagqgnsawnrpvwizg9ju3rhdgugpsanc2f2zwqnxci q2fuy2vspc9idxr0b24 xg48l1ryyw5zaxrpb24 xg4gidwvzgl2plxupc90zw1wbgf0zt5cblxuphn0ewxlplxulmj0bi1jb250ywluzxige1xuicbkaxnwbgf5oibpbmxpbmutymxvy2s7xg4gihbvc2l0aw9uoibyzwxhdgl2zttcbiagagvpz2h0oiaxzw07xg59xg5cbmj1dhrvbib7xg4gihbvc2l0aw9uoibhynnvbhv0zttcbn1cblxulnnsawrllxvwlwvudgvylwfjdgl2zsxcbi5zbglkzs11cc1szwf2zs1hy3rpdmuge1xuicb0cmfuc2l0aw9uoibhbgwgmc4ynxmgzwfzzs1vdxq7xg59xg5cbi5zbglkzs11cc1lbnrlci1mcm9tihtcbiagb3bhy2l0etogmdtcbiagdhjhbnnmb3jtoib0cmfuc2xhdgvzkdmwchgpo1xufvxuxg4uc2xpzgutdxatbgvhdmutdg8ge1xuicbvcgfjaxr5oiawo1xuicb0cmfuc2zvcm06ihryyw5zbgf0zvkoltmwchgpo1xufvxupc9zdhlszt4ilcjpbxbvcnqtbwfwlmpzb24ioij7xg4gifwiaw1wb3j0c1wioib7xg4gicagxcj2dwvcijogxcjodhrwczovl3nmyy52dwvqcy5vcmcvdnvllnj1bnrpbwuuzxntlwjyb3dzzxiuanncilxuicb9xg59in0 step to reproduce just add comment inside transition and you can see it break by show a can only be use on a single element or component error what be expect the transition component should work as expect since comment be not real dom element what be actually happen vue show an error say can only be use on a single element or component |
vuejscore | event handler fire after umounted unlike vue 2 event listener be not remove between beforeunmount and unmounted | Bug | version 3 2 31 reproduction link stackblitz com step to reproduce I need to provide two reproduction link to demonstrate the difference between vue 2 and vue 3 vue 2 vue 3 the component hierarchy be as follow app alertlist alert alert emit a hide event asynchronously from beforeunmount alertlist handle the alert s hide event the handler be wire up in the template to reproduce the bug click the toggle alert button which remove the alertlist and its alert s from the dom via vif in the vue 3 version the hide event handler fire after alertlist s unmounted lifecycle hook consequently ref and inject dependency be not available in the vue 2 version event listener be remove before the component be unmounted destroy in vue 2 as such the hide event handler do not fire what be expect event listener should be tear down after beforeunmount and before unmounted event handler should not run after a component be unmounted as it stand this be an undocumented breaking change between vue 2 and vue 3 what be actually happen event handler in this case alertlist loghide fire after unmounted note that in the vue 2 lifecycle diagram it s clear when event listener be remove lifecycle diagram in vue 3 s livecycle diagram there s no mention of event listener be remove lifecycle diagram it would be nice if this step be still document in vue 3 for context our application use uikit some of the uikit component emit event asynchronously after an animation occur for example the offcanvas accordion and modal component emit hide event after they slide close which take a small amount of time to animate in our project we sometimes handle these hide event but the handler erroneously imo fire event after the component be unmounted |
vuejscore | useattrs do not return shorthand listener in ssr | Bug | version 3 2 31 reproduction link stackblitz com step to reproduce refresh the page when open the reproduction what be expect I expect equal behaviour between client server what be actually happen some attr will be print on server and some attr onclick on client if you uncomment the alternative syntax in the sandbox v bind onclick handler then some attr onclick be print on both client server |
vuejscore | change to nonreactive variable contain primitive value be reflect in prod but not in dev | Bug | version 3 2 31 reproduction link sfc vuejs org eyjbchaudnvlijoiphnjcmlwdcbzzxr1cd5cbmltcg9ydcb7ihjlzixzagfsbg93umvmih0gznjvbsandnvlj1xuy29uc3qgzm9vid0gc2hhbgxvd1jlzih7zm9vuhjvcdoxfslcbmnvbnn0igjhcia9ihjlzigxkttcbmxldcbub25szwfjdgl2zsa9idfcbiagznvuy3rpb24gb25dbgljaygpe1xuicagic8vicnmb28gaxmgdxbkyxrlzcfcbiagicbmb28udmfsdwuuzm9vuhjvccsro1xuicagigjhci52ywx1zssro1xuicagic8vicnub25szwfjdgl2zsbpcyb1cgrhdguhisehivxuicagic8viej1dcbpdcb3b24ndcbvy2n1cibpbibhihbyb2r1y3rpb24gzw52axjvbm1lbnqsig9ubhkgc2zjihbsyxlncm91bmrcbiagicbub25szwfjdgl2zssro1xuicb9xg4gigz1bmn0aw9uig9uq2xpy2sykcl7xg4gicagly8gi2zvbybpcyd0ihvwzgf0zwrcbiagicbmb28udmfsdwuuzm9vuhjvccsro1xuicb9xg48l3njcmlwdd5cblxuphrlbxbsyxrlplxupgrpdibpzd0nzm9vjz5cbiage3tmb28uzm9vuhjvch19xg4gidwvzgl2plxuica8zgl2iglkpsdiyxinplxuicagiht7ymfyfx1cbiagpc9kaxy xg4gidxkaxygawq9j25vbljlywn0axzljz5cbiagicb7e25vbljlywn0axzlfx1cbiagpc9kaxy xg4gidxidxr0b24gqgnsawnrpsdvbknsawnrjz5cbiagicbjbglja21livxuica8l2j1dhrvbj5cbiagpgj1dhrvbibay2xpy2s9j29uq2xpy2syjz5cbiagicbjbglja21lisfcbiagpc9idxr0b24 xg48l3rlbxbsyxrlpiisimltcg9ydc1tyxauannvbii6intcbiagxcjpbxbvcnrzxci6ihtcbiagicbcinz1zvwioibcimh0dhbzoi8vc2zjlnz1zwpzlm9yzy92dwuucnvudgltzs5lc20tynjvd3nlci5qc1wixg4gih1cbn0ifq step to reproduce javascript const foo shallowref foo 1 the element node should not be update when the shallowref change however when other responsive datum change the element node bind to shallowref be also update what be expect not update what be actually happen element node update |
vuejscore | the activate hook dosen t call on initial mount when the component be async | Bug | version 3 2 31 reproduction link sfc vuejs org eyjbchaudnvlijoiphrlbxbsyxrlplxuica8zgl2ignsyxnzpvwizgvtb1wiplxuicagidxidxr0b25cbiagicagihytzm9ypvwikf8sihrhyikgaw4gdgfic1wixg4gicagica6a2v5pvwidgfixcjcbiagicagidpjbgfzcz1cilsndgfilwj1dhrvbicsihsgywn0axzloibjdxjyzw50vgfiid09psb0ywigfv1cilxuicagicagqgnsawnrpvwiy3vycmvudfrhyia9ihrhylwixg4gicagplxuicagicage3sgdgfiih19xg4gicagpc9idxr0b24 xg4gicagpetlzxbbbgl2zt5cbiagicagidxjb21wb25lbnqgomlzpvwidgfic1tjdxjyzw50vgfixvwiignsyxnzpvwidgfixci pc9jb21wb25lbnq xg4gicagpc9lzwvwqwxpdmu xg4gidwvzgl2plxupc90zw1wbgf0zt5cblxuphnjcmlwdcbzzxr1cd5cbmltcg9ydcb7ihjlziwgacwgs2vlcefsaxzllcbkzwzpbmvdb21wb25lbnqsigrlzmluzufzew5jq29tcg9uzw50lcbvbkfjdgl2yxrlzcb9igzyb20gxcj2dwvcijtcbiagxg5jb25zdcbqb3n0cya9ich7xg4gihjlbmrlcjogkckgpt4gachcimrpdlwilcbudwxslcbcilbvc3rzxciplfxuicbhy3rpdmf0zwq6icgpid0 ihtcbiagxhrjb25zb2xllmxvzyggj1bvc3rzoibvbkfjdgl2yxrlzccpxg5cdh0sxg59kttcblxuy29uc3qgqxn5bmnqb3n0cya9igrlzmluzufzew5jq29tcg9uzw50khtcbiagbg9hzgvyoiaoksa9pibuzxcguhjvbwlzzsgocmvzb2x2zskgpt4ge1xuicagifx0c2v0vgltzw91dcgoksa9pib7xg4gicagicagihjlc29sdmuoe1xuicagicagicagihjlbmrlcjogkckgpt4gachcimrpdlwilcbudwxslcbcimfzew5jifbvc3rzxciplfxuicagicagicagigfjdgl2yxrlzdogkckgpt4ge1xuicagicagicagicagy29uc29szs5sb2coicdbc3luy1bvc3rzoibvbkfjdgl2yxrlzccpxg4gicagicagicagfsxcbiagicagicagfslcbiagicagih0siduwmclcbiagfsksxg59kttcbiagxg5jb25zdcbib21lid0gzgvmaw5lq29tcg9uzw50khtyzw5kzxi6icgpid0 iggoxcjkaxzciiwgbnvsbcwgxcjib21lxcipfsk7xg5cbmnvbnn0ign1cnjlbnruywigpsbyzwyoxcjib21lxcipo1xuxg5jb25zdcb0ywjzid0ge1xuicbib21llfxuicbqb3n0cyxcbiagqxn5bmnqb3n0c1xufttcbjwvc2nyaxb0plxuxg4ilcjpbxbvcnqtbwfwlmpzb24ioij7xg4gifwiaw1wb3j0c1wioib7xg4gicagxcj2dwvcijogxcjodhrwczovl3nmyy52dwvqcy5vcmcvdnvllnj1bnrpbwuuzxntlwjyb3dzzxiuanncilxuicb9xg59in0 step to reproduce 1 click the post button 2 click the asyncpost button what be expect console post onactivate asyncpost onactivate what be actually happen console post onactivate asyncpost component s activate hook dosen t call on initial mount |
vuejscore | vite build fail with withdefault and prop extend from another interface | Bug | version 3 2 31 reproduction link sfc vuejs org eyjbchaudnvlijoiphnjcmlwdcbsyw5npvwidhnciibzzxr1cd5cbmltcg9ydcb7ihjlzib9igzyb20gj3z1zsdcblxuaw50zxjmywnlifbyb3bzihtcbiagbgfizww oibzdhjpbmdcbn1cblxuaw50zxjmywnlifnlbgvjdfbyb3bzigv4dgvuzhmguhjvchmge31cblxuy29uc3qgchjvchmgpsb3axrorgvmyxvsdhmozgvmaw5luhjvchm8u2vszwn0uhjvchm kcksihtcbiagbgfizww6icdfbwfpbccsxg59kvxupc9zy3jpchq xg5cbjx0zw1wbgf0zt5cbiagpha e3sgchjvchmubgfizwwgfx08l3a xg48l3rlbxbsyxrlplxuiiwiaw1wb3j0lw1hcc5qc29uijoie1xuicbcimltcg9ydhncijoge1xuicagifwidnvlxci6ifwiahr0chm6ly91bnbrzy5jb20vqhz1zs9ydw50aw1llwrvbuazljiumzevzglzdc9ydw50aw1llwrvbs5lc20tynjvd3nlci5qc1wixg4gih1cbn0ifq step to reproduce let vue compile the code what be expect it should compile and run what be actually happen throw error I already raise this in vite please refer to the above issue for screenshot and log |
vuejscore | event be not emit on async custom element | Bug | version 3 2 31 reproduction link codesandbox io step to reproduce click button in the reproduction sandbox to render customevent detail under each one what be expect custemevent detail to be render under the second button async what be actually happen event be not emit from the second button async and nothing be render |
vuejscore | when use custom v model with | Bug | version 3 2 31 reproduction link gitee com step to reproduce 1 create a vue3 project with vite 2 write a parent component and a child component in |
vuejscore | ssr leaks internal property in the render output | Bug | version 3 2 31 reproduction link sfc vuejs org eyjbchaudnvlijoiphnjcmlwdcbzzxr1cd5cbmltcg9ydcb7ihjlzib9igzyb20gj3z1zsdcblxuy29uc3qgbxnnid0gcmvmkcdizwxsbybxb3jszcenkvxuy29uc3qgcm9vdgvsid0gcmvmkclcbjwvc2nyaxb0plxuxg48dgvtcgxhdgu xg4gidxomsbyzwy9xcjyb290zwxcij57eybtc2cgfx08l2gxplxupc90zw1wbgf0zt4ilcjpbxbvcnqtbwfwlmpzb24ioij7xg4gifwiaw1wb3j0c1wioib7xg4gicagxcj2dwvcijogxcjodhrwczovl3nmyy52dwvqcy5vcmcvdnvllnj1bnrpbwuuzxntlwjyb3dzzxiuanncilxuicb9xg59in0 step to reproduce 1 create a sfc with a single root node 2 assign a template ref to that root node 3 render app with rendertostre 4 the output generate code have a ref key property what be expect the generate html should not contain any internal property use by the code generator what be actually happen the generate html contain a ref key property this only happen if the sfc have a single node where the template ref be assign |
vuejscore | compute property don t work with typescript type predicate properly | null | version 3 2 31 reproduction link stackblitz com step to reproduce to reproduce from the minimal reproduction link 1 open 2 run npm run typecheck in the terminal to reproduce from scratch 1 create a new component that use typescript 2 create a user define type guard function type predicate documentation use type predicate 3 create a ref that can be use as input to the previously create function 4 create a compute that return the value of call the function with the ref 5 create an if statement in the script tag or the template tag that use the compute and inside the if access a property of the ref that be only present in one of its union type 6 run vue tsc to type check the component what be expect no error appear in the terminal also if a linter be configure it doesn t show error what be actually happen typescript error ts2339 appear in the terminal error ts2339 property swim do not exist on type swim string fly string property swim do not exist on type fly string even though call the type guard function directly doesn t raise an error it should also work with compute property to allow reusable code code vue |
vuejscore | attribute inheritance inconsistent across production and development | Bug | version 3 2 31 reproduction link provide below step to reproduce open development and production link compare whether class red bg be apply to the button development vue sfc link eyjbchaudnvlijoiphnjcmlwdcbzzxr1cd5cbmltcg9ydcbneuj1dhrvbibmcm9ticcul015qnv0dg9ulnz1zsdcbjwvc2nyaxb0plxuxg48dgvtcgxhdgu xg4gidxneuj1dhrvblxuicagigvuywjszwrcbiagicbidxr0b25cbiagicbjbgfzcz1cinjlzc1iz1wixg4gica xg4gicagsgvsbg8gd29ybgrcbiagpc9neuj1dhrvbj5cbjwvdgvtcgxhdgu xg5cbjxzdhlszt5cbiaglnjlzc1izyb7xg4gicagymfja2dyb3vuzc1jb2xvcjogcmvkxg4gih1cbjwvc3r5bgu xg4ilcjpbxbvcnqtbwfwlmpzb24ioij7xg4gifwiaw1wb3j0c1wioib7xg4gicagxcj2dwvcijogxcjodhrwczovl3vucgtnlmnvbs9adnvll3j1bnrpbwutzg9tqdmumi4zms9kaxn0l3j1bnrpbwutzg9tlmvzbs1icm93c2vylmpzxcisxg4gicagxcjfdnvlxci6ifwiahr0chm6ly91bnbrzy5jb20vqhz1zs9ydw50aw1llwrvbuazljiumzevzglzdc9ydw50aw1llwrvbs5lc20tynjvd3nlci5wcm9klmpzxcjcbiagfvxufsisik15qnv0dg9ulnz1zsi6ijxzy3jpchqgc2v0dxa xg5pbxbvcnqgeybkzwzpbmvqcm9wcyb9igzyb20gj3z1zsdcblxuzgvmaw5luhjvchmoe1xuxhrlbmfibgvkoibcb29szwfulfxuicbidxr0b246iejvb2xlyw4sxg59kvxupc9zy3jpchq xg5cbjx0zw1wbgf0zt5cbiagphrlbxbsyxrlihytawy9xcjlbmfibgvkxci xg4gicagpgj1dhrvbib2lwlmpvwiynv0dg9uxci xg4gicagica8c2xvdcavplxuicagidwvynv0dg9uplxuica8l3rlbxbsyxrlplxupc90zw1wbgf0zt4ifq vue toggle in import map production vue sfc link eyjbchaudnvlijoiphnjcmlwdcbzzxr1cd5cbmltcg9ydcbneuj1dhrvbibmcm9ticcul015qnv0dg9ulnz1zsdcbjwvc2nyaxb0plxuxg48dgvtcgxhdgu xg4gidxneuj1dhrvblxuicagigvuywjszwrcbiagicbidxr0b25cbiagicbjbgfzcz1cinjlzc1iz1wixg4gica xg4gicagsgvsbg8gd29ybgrcbiagpc9neuj1dhrvbj5cbjwvdgvtcgxhdgu xg5cbjxzdhlszt5cbiaglnjlzc1izyb7xg4gicagymfja2dyb3vuzc1jb2xvcjogcmvkxg4gih1cbjwvc3r5bgu xg4ilcjpbxbvcnqtbwfwlmpzb24ioij7xg4gifwiaw1wb3j0c1wioib7xg4gicagxcjfdnvlxci6ifwiahr0chm6ly91bnbrzy5jb20vqhz1zs9ydw50aw1llwrvbuazljiumzevzglzdc9ydw50aw1llwrvbs5lc20tynjvd3nlci5qc1wilfxuicagifwidnvlxci6ifwiahr0chm6ly91bnbrzy5jb20vqhz1zs9ydw50aw1llwrvbuazljiumzevzglzdc9ydw50aw1llwrvbs5lc20tynjvd3nlci5wcm9klmpzxcjcbiagfvxufsisik15qnv0dg9ulnz1zsi6ijxzy3jpchqgc2v0dxa xg5pbxbvcnqgeybkzwzpbmvqcm9wcyb9igzyb20gj3z1zsdcblxuzgvmaw5luhjvchmoe1xuxhrlbmfibgvkoibcb29szwfulfxuicbidxr0b246iejvb2xlyw4sxg59kvxupc9zy3jpchq xg5cbjx0zw1wbgf0zt5cbiagphrlbxbsyxrlihytawy9xcjlbmfibgvkxci xg4gicagpgj1dhrvbib2lwlmpvwiynv0dg9uxci xg4gicagica8c2xvdcavplxuicagidwvynv0dg9uplxuica8l3rlbxbsyxrlplxupc90zw1wbgf0zt4ifq vue toggle in import map what be expect for the development build to have consistent class inheritance logic as the production build what be actually happen the class be only be inherit in development |
vuejscore | provide null to a readonly property of a htmlelement lead to an error instead of a warning | Bug | version 3 2 31 reproduction link sfc vuejs org eyjbchaudnvlijoiphrlbxbsyxrlplxuica8c2vszwn0iglkpvwizm9vxcigbmftzt1cimzvb1wiidp0exblpvwidw5kzwzpbmvkxciglz5cbjwvdgvtcgxhdgu iiwiaw1wb3j0lw1hcc5qc29uijoie1xuicbcimltcg9ydhncijoge1xuicagifwidnvlxci6ifwiahr0chm6ly91bnbrzy5jb20vqhz1zs9ydw50aw1llwrvbuazljiumzevzglzdc9ydw50aw1llwrvbs5lc20tynjvd3nlci5qc1wixg4gih1cbn0ifq step to reproduce writing in a vue component to see an error in the console type be a read only property of htmlselectelement browser microsoft edge version 99 0 1150 30 official build 64 bit chrome version 99 0 4844 51 official build 64 bit error in the console typeerror can not set property type of which have only a getter runtime dom esm bundler js 830f 261 browser firefox version 98 0 64 bit error in the console typeerror set getter only property type what be expect write in the template throw a warning and not an error this be what we should have also when value null what be actually happen a javascript error be throw instead of a warning in the function patchdomprop of runtime dom esm bundler js it try to set an empty string to the read only property el key the error should be manage by wrap this line into a try catch |
vuejscore | template ref in v for not work | Bug | version 3 2 31 reproduction link stackblitz com step to reproduce open the devtool and look at the console log from onmounte you now see three log each represent a different template ref log one and three be a single template ref and an array fill with function ref they be work fine as expect the issue be that the second ref be not return an array of element from the v for but stay empty as initialize what be expect template ref on the v for should be a dom nodelist or an array of domelement what be actually happen the initialized ref stay empty |
vuejscore | v show be invalid on the dev root fragment node | Bug | version 3 2 31 reproduction link sfc vuejs org eyjbchaudnvlijoiphnjcmlwdcbzzxr1cd5cbmltcg9ydcb7ihjlzib9igzyb20gj3z1zsdcbmltcg9ydcbdb21wigzyb20gjy4vq29tcc52dwunxg5cbmnvbnn0ihnob3cgpsbyzwyodhj1zslcbnnldeludgvydmfskcgpid0 ihtcbiagc2hvdy52ywx1zsa9icfzag93lnzhbhvlxg59lcaxmdawkvxupc9zy3jpchq xg5cbjx0zw1wbgf0zt5cbiagica8q29tccb2lxnob3c9xcjzag93xci pc9db21wplxupc90zw1wbgf0zt5cbiisimltcg9ydc1tyxauannvbii6intcbiagxcjpbxbvcnrzxci6ihtcbiagicbcinz1zvwioibcimh0dhbzoi8vdw5wa2cuy29tl0b2dwuvcnvudgltzs1kb21amy4yljmxl2rpc3qvcnvudgltzs1kb20uzxntlwjyb3dzzxiuanncilxuicb9xg59iiwiq29tcc52dwuioii8c2nyaxb0ihnldhvwplxuxg48l3njcmlwdd5cblxuphrlbxbsyxrlplxuica8is0tiejyb2tlbiegls0 xg5cddxkaxy xg4gicagpha agvsbg88l3a xg4gidwvzgl2plxupc90zw1wbgf0zt4ifq step to reproduce observation hello what be expect hello should twinkle what be actually happen v show false invalid |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.