You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In a freshly created app created using create-vite-app I stumbled upon a weird bug that is triggered when you update the state (for example by clicking on the increase button) and then add/remove/change attributes of any native HTML element that listens to any event. This should trigger one of two possible errors:
TypeError: "el is null" if style or class attributes are changed.
TypeError: "right-hand side of 'in' should be an object, got null" if any other attributes are changed.
System Info
requiredvite version: 0.13.2
required Operating System: MacOS 10.15.4
required Node version: 12.16.1
Optional:
npm/yarn version: 6.13.4/1.22.4
Installed vue version (from yarn.lock or package-lock.json): 3.0.0-beta.10
Hello, thank you for taking time filling this issue!
However, we kindly ask you to use our Issue Helper when creating new issues, in order to ensure every issue provides the necessary information for us to investigate. This explains why your issue has been automatically closed by me (your robot friend!).
I hope to see your helper-created issue very soon!
Describe the bug
In a freshly created app created using
create-vite-app
I stumbled upon a weird bug that is triggered when you update the state (for example by clicking on theincrease
button) and then add/remove/change attributes of any native HTML element that listens to any event. This should trigger one of two possible errors:TypeError: "el is null"
ifstyle
orclass
attributes are changed.TypeError: "right-hand side of 'in' should be an object, got null"
if any other attributes are changed.System Info
vite
version: 0.13.2vue
version (fromyarn.lock
orpackage-lock.json
): 3.0.0-beta.10@vue/compiler-sfc
version: 3.0.0-beta.10Logs
Reproduction
create-vite-app
cmd and start the appincrease
buttonThe text was updated successfully, but these errors were encountered: