repository stringclasses 156 values | issue title stringlengths 1 1.01k ⌀ | labels stringclasses 8 values | body stringlengths 1 270k ⌀ |
|---|---|---|---|
vuejscore | unable to unset a form prop on a button with null value | Bug | version 3 0 4 reproduction link step to reproduce run the fiddle above check the console see an error what be expect form attribute be be unset successfully what be actually happen console warning fail set prop form on value null be invalid typeerror can not set property form of which have only a getter 1788 attempt to solve a similar problem make vue patch this with setattribute instead of set it as a domprop but the add value check make vue fall back to a domprop assignment for non string value note also that set it as an empty string be not a proper solution as this break the button s form property s inheritance of the form s i d it might be nest within so we need to use setattribute regardless of the type of value |
vuejscore | add to this option compute during beforecreate only work if compute be already define on component | Bug | version 3 0 4 reproduction link step to reproduce create a component app with a mixin that add to this option compute js const mixin beforecreate if this option compute this option compute this option compute value return work vue createapp mixin mixin compute uncommente this line make it work mount app what be expect expect this value to be work what be actually happen this value be undefined in vue 2 this work in vue 3 this only work if the compute option be already define |
vuejscore | fix compiler core should add the dev root fragment flag to v if branch | Bug | close 2780 |
vuejscore | html comment between component root element prevent apply class to element after comment | Bug | version 3 0 4 reproduction link step to reproduce try to remove comment between divs in helloworld component and result html will differ text I also want to be bold will become bold what be expect class should be pass to the root element in both case second component text should also be bold what be actually happen due to presence of comment between divs class be not apply to the second div |
vuejscore | view isn t update in a weird case combination of many factor transition injection compute | Bug | version 3 0 4 reproduction link image step to reproduce follow the link although the case seem not that minimal I can t figure out a small one any small change may make the demo work as expect what be expect after the button be click it should disappear what be actually happen it stay there |
vuejscore | transition effect of v show leave be not work in some case | Bug | version 3 0 4 reproduction link step to reproduce when to watch and use transition reference datum the transition effect of v show leave be not work it work well when use as v if it work well if the code use as v if be present together case where comment be remove from minimal link it work well if temp be not use in template what be expect apply transition when v show leave what be actually happen display none style add and transition not active |
vuejscore | fix runtime core instancewatch should pass this proxy to source as the first argument | Bug | close 2731 |
vuejscore | toref function return type get a union of ref | Bug | version 3 0 4 reproduction link about blank about blank step to reproduce interface state somevalue string number string number const state reactive somevalue 0 const somevalueref toref state somevalue what be expect typeof somevalueref should be ref what be actually happen typeof somevalueref be ref ref ref number string maybe add api name toshallowref |
vuejscore | inconstant attr inheritance behavior in production and development again | Bug | version 3 0 4 reproduction link image problem state in be solve however the behavior isn t correct in other case step to reproduce follow the link npx vite dev npx vite build prod then serve the dist what be expect constant behavior what be actually happen inconstant behavior |
vuejscore | script setup sometimes generate invalid code when use defineemit and defineprop | Bug | version 3 0 4 reproduction link step to reproduce just run the repro with npm run dev what be expect compiler should generate valid code what be actually happen code fail with syntax error the problem be in this line from output javascript import ref from module vue js the precede comma be not valid in this place of import statement a workaround be change the order of import so that defineemit and defineprop be trail I m not sure if this be a vite specific error I can move the issue if need |
vuejscore | template compile will generate useless createvnode import when the component can be statically optimize | Bug | version 3 0 4 reproduction link 7b 22src 22 3a 22 3ctemplate 3e 5cn 20 20 3ctemplate 20v if 3d 5c 22column render 5c 22 3e 5cn 20 20 20 20 3crender 20 3arender 3d 5c 22 20 3d 3e 20column render row 2c 20index 5c 22 20 2f 3e 5cn 20 20 3c 2ftemplate 3e 5cn 20 20 3ctemplate 20v else 3e 5cn 20 20 20 20 7b 7b 20row 5bcolumn key 5d 20 7d 7d 5cn 20 20 3c 2ftemplate 3e 5cn 3c 2ftemplate 3e 22 2c 22options 22 3a 7b 22mode 22 3a 22module 22 2c 22prefixidentifiers 22 3afalse 2c 22optimizeimports 22 3afalse 2c 22hoiststatic 22 3afalse 2c 22cachehandlers 22 3afalse 2c 22scopeid 22 3anull 2c 22inline 22 3afalse 2c 22ssrcssvar 22 3a 22 7b 20color 20 7d 22 2c 22bindingmetadata 22 3a 7b 22testcomponent 22 3a 22setup 22 2c 22foo 22 3a 22setup 22 2c 22bar 22 3a 22props 22 7d 7d 7d 7b 22src 22 3a 22 3ctemplate 3e 5cn 20 20 3ctemplate 20v if 3d 5c 22column render 5c 22 3e 5cn 20 20 20 20 3crender 20 3arender 3d 5c 22 20 3d 3e 20column render row 2c 20index 5c 22 20 2f 3e 5cn 20 20 3c 2ftemplate 3e 5cn 20 20 3ctemplate 20v else 3e 5cn 20 20 20 20 7b 7b 20row 5bcolumn key 5d 20 7d 7d 5cn 20 20 3c 2ftemplate 3e 5cn 3c 2ftemplate 3e 22 2c 22options 22 3a 7b 22mode 22 3a 22module 22 2c 22prefixidentifiers 22 3afalse 2c 22optimizeimports 22 3afalse 2c 22hoiststatic 22 3afalse 2c 22cachehandlers 22 3afalse 2c 22scopeid 22 3anull 2c 22inline 22 3afalse 2c 22ssrcssvar 22 3a 22 7b 20color 20 7d 22 2c 22bindingmetadata 22 3a 7b 22testcomponent 22 3a 22setup 22 2c 22foo 22 3a 22setup 22 2c 22bar 22 3a 22props 22 7d 7d 7d step to reproduce image 7b 22src 22 3a 22 3ctemplate 3e 5cn 20 20 3ctemplate 20v if 3d 5c 22column render 5c 22 3e 5cn 20 20 20 20 3crender 20 3arender 3d 5c 22 20 3d 3e 20column render row 2c 20index 5c 22 20 2f 3e 5cn 20 20 3c 2ftemplate 3e 5cn 20 20 3ctemplate 20v else 3e 5cn 20 20 20 20 7b 7b 20row 5bcolumn key 5d 20 7d 7d 5cn 20 20 3c 2ftemplate 3e 5cn 3c 2ftemplate 3e 22 2c 22options 22 3a 7b 22mode 22 3a 22module 22 2c 22prefixidentifiers 22 3afalse 2c 22optimizeimports 22 3afalse 2c 22hoiststatic 22 3afalse 2c 22cachehandlers 22 3afalse 2c 22scopeid 22 3anull 2c 22inline 22 3afalse 2c 22ssrcssvar 22 3a 22 7b 20color 20 7d 22 2c 22bindingmetadata 22 3a 7b 22testcomponent 22 3a 22setup 22 2c 22foo 22 3a 22setup 22 2c 22bar 22 3a 22props 22 7d 7d 7d what be expect createvnode shouldn t be import what be actually happen createvnode be import |
vuejscore | errorcapture not trigger by error in async setup during ssr | Bug | version 3 0 4 reproduction link step to reproduce js const createssrapp definecomponent require vue const rendertostre require vue server renderer const child definecomponent name child1 setup some error throw new error child1 error template test const asyncchildren definecomponent name asyncchildren async setup some async error e g axio fetch throw new error async child error return promise reject async child error template test abc const app createssrapp name app component child asyncchildren template errorcapture error console log errorcapture error app config errorhandler error console log errorhandler error rendertostre app then re console log rendertostre re catch error console log rendertostre error error what be expect async setup function can throw async error to parent what be actually happen no handle async error onerrorcapture hook and errorhandler can capture the async error but not capture the async setup function async error in the package server renderer there be also no error handle for serverprefetch and async setup l96 |
vuejscore | script setup ref import from a vue file doesn t work after build | Bug | version 3 0 4 reproduction link step to reproduce create a fresh vitejs app helloworld vue app vue what be expect the value should be true false what be actually happen after build the ref variable output a weird value if I try to do isactive isactive on app vue I ve get no error on dev but get error illegal reassignment to import isactive when I try to build build link |
vuejscore | attribute with a false value still be add to the dom | Bug | version 3 0 4 reproduction link step to reproduce datum javascript datum return valuea false valueb true valuec null template html list item a false list item b true list item c null what be expect attribute with boolean false value will not be add to the the list should be render as html list item a false list item b true list item c null what be actually happen the boolean false value be consider as a string and add to the attribute html list item a false list item b true list item c null in vue v2 the boolean value will not be add when the bind value be false |
vuejscore | this be no long pass for the first argument of this watch | Bug | version 3 0 4 reproduction link vue 2 vue 3 by skirtle code at step to reproduce the first argument exporfn of this watch and vue watch couldn t receive the first argument vm which equal to this any more what be expect add the first argument back or write this change in doc what be actually happen only this leave currently since vue 3 |
vuejscore | fix compiler sfc removespecifi issue when remove initial import script setup | Bug | fix an issue with removespecifi in compilerscript ts when there be several initial import remove ts import defineprop defineemit ref from vue be be compile to ts import ref from vue add a test case in compilescript spec ts |
vuejscore | datum property read in prop watch treat as a rendering dependency | Bug | version 3 0 4 reproduction link step to reproduce 1 click button 1 2 click button 2 3 note the logging what be expect click button 2 should not cause anything to be log what be actually happen click button 2 be log a message indicate that the component have re render click the first button cause a prop to change trigger the watcher the watcher access a property which be then incorrectly track as a render dependency I report this previously as part of 2521 but it be only partially fix |
vuejscore | can not use v for in the slot | Bug | version 3 0 4 reproduction link step to reproduce when use v for in the slot if the initial list object an error will be report directly in the subsequent push what be expect correctly perform responsive rendering what be actually happen unhandled error during execution of scheduler flush this be likely a vue internal bug please open an issue at find this problem in 3 0 4 |
vuejscore | flip animation not apply when first item splice | Bug | version 3 0 4 reproduction link work vs broke step to reproduce list move transition that s at this link change the remove method to match js this item splice 0 1 what be expect the first item in the array be remove and an animation smooth out the other item move into the first spot what be actually happen it jerkily move the item to the first index |
vuejscore | script setup ref import from a vue file doesn t seem to update when use in anothr component s template | Bug | version 3 0 3 reproduction link step to reproduce yarn yarn dev open browser and click the button what be expect othercomponentref and othercomponentreactive both change or not what be actually happen othercomponentreactive work fine othercomponentref work in |
vuejscore | true value and false value be ignore on initial render | Bug | version 3 0 3 reproduction link step to reproduce what be expect checkbox expect to be check since model be false and true value false what be actually happen checkbox be not check on first render after you click it once it actually work okay |
vuejscore | img tag attribute width height render with 0 value when null undefined specify | Bug | version 3 0 3 reproduction link step to reproduce insert an image via the img tag and specify width or height as null or undefined what be expect attribute width and height have not be render accord with the vue 3 documentation attribute what be actually happen attribute width and height have be render with 0 value |
vuejscore | can t access ref correctly if component be import by defineasynccomponent | Bug | version 3 0 3 reproduction link step to reproduce 1 import component by use defineasynccomponent for example component item 2 define ref in template for example 3 access ref in manual event callback like click 4 access funcion in component item 5 use this ref item do fail 6 use this ref item ref item do success what be expect access ref by this ref item what be actually happen have to access ref by use this ref item ref item |
vuejscore | fix runtime core optimization the logic of set prop close 2651 | Bug | close 2651 if app mixin call app mixin will be it will become prop after normalizepropsoption call |
vuejscore | teleport to svg element fail to render | Bug | version 3 0 2 reproduction link step to reproduce 1 create an svg element 2 try to teleport an element e g circle into the svg element what be expect the circle be render inside the svg element what be actually happen the circle be not render |
vuejscore | mixin trigger an emitted event warn | Bug | version 3 0 2 reproduction link step to reproduce 1 click the button note the warning 2 remove the line app mixin and re run the fiddle 3 click the button no long trigger a warning what be expect no warning even with the mixin what be actually happen text vue warn component emit event update modelvalue but it be neither declare in the emit option nor as an onupdate modelvalue prop the warning be only suppose to be show when the emit option be specify nothing in this example specify an emit option so it shouldn t be show the same problem occur when use the mixin or extend option I believe it s cause by an inconsistency in normalizeemitsoption l152 without the mixin it return null with the mixin it return an empty object which be enough to trigger the warning originally observe in |
vuejscore | component api provide doesn t support symbol | Bug | version 3 0 2 reproduction link bug reproduction on codepen step to reproduce try provide a symbol it will not inject what be expect for the symbol provide to work especially because use provide in setup and app provide support symbol provide and be document what be actually happen symbol provide be not work |
vuejscore | null event crash when call | Bug | version 3 0 2 reproduction link step to reproduce compiler optimization cachehandler change the behavior of the link fiddle basically without the optimization you can bind null as an event handler and everything work fine I e nothing happen when event be call if you compile with cachehandler the follow code be generate 7b 22src 22 3a 22 3cinput 20 40blur 3d 5c 22null 5c 22 3e 22 2c 22options 22 3a 7b 22mode 22 3a 22module 22 2c 22prefixidentifiers 22 3afalse 2c 22optimizeimports 22 3afalse 2c 22hoiststatic 22 3atrue 2c 22cachehandlers 22 3atrue 2c 22scopeid 22 3anull 2c 22ssrcssvar 22 3a 22 7b 20color 20 7d 22 2c 22bindingmetadata 22 3a 7b 22testcomponent 22 3a 22setup 22 2c 22foo 22 3a 22setup 22 2c 22bar 22 3a 22props 22 7d 2c 22optimizebinding 22 3afalse 7d 7d it s very easy to see that it s call null args which of course fail at runtime what be expect same behavior no crash what be actually happen different behavior crash when optimize you might ask isn t it stupid bind null to an event it s pretty useful when you want to listen to an event sometimes but not always or when you re pass through optional handler from outside code it can be do by use the event member syntax onevent member or easily inside a functional component the alternative would be to coalesce a no op function or don t bind the event at all which be a lot less convenient than pass null in any case the fact that non optimize and optimize case do not behave the same be bad |
vuejscore | transition component do not work with leave from | Bug | version 3 0 2 reproduction link step to reproduce what be expect when trigger leave the font color should translate from red to default what be actually happen 1 property in class leave from not work 2 the class leave from affect the normal operation of transition component the reason be relate to the process of add remove css class I would like to fix it |
vuejscore | v show conflict with string base style bind | Bug | version 3 0 2 reproduction link step to reproduce click change style string button in the pen what be expect the red div be not expect to show under any circumstance since it s v show be set to false what be actually happen update the reactive style string override the display none generate by v show cause the div to appear this behavior only happen if the style bind be a string v show work as expect if style bind be an object one would expect the behavior to be consistent regardless the type of the style bind |
vuejscore | lang on a html tag produce vuecompilererror invalid end tag | Bug | version 16 0 0 rc 0 reproduction link step to reproduce clone my repro project yarn and yarn webpack template what be expect compilation succeed what be actually happen error in src test vue module error from node modules vue loader dist index js vuecompilererror invalid end tag at src test vue 4 2 2 3 4 5 src index js 1 0 21 remove lang attribute fix this vuejs vue loader 1726 be close as not be able to repro but it still win t compile |
vuejscore | handler depend on outer scope s value in nest slot be not update | Bug | version 3 0 2 reproduction link step to reproduce image 1 remove at key 1 image 2 create at key 2 image what be expect the insert item should be place after key 2 image what be actually happen it be place after key 3 image it can be assume that index be not collect as the dependency of the button group since when render it the value be not access what s more it work in vue2 |
vuejscore | fragment dynamic component with table keep table element in dom in production mode | Bug | version 3 0 2 reproduction link step to reproduce yarn build serve the fist folder prod like click on table button click on index button what be expect the table should disappear what be actually happen it stay when go back to index couldn t reproduce on a jsfiddle from |
vuejscore | keepalive include property bind responsive datum keepalive include | Bug | version 3 0 2 reproduction link step to reproduce the link be the github address you need to perform the follow step to run the project 1 npm install 2 npm run dev the project run enter the a component click the to two button to enter the b component in component b click the goback button to return to component a github 1 npm install 2 npm run dev a to two b b goback a what be expect 1 when display component a component a should be cache by keepalive 2 when component a enter component b both component a and component b should be cache by keepalive 3 when component b return to component a component b should no long be cache 1 a a keepalive 2 a b a b keepalive 3 b a b what be actually happen expectation 1 and expectation 2 meet expectation it be expect that component b in 3 be still cache when component b be enter again the image do not execute the network request 1 2 3 b b network I use the include property of keep alive to bind a responsive array hope to control the cache result of keepalive through the array to achieve the operation effect of scene switch in the native app taskstack these operation be execute perfectly in vue 2 x you can check this link but there be unexpected error in vue 3 I think this should be a bug in vue 3 the component name remove from include be not clear from the cache keep alive include keepalive app taskstack vue 2 x vue 3 vue 3 bug include |
vuejscore | inconstant inheritattrs behavior in production and development | Bug | version 3 0 2 reproduction link step to reproduce 1 npm run dev image 2 npm run build then serve dist image what be expect I m not sure which be expect by vue I expect the dev behavior what be actually happen behavior be inconstant |
vuejscore | warn extraneous non emit event listener show up even when emit be set | Bug | version 3 0 2 reproduction link step to reproduce create a fragment component with setup as render function then define a custom event listen to the custom event warning should pop up in the console when load the fragment component e g an input component as child component javascript import definecomponent h from vue export default definecomponent prop msg string emit test change setup prop emit return return h h1 prop msg h input onchange evt emit test change evt parent component vue what be expect the warning should not appear what be actually happen a warning appear extraneous non emit event listener testchange be pass to component but could not be automatically inherit because component render fragment or text root node if the listener be intend to be a component custom event listener only declare it use the emit option event work fine |
vuejscore | slot with dynamic name attribute do not update content | Bug | version 3 0 2 reproduction link step to reproduce go to and click the tab what be expect the content of tab vue s slot should change what be actually happen the content of the first tab display but never change I have the same code in a vue 2 sandbox and it work as expect see I have look but can not find any document reason why this wouldn t work the same in vue 3 |
vuejscore | collection add set expose raw target | Bug | version 3 0 2 reproduction link step to reproduce call set add or map set those method be specify to return the collection itself so they can be chain set add 1 add 2 add 3 what be expect those method should return the reactive collection so that set add 1 set be true and reactivity work when chain what be actually happen those method return the raw collection break the collection contract and break reactivity I point a few other thing that be less clear cut bug but probably not desirable behavior e g observable difference between reactive and non reactive collection behavior here |
vuejscore | datum read in watch be treat as a rendering dependency | Bug | version 3 0 2 reproduction link step to reproduce 1 click button 1 note the logging the root component have update unnecessarily if you click button 1 again nothing will happen 2 click button 2 both the root and child component will update that be expect 3 click button 1 again this time the child component update unnecessarily what be expect click button 1 update the count property that shouldn t trigger any rendering what be actually happen extra rendering be occur first in the parent component and then in the child the key to this be the watch if you comment out the content of the handler it all work as expect with button 1 not trigger any render the first problem be cause by the immediate true it seem that any reactive datum read during that initial call be treat as a render dependency of the parent component presumably because the parent component be still consider to be render at that point the second problem be similar the watcher be trigger by the prop change and the dependency seem to be register against the rendering of the child update the first problem can also be trigger use a create hook instead of an immediate watcher see to reproduce that variant of the problem |
vuejscore | use bundler build with compiler vue esm bundler js with webpack in production mode include babel parser in final bundle | Bug | version 3 0 2 reproduction link step to reproduce 1 create new project with vue cli select vue 3 preset 2 modify build command in package json by add report 3 create vue config js and enable runtime compilation runtimecompiler true which switch vue alia to vue esm bundler js 3 run yarn build 4 check dist report html what be expect vendor bundle should not include babel parser package 230 kb what be actually happen babel parser be part of the production bundle as anything from babel parser be not include in browser compiler build of vue vue esm browser js for example it should not be include when use with bundler build I m not an expert on vue 3 codebase but it seem problem be in the l90 processexpression function if dev browser simple in browser validation same logic in 2 x validatebrowserexpression node context asparam asrawstatement return node same code in vue compiler core dist compiler core esm bundler js npm package if process env node env production true simple in browser validation same logic in 2 x validatebrowserexpression node context asparam asrawstatement return node the code which be intend to run in the browser be use only in dev build and eliminate in production build which leave the rest of the processexpression function which be use babel parser in the bundle |
vuejscore | rendertostre render fragment instead of tag provide as prop to transitiongroup | Bug | version 3 0 2 reproduction link step to reproduce 1 clone git repo and run server js 2 browse localhost 8080 probably the most basic vue ssr app the world have ever see I hope it s enough of a reproduction to see the problem I encounter instead of run the server it will also be enough to just look at what the rendertostre function return this obviously win t show the hydration mismatch on client though what be expect render actual tag that be provide as prop what be actually happen it render fragment please let I know if this need more information and I ll try to provide cheer |
vuejscore | readonly a b c include track dependency even though array be nonreactive | Bug | version 3 0 2 reproduction link step to reproduce readonly a b c collect by dependency what be expect a b c should not be collect by dependency what be actually happen a b c collect by dependency |
vuejscore | kebab case prop on slot be not transform to camelcase | Bug | version 3 0 2 reproduction link step to reproduce open and you ll see that |
vuejscore | be break flicker when toggle really fast spam click a button to toggle | Bug | version 3 0 2 reproduction link step to reproduce spam click the show overlay button what be expect the fade transition should smoothly toggle between opacity 0 and opacity 1 no matter how fast you click what be actually happen the fade transition constantly show hide abruptly while spam click exactly same transition work smoothly in vue 2 here I be attach sandbox for that |
vuejscore | fallback slot content not render in nest component with slot | Bug | version 3 0 2 reproduction link step to reproduce follow the link image in vue2 it work image what be expect fallback content of inner be show what be actually happen not display |
vuejscore | parent doesn t skip transition component | Bug | version 3 0 1 reproduction link step to reproduce 1 open the production link 2 watch the console what be expect console output plain app in transition app in keep alive app in teleport app what be actually happen console output plain app in transition basetransition in keep alive app in teleport app in vue 2 the transition component be abstract and parent skip it so component could reach the real parent component now the parent of a component nest in an transition be a basetransition instance and add to the problem this component doesn t have a public proxy with a parent property so developer can t even manually skip it by call this parent parent |
vuejscore | access of array per index isn t track | Bug | version 3 0 1 reproduction link step to reproduce click the add item button what be expect array item grouping render what be actually happen use for index in array in compute or method when the array be initialize to empty add array item can not refresh the view |
vuejscore | nest transition render inside v slot never leave | Bug | version 3 0 1 reproduction link step to reproduce click go user index click home what be expect user index or rather the container to fade out then home to fade in what be actually happen content disappear and nothing can be display anymore come from when use a different transition mode as the default one you can clearly see that the leave element be remove right away without trigger the leaving transition the first wrapping router view be not need to reproduce the bug it s only need inside the child component the bug do not exist when no wrapping component router view be use workaround wrap the nest router view inside child component with an element like a div |
vuejscore | typeerror find non callable iterator raise in a wired condition I can t summarize it | Bug | version 3 0 1 reproduction link image the reproduction be extract from my real world project it seem vnode be pass to key to make it render you have multiple choice 1 comment any of or 1 remove the empty object inside button vue s mixin 1 remove the wrapper in inner vue step to reproduce follow the link what be expect it should render what be actually happen error raise |
vuejscore | dynamic event name bind with nullish value not work | Bug | version 3 0 1 reproduction link step to reproduce follow the link what be expect no error like vue2 see what be actually happen error happen |
vuejscore | watch can register it s effect on the wrong instance | Bug | version 3 0 0 step to reproduce I m in the process of port a smallish front end 10klocs from vue2 to vue 3 0 0 I have one mixin that install a watch and uninstall it like this abbreviate update function this dom update unwatch1 this dom update unwatch1 null const dom update reactive vm this dom update unwatch1 this watch dom update reactive this forceupdate beforeunmount function this dom update unwatch1 this dom update unwatch1 null call unwatch1 always trigger the follow vue js 1180 vue warn unhandled error during execution of beforeunmount hook at at vue js 1180 vue warn unhandled error during execution of scheduler flush this be likely a vue internal bug please open an issue at at vue js 212 uncaught in promise typeerror can not read property indexof of null at remove vue js 212 at object unwatch1 vue js 6489 at proxy beforeunmount util js 737 at callwitherrorhandle vue js 1296 at callwithasyncerrorhandle vue js 1305 at array hook weh hook weh vue js 3665 at invokearrayfns vue js 275 at unmountcomponent vue js 6157 at unmount vue js 6071 at patchkeyedchildren vue js 5892 remove vue js 212 anonymous vue js 6489 beforeunmount util js 737 callwitherrorhandle vue js 1296 it look like vue s unwatch callback as return from watch can not remove itself from instance effect since vue js read vue js 211 const remove arr el vue js 212 const I arr indexof el vue js 6489 remove instance effect runner since I m in the middle of a transition it s impossible for I to deduce a minimal test case I hope the trace be useful regardless the full unported vue2 base code can be find here still use beforedestroy instead of beforeunmount l696 what be expect unwatch as return from watch can be call without exception what be actually happen an exception be throw |
vuejscore | v on object syntax doesn t work with v if | Bug | version 3 0 0 reproduction link step to reproduce click on w v if button what be expect alert to work what be actually happen alert doesn t work |
vuejscore | feat runtime support delay initialize prop fix 2325 | Bug | 54ed759 ignore that value also can cause 2325 which be due to the order when initialize an element s attribute I believe similar problem may exist on other platform so I think it might be well to add delayinitprop to runtime core runtime core provide a render option call delayinitprop which receive el and key return whether delay or the priority benchmark loop vs bench js delayinitprop el hostelement key string number boolean return value true or number great than 0 mean put this prop at the end of the delay queue false or 0 mean no need to delay number less than 0 mean put this prop at the beginning of the delay queue the need for delay be weak runtime dom delay initialize value fix 2325 |
vuejscore | any content prevent slot component use default value | Bug | version 3 0 0 reproduction link step to reproduce there be a simple example you just need to check the element on the dev tool image image what be expect default value should be use for invalid content what be actually happen any content prevent use default value also a comment |
vuejscore | v show do not take effect with custom directive on parent | Bug | version 3 0 0 reproduction link step to reproduce 1 add any custom directive to a parent component 2 use v show directive in the child s root dom 3 if the value of v show be false the child be still show 4 change v show to v if and the child will not be show what be expect visually hide child element with v show even if parent have a custom directive what be actually happen the child element still appear |
vuejscore | possible dom update issue with input type range | Bug | version 3 0 0 reproduction link step to reproduce 1 click show modal button 2 type something into input 3 see range slider jumping correct itself what be expect render first tick display range value correctly what be actually happen range slider be jump correct itself when onmounte produce the next tick see for further detail and assumption that could be hepful |
vuejscore | toggle teleport disabled may create duplicate child | Bug | version 3 0 0 reproduction link step to reproduce click toggle twice then click toggle disabled once image what be expect no duplicate child what be actually happen there be duplicate child |
vuejscore | teleport child be immediately remove from html when disable true in transition | Bug | version 3 0 0 reproduction link step to reproduce follow the link what be expect when teleport be disabled it shouldn t be unmounted immediately inside transition what be actually happen it disappear immediately |
vuejscore | provide add with mixin override local injection | Bug | version 3 0 0 reproduction link step to reproduce follow the link what be expect show app app what be actually happen show noapp app |
vuejscore | text add with ime to input that have v model be go when the view be update | Bug | version 3 0 0 reproduction link step to reproduce 1 place an input or textarea with v model 2 type some text in language that can be unresolved state such as japanese or chinese 3 update view in some way what be expect nothing happen even if update what be actually happen the unresolved text will be go reproduce I m not use any delete key in the video not reproduce in vue js 2 x |
vuejscore | can t get value from datum in production mode | Bug | version 3 0 0 reproduction link step to reproduce 1 clone the repo 2 run npm I 3 run npm run build 4 run project from the dist folder 5 click to button and see the console you will get an error what be expect I want to get the value from datum what be actually happen I get an error when try to get value it happen when I have a base component with datum and provide I extend another component with the base component |
vuejscore | template compilation error if else with space between element do not work | Bug | version 3 0 0 reproduction link template explorer 7b 22src 22 3a 22 3cdiv 20id 3d 5c 22app 5c 22 3e 5cn 20 20 3c 20doesn t 20work 20 3e 5cn 20 20 3cspan 20v if 3d 5c 22a 5c 22 3e1 3c 2fspan 3e 20 3cspan 20v else if 3d 5c 22b 5c 22 3e2 3c 2fspan 3e 5cn 20 20 3c 20doesn t 20work 20 3e 5cn 20 20 3cspan 20v if 3d 5c 22a 5c 22 3e3 3c 2fspan 3e 20 3cspan 20v else if 3d 5c 22b 5c 22 3e4 3c 2fspan 3e 20 3cspan 20v else 3e5 3c 2fspan 3e 5cn 20 20 3c 20works 20 3e 5cn 20 20 20 3cspan 20v if 3d 5c 22b 5c 22 3e6 3c 2fspan 3e 3cspan 20v else 3e7 3c 2fspan 3e 5cn 20 20 20 5cn 20 20 20 3c 5cn 20 20 20outputs 3a 201 2023 204 2057 5cn 20 20 20but 20should 20output 3a 20137 5cn 20 20 20 3e 5cn 3c 2fdiv 3e 5cn 22 2c 22options 22 3a 7b 22mode 22 3a 22module 22 2c 22prefixidentifiers 22 3afalse 2c 22optimizeimports 22 3afalse 2c 22hoiststatic 22 3afalse 2c 22cachehandlers 22 3afalse 2c 22scopeid 22 3anull 2c 22ssrcssvar 22 3a 22 7b 20color 20 7d 22 2c 22bindingmetadata 22 3a 7b 22testcomponent 22 3a 22setup 22 2c 22foo 22 3a 22setup 22 2c 22bar 22 3a 22props 22 7d 7d 7d step to reproduce have an if else on element that be separate by a space on the same line what be expect the if else function correctly show only the if elseif else that it should instead of all of they and no warning return what be actually happen you get the error template compilation error v else v else if have no adjacent v if and the if else aren t handle properly |
vuejscore | directive on root element of component be not invoke when component have bind directive | Bug | version 3 0 0 reproduction link step to reproduce follow the link what be expect log 3 2 1 what be actually happen log 3 1 |
vuejscore | watcher for a route param be call when a user leave the route | Bug | version 3 0 0 reproduction link sfc enrnu8fyozam rwnl9azgu8mddf5gp09 0jbekdge2xddhn vtimmstt9nrduycspyf56xfhe2pyeujwsni1vhopdv1kxowso9hwwwusdhkyq2fzygbuwa dpv hdhborb4hofpekict4l d435l5xynqotnyoebctggqjvaoq gzqc665aurc8bafr0k2q81aq87vsb0xe4xasspflcd1mgua qapvtzzzaeenyukyv7z5pmks8j3rvaldtkkd1sbckpi5mqd1svlzybtlwgtxgceynaoxb5d2n9rczzpnoqtgjzenhysmgghtnmihuhgrpcbw6ertkt0row6lpbm5v3vngop67stb5ywlfa1xlefvccvzchrgmfa6xyefvjss4d10tzd 5xnue01duj xlidm6cfdm9dmhjwlbsjsotocz2p1f1ajf x3ne qtb6al4re6ys0ox3jx6pslshxcxmdwrn1zfhlgg3micnsjbtb6q6i1ma2gdmg11wvuj9tqafnb92ksyvfqfqlrbnfeuarh4iclc7omi7asnlfavw8oyfnokbtqummwx q561ifv3r7g36vdoef1gg9cj2hqeii7zvypgcefiw5 no vue router step to reproduce 1 click foo1 link in result tab 2 click bar link in result tab 3 fetch foo undefine will be show in console same code with vue v2 x do not show fetch foo undefine what be expect watcher for a route param be not call when a user leave the route same as v2 what be actually happen watcher for a route param be call when a user leave the route watcher get undefined as the route param it may be cause by this break change break change I don t think it s natural that we need to consider the possibility a route param be undefined in a route which require the param |
vuejscore | dynamicchildren be unmounted multiple time in some case | Bug | version 3 0 0 reproduction link step to reproduce just run and view the console log what be expect myt umounte be show once what be actually happen myt umounte be show twice I encounter this one when I have a onbeforeunmounte hook that couldn t handle be run twice then after debug I find that it be run even 4 time dig far I find out that this only happen in case of a component wrap into a parent div that have at least one dynamic property that reference a setup var dig even far I find that what happen be that when a setup var be be use the patchflag for that vnode be set to 8 when that happen it get add to the dynamicchildren of the encapsulating block together with the vnode for my test then later when unmounte the code end up here l2029 first the vnode for my test get unmounted call onbeforeunmounte in the process then next the wrapper div be also unmounted but because it also have the my test vnode as a child that be unmounted again later result in another onbeforeunmounte invocation notice that the component isn t patch double because of the optimize arg that s pass to the patcher which refrain it from patch its child maybe a similar approach can be use to prevent double unmounting of dynamicchildren |
vuejscore | ref in slot disappear when wrap teleport | Bug | version 3 0 0 reproduction link step to reproduce follow the link image what be expect ref ref2 ref ref3 should be bind when focus the input what be actually happen they be undefined |
vuejscore | nexttick don t work as expect | Bug | version 3 0 0 reproduction link step to reproduce just click on the button change lg and take a look into the console this var line 17 inside the nexttick be the window object and not the current instance what be expect this should be the current instance what be actually happen this be the window object to see how it s work with vue 2 and 3 i v create two fiddle vuejs 2 ex vuejs 3 ex |
vuejscore | errorcapture errorhandler can t catch error from create hook | Bug | version 3 0 0 reproduction link step to reproduce throw error from child component try to catch it via errorcapture in parent component try to catch it via global errorhandler what be expect error be catch what be actually happen error can t be catch |
vuejscore | errorcapture reverse behavior | Bug | version 3 0 0 reproduction link step to reproduce throw error from child component catch error in parent component via errorcapture hook return false as per documentation to prevent error propagation what be expect error be not propagate what be actually happen error propagate to window |
vuejscore | v model number do not work for select tag | Bug | version 3 0 0 reproduction link step to reproduce just select a number from the dropdown the type show up as string what be expect the type should be number what be actually happen the type be string this be work correctly in vue 2 see |
vuejscore | inconsistent event case for render function | Bug | version 3 0 0 reproduction link step to reproduce create a render function that recieve a custom event in eslint plugin vue the doc you recommend to use kebab case for event that be emit event name this cause some friction for I when use render function as when listen for those event in the prop arg of h we need to prefix the event name with on the name of the event to listen to however I look at the source and the only transformation do be that the first letter of the event be capitalise this mean that kebab case event as recommend would need to be listen to as onevent emit what be expect that the casing would adhere to either camel or kebab case listen for event not combine both what be actually happen its a mixture of both ontest event be the key require rather than either on test event as specify in the component be emit or ontestevent to avoid the need to wrap the event key in quote I think the doc should be update to clarify this inconsistency I ll create an issue in the docs repo to talk about this once this have be clarify |
vuejscore | watch trigger even if value be not change | Bug | version 3 0 0 reproduction link step to reproduce open console and watch output what be expect only one log message true false what be actually happen log fire every second with false false js const compute watch ref vue const source ref 0 const iszero compute source value 0 watch iszero prev next console log prev next fire every second setinterval source value 1000 this be part from doc watch the watch api be the exact equivalent of the component watch property watch require watch a specific data source and apply side effect in a separate callback function it also be lazy by default I e the callback be only call when the watch source have change |
vuejscore | memory leak in ssr | Bug | version 3 0 0 reproduction link step to reproduce 1 run yarn in both the rc5 and gm dir 2 run node test js in the rc5 dir note the two end number report 3 run node test js in the gm dir note the two end number report what be expect some memory should be reclaim by the gm run after the sleep step what be actually happen no memory be reclaim this be my good approximation of what we re see in a much more complicated ssr environment when we change dependency and only the vue specific dependency from the 3 0 0 rc 5 release to 3 0 0 we see a very clear memory leak |
vuejscore | error can not read property el of undefined in production mode | Bug | version 3 0 0 reproduction link step to reproduce 1 use vue cli to create a new project 2 put the code into your page s template const a 100 3 run yarn build 4 run http server dist 5 visit the page 6 error happen now what be expect it should wokr with the same as const a 100 what be actually happen runtime core esm bundler js 5c40 2020 uncaught typeerror can not read property el of undefined at cloneifmounte runtime core esm bundler js 5c40 2020 at mountchildren runtime core esm bundler js 5c40 4178 at mountelement runtime core esm bundler js 5c40 4103 at processelement runtime core esm bundler js 5c40 4075 at patch runtime core esm bundler js 5c40 3988 at mountchildren runtime core esm bundler js 5c40 4180 at mountelement runtime core esm bundler js 5c40 4103 at processelement runtime core esm bundler js 5c40 4075 at patch runtime core esm bundler js 5c40 3988 at componenteffect runtime core esm bundler js 5c40 4493 |
vuejscore | toggle nest component with async setup inside suspense fail | Bug | version 3 0 0 reproduction link step to reproduce click toggle child many time what be expect the child to display what be actually happen the child doesn t display and there be an error find with |
vuejscore | suspense component kill reactive change | Bug | version 3 0 0 reproduction link step to reproduce there be a really simple form with just two input when you change the input datum in the sandbox you will see that the form state win t change between suspense tag if the repo be not open please use the refresh button on top left of the sandbox browser what be expect the code tag under the suspense component should be reactive what be actually happen the reactive text be not change |
vuejscore | reactivity issue with property watch and emit | Bug | version 3 0 0 reproduction link step to reproduce on the minimal reproduction example click on via watch on component property what be expect it should display global indirectval what be actually happen it display global initialvalue on the minimal reproduction example you can replace with to show the behaviour with vue js 2 x be this an expect regression I ve read various migration stuff and didn t find any mention of this in the project that hit this issue the component be do stuff with textarea cursor component code l3 l33 |
vuejscore | unhandled error during execution of watcher callback and scheduler flush | Bug | version 3 0 0 reproduction link step to reproduce click the increment button what be expect this el should be define inside of the watcher like in vue 2 what be actually happen it be null |
vuejscore | beforeunmount be call twice | Bug | version 3 0 0 reproduction link reproduction 1 reproduction 2 use template have bug reproduction 2 use h behave correctly it could be a bug of vue compiler reproduction 2 1 a more compact reproduction of r2 r1 and r2 may be cause by different reason please have a look step to reproduce follow the link what be expect beforeunmount be call once what be actually happen beforeunmount be call twice it seem different child of a parent instance resolve to the same child instance the reproduction condition be quite wired update maybe it s relate to createblock |
vuejscore | watcheffect be call twice on initialisation | Bug | version 3 0 0 rc 11 reproduction link step to reproduce consider this component typescript setup const price ref 10 const history ref watcheffect history value push price change to price value return price history what be expect in rc 10 it only display one change when initialise price change to 10 what be actually happen in rc 11 it display this change twice |
vuejscore | v once clash with v if | Bug | version 3 0 0 rc 9 reproduction link step to reproduce 1 create a new vue 3 project through vue cli or vite 2 replace app vue with 3 run npm run serve or npm run dev with vite and try load the app in a browser what be expect the result webpage should display a what be actually happen error vue cli error fail to compile with 1 error 2 32 19 pm error in src app vue vue type template i d 7ba5bd90 module build fail from node modules vue loader v16 dist templateloader js typeerror can not read property 2 of undefined at injectprop my project path node modules vue compiler core dist compiler core cjs js 443 82 at createchildrencodegennode my project path node modules vue compiler core dist compiler core cjs js 2841 9 at createcodegennodeforbranch my project path node modules vue compiler core dist compiler core cjs js 2797 62 at array my project path node modules vue compiler core dist compiler core cjs js 2696 38 at traversenode my project path node modules vue compiler core dist compiler core cjs js 1681 19 at traversechildren my project path node modules vue compiler core dist compiler core cjs js 1624 9 at traversenode my project path node modules vue compiler core dist compiler core cjs js 1675 13 at traversechildren my project path node modules vue compiler core dist compiler core cjs js 1624 9 at traversenode my project path node modules vue compiler core dist compiler core cjs js 1675 13 at transform my project path node modules vue compiler core dist compiler core cjs js 1566 5 at object basecompile my project path node modules vue compiler core dist compiler core cjs js 4115 5 at object compile my project path node modules vue compiler dom dist compiler dom cjs js 3033 25 at docompiletemplate my project path node modules vue compiler sfc dist compiler sfc cjs js 580 34 at object compiletemplate my project path node modules vue compiler sfc dist compiler sfc cjs js 564 16 at object templateloader my project path node modules vue loader v16 dist templateloader js 32 37 src app vue vue type template i d 7ba5bd90 1 0 319 1 0 319 src app vue src main js multi webpack dev server client webpack hot dev server js src main js with vite typeerror can not read property 2 of undefined at injectprop my project path node modules vue compiler core dist compiler core cjs js 443 82 at createchildrencodegennode my project path node modules vue compiler core dist compiler core cjs js 2841 9 at createcodegennodeforbranch my project path node modules vue compiler core dist compiler core cjs js 2797 62 at array my project path node modules vue compiler core dist compiler core cjs js 2696 38 at traversenode my project path node modules vue compiler core dist compiler core cjs js 1681 19 at traversechildren my project path node modules vue compiler core dist compiler core cjs js 1624 9 at traversenode my project path node modules vue compiler core dist compiler core cjs js 1675 13 at traversechildren my project path node modules vue compiler core dist compiler core cjs js 1624 9 at traversenode my project path node modules vue compiler core dist compiler core cjs js 1675 13 at transform my project path node modules vue compiler core dist compiler core cjs js 1566 5 |
vuejscore | css scope not work when set inheritattrs false | Bug | version 3 0 0 rc 9 reproduction link step to reproduce 1 use nest component root dom at deep child 2 set inheritattrs false css scope not work we can use v bind attrs but maybe we can have simple method what be expect css scope work what be actually happen css scope not work |
vuejscore | regression slot be not re render when inside | Bug | version 3 0 0 rc 7 still an issue in late 3 0 0 rc 9 reproduction link working case with 3 0 0 rc 6 here step to reproduce put a reactive value to be render inside a slot wrap by a in the fiddle above the contrived example be use be div only to illustrate the issue as it do not make much sense in a real world use case what be expect the reactive value change should trigger a render and the slot should be update what be actually happen the slot be not update accordingly to the value change |
vuejscore | change event happen before v model update the value | Bug | version 3 0 0 rc 7 reproduction link step to reproduce 1 select a country from the dropdown list 2 no datum for the select country be show 3 select another country 4 the datum for the first country select be now show what be expect the first time the country be select to show datum for that country right away what be actually happen 1 the first time I select a country the selectedcountry ref variable be show as an object with the property value set to the country select 2 when the code try to access selectedcountry value it return null although when I debug in the devtool the selectedcountry be a valid object with the value property set to the country select I expect the v model on the select to automatically bind to the selectedcountry the first time I select a value |
vuejscore | with form input | Bug | version 3 0 0 rc 5 reproduction link step to reproduce 1 wait for the page to fully load 2 type something into the input 3 press the cancel button what be expect the content should disappear because of the v if what be actually happen the content do not disappear instead I get this warning vue warn unhandled error during execution of scheduler flush this be likely a vue internal bug please open an issue at at in chrome I get this error uncaught in promise typeerror can not read property parentnode of null at remove vue next 7235 at performremove vue next 5662 at remove vue next 5680 at object remove vue next 2317 at unmount vue next 5637 at patch vue next 4693 at componenteffect vue next 5248 at reactiveeffect vue next 391 at callwitherrorhandle vue next 1274 at flushjob vue next 1427 in firefox I get this error uncaught in promise typeerror child be null vue next 7235 vue next 5662 vue next 5680 vue next 2317 vue next 5637 vue next 4693 vue next 5248 vue next 391 vue next 1274 vue next 1427 vue next 7235 26 do any of the following seem to make this work and stop the error from happen remove the wrapping element remove the v model on the not type anything into the input before press the cancel button add an submit event handler to the add a wrapping around the |
vuejscore | transition group appear class not disappear inside suspense | Bug | version 3 0 0 rc 5 reproduction link step to reproduce npm I npm run dev start dev server and navigate to localhost 8080 index what be expect vue next 0 vue next 1 vue next 2 vue next 3 vue next 4 what be actually happen vue next 0 vue next 1 vue next 2 vue next 3 vue next 4 e g in parent vue component in child component item username |
vuejscore | move an element drop the ref | Bug | version 3 0 0 rc 5 reproduction link step to reproduce 1 open the console log 2 click the button 3 note the ref inputel be null what be expect inputel should reference the appropriate element what be actually happen it s null the example be attempt to move an input between the bottom and top of the component it be only ever in one place at once so the template use the same ref in both case it seem that remove a vnode trigger a null ref during unmounte this problem also impact one of the example in the documentation see I originally stumble across this while use v for with ref base on 1166 it would seem that may no long be support so I remove it from my example it s a bit unclear what s plan as I can t find an rfc and currently the vue 3 documentation just describe the vue 2 behaviour with a few addition about the composition api |
vuejscore | when the same component be bind to the same event the event will be problematic | Bug | version 3 0 0 rc 5 reproduction link step to reproduce 1 click button1 and button2 will echo noop 2 click toggle disable 3 click button1 will echo noop click button2 will echo twice click 4 toggle disable more button2 will echo any what be expect when bind dynamic event can trigger correct event what be actually happen not correct event |
vuejscore | v for render twice | Bug | version 3 0 0 rc 2 reproduction link step to reproduce 1 clone the reproduction repo 2 use cd move into it 3 yarn 4 yarn dev what be expect v for be correctly render what be actually happen v for render twice this be a very weird problem when you delete the scope style block of app vue it work when you delete the comment in helloworld vue s template block it work when you delete the custom directive v nothing in helloworld vue it work when you add v if datum to the container tag in helloworld vue it work |
vuejscore | strange behavior when use v model on the root element of a custom component have itself a v model | Bug | version 3 0 0 rc 1 reproduction link step to reproduce good enter 1 in the first wrap field the field stay at 1 and the display value be 100 bad enter 1 in the second unwrapped field the field now show 0 01 and the display value be 1 what be expect both field should stay at 1 and both value should be display at 100 what be actually happen second field be set to 0 01 and the display value be 1 |
vuejscore | v for with v else do not work on | Bug | version 3 0 0 rc 1 reproduction link step to reproduce from what I gather in vue 2 v for be low priority than v else so it should work correctly but update to vue 3 make this code no long work I look in the vue eslint plugin and they didn t add a warning for this because it s expect to work issuecomment 533372342 what be expect the loop work correctly what be actually happen message key be undefined |
vuejscore | hmr be not work under certain circumstance difficult to pin point the exact context patch issue | Bug | version 3 0 0 rc 1 reproduction link step to reproduce so with my team we ve be notice that in the last couple of vue vite version hmr be really not work anymore for we often time it give cryptic error in the console and difficult ro reproduce consistently it be probably due to multiple reason but I manage to isolate a bug at least I have an insanely hard time to make a minimal repro out of it because it seem really flaky but on my machine this minimal repro be fail everytime so yeah sorry you might see some stuff there that seem really randomly put but I swear if you remove one single line the bug do not show anymore xd just this single bug make hmr break and unusable for we I can provide machine specific info if you guy can t reproduce |
vuejscore | tailwind extract component and | Bug | version 3 0 0 rc 1 reproduction link step to reproduce 1 run terminal command npm run dev what be expect the custom color should appear on the button what be actually happen the compiler be add the component scope data name to the var but not the css variable declaration so the color be not be use I know var be experimental and this be probably an edge case but I figure it be worth mention if either the scope or var be remove the color work just fine |
vuejscore | about lifecycle of keep alive | Bug | version 3 0 0 rc 1 reproduction link step to reproduce 1 open link 2 open devtool 3 click button what be expect one activate hook what be actually happen create hook mount hook |
vuejscore | flaky error end be out of bound while work with | Bug | version 3 0 0 rc 1 reproduction link step to reproduce 1 clone repo run npm I and run npm run dev 2 open the localhost 3000 in browser 3 open in editor the file src component helloworld vue 4 edit |
vuejscore | parse template throw error missing end tag with newline | Bug | version 3 0 0 beta 17 reproduction link 7b 22src 22 3a 22 20 20 20 20 3cspan 5cr 5cn 20 20 20 20 20 20v if 3d 5c 22iswordlimitvisible 20 26 26 20type 20 3d 3d 3d 20 textarea 5c 22 5cr 5cn 20 20 20 20 20 20class 3d 5c 22el input count 5c 22 5cr 5cn 20 20 20 20 20 20 3e 7b 7b 20textlength 20 7d 7d 2f 7b 7b 20upperlimit 20 7d 7d 3c 2fspan 5cr 5cn 20 20 20 20 3e 22 2c 22options 22 3a 7b 22mode 22 3a 22module 22 2c 22prefixidentifiers 22 3afalse 2c 22optimizebinding 22 3afalse 2c 22hoiststatic 22 3afalse 2c 22cachehandlers 22 3afalse 2c 22scopeid 22 3anull 7d 7d 7b 22src 22 3a 22 20 20 20 20 3cspan 5cr 5cn 20 20 20 20 20 20v if 3d 5c 22iswordlimitvisible 20 26 26 20type 20 3d 3d 3d 20 textarea 5c 22 5cr 5cn 20 20 20 20 20 20class 3d 5c 22el input count 5c 22 5cr 5cn 20 20 20 20 20 20 3e 7b 7b 20textlength 20 7d 7d 2f 7b 7b 20upperlimit 20 7d 7d 3c 2fspan 5cr 5cn 20 20 20 20 3e 22 2c 22options 22 3a 7b 22mode 22 3a 22module 22 2c 22prefixidentifiers 22 3afalse 2c 22optimizebinding 22 3afalse 2c 22hoiststatic 22 3afalse 2c 22cachehandlers 22 3afalse 2c 22scopeid 22 3anull 7d 7d step to reproduce open the link and check the prompt textlength upperlimit what be expect parse success what be actually happen throw parse error vue template compilation error element be miss end tag |
vuejscore | type error typescript infer prop with default value as require in custom render function | Bug | version 3 0 0 beta 15 reproduction link step to reproduce 1 git clone kightlingerh vue type error reproduction git 2 cd vue type error reproduction 3 yarn 4 yarn tsc output src index ts 20 7 error ts6133 componentb be declare but its value be never read 20 const componentb definecomponent src index ts 23 32 error ts2769 no overload match this call the last overload give the follow error argument of type isfullheight true be not assignable to parameter of type vnodeprop v isvnode undefined symbol iterator undefine isfullheight boolean isthemeable boolean isfullheight boolean isthemeable boolean undefined property isthemeable be miss in type isfullheight true but require in type isfullheight boolean isthemeable boolean 23 return h componenta 24 typescript say prop isthemeable be require here 25 isfullheight true 26 node module vue runtime core dist runtime core d ts 539 25 539 export declare function h type constructor prop rawprop p extend p null never child rawchildren rawslot vnode the last overload be declare here find 2 error what be expect that prop with default value be infer as optional for custom render function use h what be actually happen prop be be infer as require this be for a component library that exclusively utilize render function |
vuejscore | ts4082 default export of the module have or be use private name methodoption | Bug | version 3 0 0 beta 15 reproduction link step to reproduce idem as issue 1370 but for non export methodoption rollup build be report error plugin rpt2 error cinput vue vue type script lang ts 44 1 semantic error ts4082 default export of the module have or be use private name methodoption what be expect something like the follow work without error import definecomponent from vue import string from vue type import as allformmixin from form mixin const mixin object value allformmixin export default definecomponent name helloworld prop msg string mixin what be actually happen semantic error ts4082 default export of the module have or be use private name methodoption mixin be to provide a bunch of share compute method from form mixin ts this a previously js project convert in ts project with temporary ts nocheck in the script part methodoption be not export and apparently the compiler be against export a private variable |
vuejscore | attrs be not trigger render update when inside slot | Bug | version 3 0 0 beta 14 reproduction link step to reproduce render attrs inside a wrapper component with default slot it do not seem to be collect as a reactive dependency what be expect attrs should be reactive like any other reactive object see here what be actually happen it do not update trigger a re render of the slot comment maybe this be expect because I think in vue3 attrs be not actually a reactive object but just a proxy thus this be why it be not trigger update however come from vue 2 where this be a reactive object it be confusing that it be not anymore and be probably go to break some component I wonder then if there be an official recommendation when deal with this kind of use case |
vuejscore | transition group appear class not disappear | Bug | version 3 0 0 beta 14 reproduction link step to reproduce npm I npm run dev start dev server and navigate to localhost 8080 what be expect div class list div class list item vue next 0 div div class list item vue next 1 div div class list item vue next 2 div div class list item vue next 3 div div class list item vue next 4 div div what be actually happen div class list div class list item vue next 0 div div class list item appear active appear to vue next 1 div div class list item appear active appear to vue next 2 div div class list item appear active appear to vue next 3 div div class list item appear active appear to vue next 4 div div use transition group component after page render appear to class and appear active class not disappear except for the first one |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.