owner stringclasses 14
values | repo stringclasses 14
values | id int64 116k 4.61B | issue_number int32 1 181k | author stringlengths 1 39 | body stringlengths 1 262k | created_at timestamp[us]date 2000-06-06 02:40:44 2026-06-02 20:16:18 | updated_at timestamp[us]date 2000-06-06 02:40:44 2026-06-02 20:22:56 | reactions unknown | author_association stringclasses 5
values |
|---|---|---|---|---|---|---|---|---|---|
vuejs | core | 699,036,099 | 2,237 | unbyte | string concatenation? 😂 | 2020-09-25T16:48:49 | 2020-09-25T16:48:49 | {} | CONTRIBUTOR |
vuejs | core | 699,540,358 | 2,246 | jmurth1234 | @leopiccionia I'm not trying to apply styles to a slot though, just the element that contains the slotted item?
Or am I misunderstanding? | 2020-09-26T19:50:30 | 2020-09-26T19:50:30 | {} | NONE |
vuejs | core | 699,547,649 | 2,246 | leopiccionia | Finally ran your repro.
The selectors are indeed not compiling correctly -- so `::v-slotted(.button)` actually makes the button crimson, but perhaps shouldn't.
It may be related to using a render function. Converting it to a non-functional component with a `render` method doesn't solve it.
Converting the template to... | 2020-09-26T21:04:07 | 2020-09-26T21:06:05 | {} | CONTRIBUTOR |
vuejs | core | 699,572,636 | 2,227 | waantony | > There is no such syntax, you have to use the function one. Why were you expecting this syntax to work?
The object syntax for events was supported in `vue@2.x`, why it was removed in `vue@3.x` ? Just wanna know the reason... | 2020-09-27T01:59:08 | 2020-09-27T01:59:08 | {} | NONE |
vuejs | core | 700,342,281 | 2,260 | thecrypticace | This is because JS can't track accesses to arbitrary variables, only properties on an object. If you make `firstTime` a ref it'll work just fine:
```js
let firstTime = Vue.ref(true);
const message = Vue.computed(() => {
if (firstTime.value) {
firstTime.value = false;
retu... | 2020-09-28T23:52:19 | 2020-09-28T23:52:19 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 697,361,740 | 2,201 | Subwaytime | Okay, so i removed `defineAsyncComponent` the last error message disappears but the first error with the single root node still persists even tho all components have only one root node.
Before #2099 the `router-view` behavior was fine with suspense, but thanks for opening #2215. Is this case also related to the chil... | 2020-09-23T13:24:20 | 2020-09-23T13:34:18 | {} | NONE |
vuejs | core | 698,756,042 | 2,228 | dsonet | Why? | 2020-09-25T06:50:31 | 2020-09-25T06:50:31 | {} | CONTRIBUTOR |
vuejs | core | 698,854,310 | 2,232 | hidoos | > Make `userList` reactive:
>
>
>
> ```js
>
> userList: reactive([
>
> { id: 1, name: "name1", isAudit: false },
>
> { id: 2, name: "name2", isAudit: true },
>
> { id: 3, name: "name3", isAudit: true },
>
> ])
>
> ```
Thank you. I got it wrong | 2020-09-25T10:30:08 | 2020-09-25T10:30:08 | {} | NONE |
vuejs | core | 698,887,197 | 2,233 | Shouhua | here is my code(https://codesandbox.io/s/youthful-gauss-h452m?file=/src/components/Greet.vue), use "proxy" can work, "ctx" is internal property of "ComponentInternalInstance".
In addition, pay attention to local variable name conflicts, local variables have higher priority, uncomment local variable will print local v... | 2020-09-25T11:55:04 | 2020-09-25T11:55:04 | {
"+1": 9
} | NONE |
vuejs | core | 699,604,672 | 2,247 | underfin | Thanks for all review :) | 2020-09-27T08:34:18 | 2020-09-27T08:34:18 | {} | MEMBER |
vuejs | core | 700,149,365 | 2,256 | yyx990803 | `marquee` is obsolete and no longer considered a native element. | 2020-09-28T16:40:03 | 2020-09-28T16:40:03 | {} | MEMBER |
vuejs | core | 700,388,487 | 2,253 | codevvvv9 | good | 2020-09-29T02:29:30 | 2020-09-29T02:29:30 | {} | NONE |
vuejs | core | 700,476,292 | 2,260 | edison1105 | > Okay, but shouldn't `name` be tracked regardless of the `if` statement? The following obviously also works. It stops working after we add an `if` statement:
>
> ```
> const message = Vue.computed(() => {
> return `Hello ${name.value}`;
> });
> ```
Vue3 collect field's dependency when it's `getter()` is ca... | 2020-09-29T06:21:24 | 2020-09-29T06:23:03 | {} | MEMBER |
vuejs | core | 697,493,997 | 2,216 | posva | Do
```js
setup(){
return ()=> withDirectives(h('div', {style:"width: 100px;height: 100px;background: red"}),[[vShow,false]])
},
``` | 2020-09-23T14:57:51 | 2020-09-23T14:57:51 | {} | MEMBER |
vuejs | core | 698,153,592 | 2,210 | Zcating | How? Would you please show me the code? | 2020-09-24T06:54:53 | 2020-09-24T06:54:53 | {} | CONTRIBUTOR |
vuejs | core | 698,119,089 | 2,221 | HcySunYang | The `compiler` in production mode:
| 2020-09-24T05:22:27 | 2020-09-24T08:21:43 | {} | MEMBER |
vuejs | core | 698,763,641 | 2,227 | posva | There is no such syntax, you have to use the function one. Why were you expecting this syntax to work? | 2020-09-25T07:10:20 | 2020-09-25T07:10:20 | {} | MEMBER |
vuejs | core | 698,861,812 | 2,234 | jacekkarczmarczyk | https://codepen.io/jkarczm/pen/qBZvBVO
priority of v-if and v-for has changed in Vue 3 | 2020-09-25T10:48:53 | 2020-09-25T10:48:53 | {} | CONTRIBUTOR |
vuejs | core | 699,488,695 | 2,244 | posva | I tried the example on the readme and it doesn't throw an error. Please don't open issues without a reproduction | 2020-09-26T12:23:13 | 2020-09-26T12:23:13 | {} | MEMBER |
vuejs | core | 700,435,369 | 2,253 | FrankFang | I dont do this. But someone may do this. It should be consistent.
Ok, I see. | 2020-09-29T05:28:27 | 2020-09-29T05:28:37 | {
"-1": 1
} | NONE |
vuejs | core | 698,833,749 | 2,231 | posva | I think this is intended as it allows to trigger a watcher whenever a computed is reevaluated. You can still only pay attention to the value by doing:
```js
watch(() => isOdd.value, (prev, next) => console.log(prev, next));
``` | 2020-09-25T09:43:34 | 2020-09-25T09:43:34 | {
"+1": 1
} | MEMBER |
vuejs | core | 698,997,778 | 2,237 | posva | Please answer the question there instead of opening duplicates. It will be reopened if the syntax was meant to work | 2020-09-25T15:33:24 | 2020-09-25T15:33:24 | {} | MEMBER |
vuejs | core | 699,043,212 | 2,237 | eliot-ye | > string concatenation? 😂
I see. I used the following method. Thank you
```js
h("button", { [props.once ? "onClickOnce" : "onClick"]: () => b.value++ }, `object: ${b.value}`)
``` | 2020-09-25T17:02:52 | 2020-09-25T17:02:52 | {} | NONE |
vuejs | core | 699,480,109 | 2,221 | chenhaihong | > Just ask, why not keep html comments in `<pre>` ?
The both ones below work with the same as each other in a pure html doc.
So i think that it may remove the html comments in a production mode.
```
# code a
<pre>
<!-- <code class="javascript" v-hljs>const a = 100;</code> -->
<code class="javascr... | 2020-09-26T11:02:41 | 2020-09-26T11:02:41 | {} | NONE |
vuejs | core | 699,491,911 | 2,231 | Jorge-Luis-Rangel-Peralta | It makes more sense to me that the watch is triggeret only two times, one with (true, true) and (true, false). Why is it implemented this way?. In other words, watch does not perform any comparation in the values? | 2020-09-26T12:53:57 | 2020-09-26T12:54:25 | {
"+1": 3
} | NONE |
vuejs | core | 700,000,588 | 629 | seanlandsman | @milewski did you find an alternative to `Vue.extend` ?
| 2020-09-28T13:17:40 | 2020-09-28T13:17:40 | {} | NONE |
vuejs | core | 700,127,266 | 2,251 | posva | @fotijr I meant CSS, sorry, like postcss or any other plugin. Vue doesn't parse the CSS after all. It could still come from Vue or Vite, but in that case, a boiled down reproduction should be provided | 2020-09-28T16:00:21 | 2020-09-28T16:02:41 | {
"+1": 1
} | MEMBER |
vuejs | core | 697,503,993 | 2,210 | CyberAP | You can inject via install options. | 2020-09-23T15:04:09 | 2020-09-23T15:04:09 | {} | CONTRIBUTOR |
vuejs | core | 698,420,441 | 2,143 | surmon-china | > Similar to `<transition>`, the new Suspense now must be used with `<router-view>` via its [slot-based syntax](https://next.router.vuejs.org/api/#router-view-s-v-slot) because it now must have direct access to the toggled root node:
>
> ```
> <router-view v-slot="{ Component }">
> <suspense>
> <component :... | 2020-09-24T15:32:13 | 2020-09-24T15:32:13 | {
"confused": 14
} | NONE |
vuejs | core | 699,000,393 | 2,232 | posva | Or a ref, that would also work | 2020-09-25T15:38:21 | 2020-09-25T15:38:21 | {} | MEMBER |
vuejs | core | 699,162,530 | 2,205 | dependabot-preview[bot] | Superseded by #2240. | 2020-09-25T21:24:54 | 2020-09-25T21:24:54 | {} | CONTRIBUTOR |
vuejs | core | 699,425,070 | 2,226 | HcySunYang | See https://github.com/vuejs/vue-next/issues/1866#issuecomment-674881439 | 2020-09-26T05:20:14 | 2020-09-26T05:20:14 | {} | MEMBER |
vuejs | core | 698,173,056 | 2,220 | boussadjra | Thank you for interacting with my issue, originally i had the issue in the following example :
main.ts
```
import { createApp } from 'vue'
import App from './App.vue'
import router from './router'
import store from './store'
import './styles/app.scss'
import mitt from 'mitt';
const emitter = mitt();
le... | 2020-09-24T07:37:58 | 2020-09-24T07:37:58 | {} | NONE |
vuejs | core | 698,239,263 | 1,927 | Fiv5 | > @Fiv5 can you opeen a PR or an issue at vuejs/docs-next repository to track it?
Sure, my pleasure! | 2020-09-24T09:46:57 | 2020-09-24T09:46:57 | {} | NONE |
vuejs | core | 699,116,436 | 2,233 | posva | Hi, thanks for your interest but Github issues are for bug reports and feature requests only. You can ask questions on the [forum](http://forum.vuejs.org/), the [Discord server](https://vue-land.js.org/) or [StackOverflow](http://stackoverflow.com/tags/vue.js).
---
The global properties are meant to be used by th... | 2020-09-25T19:35:48 | 2020-09-25T19:35:48 | {} | MEMBER |
vuejs | core | 699,455,892 | 2,215 | HcySunYang | I tracked down this issue. When a component with `asyncDep` is toggled, the component will be re-mount, which means `registerDep` will be called. But `suspense` has been resolved, and `pendingBranch` is `null`, nothing will happen according to the [current implementation](https://github.com/vuejs/vue-next/blob/master/p... | 2020-09-26T08:10:27 | 2020-09-26T08:10:27 | {
"heart": 4
} | MEMBER |
vuejs | core | 699,933,252 | 2,253 | posva | You cannot have a prop and a data property (or any other property that is directly available through `this` or on the template, with the same name. There is already a warning on the console about duplicated names | 2020-09-28T10:53:21 | 2020-09-28T10:53:21 | {
"+1": 1
} | MEMBER |
vuejs | core | 699,967,285 | 2,255 | xuliangzhan | Thanks, ```marquee ``` tag is obsolete, I will use CSS3 instead | 2020-09-28T12:10:31 | 2020-09-28T12:10:31 | {} | NONE |
vuejs | core | 700,319,066 | 629 | backbone87 | https://github.com/vuejs/rfcs/blob/master/active-rfcs/0009-global-api-change.md#global-api-mapping
should work:
```ts
export default defineComponent({ extends: defineComponent({ ... }) });
``` | 2020-09-28T22:34:43 | 2020-09-28T22:34:43 | {
"+1": 2
} | NONE |
vuejs | core | 921,782,092 | 1,558 | zangtian2 | > Nice catch, sorry for the false report and thanks for taking a look @underfin !
hi， brother, how to fix it ? | 2021-09-17T13:06:54 | 2021-09-17T13:06:54 | {} | NONE |
vuejs | core | 921,822,256 | 4,417 | yyx990803 | Vue only prefixes property **names**. `fit-content` is a property value. Unfortunately I don't think there is a way to automatically detect values that need prefixing at runtimes. | 2021-09-17T14:02:53 | 2021-09-17T14:02:53 | {} | MEMBER |
vuejs | core | 921,828,367 | 4,417 | yyx990803 | Btw re @jods4 's comment - static string style bindings are in fact pre-compiled into constant objects so they work the same with object bindings. | 2021-09-17T14:10:26 | 2021-09-17T14:10:26 | {} | MEMBER |
vuejs | core | 921,870,926 | 4,620 | yyx990803 | Ah ok, you are nesting one custom element in another.
Since custom elements are registered globally and not under a normal Vue app, configuring an app instance has no effects on them. You need to pass the `compilerOptions` inline:
```js
customElements.define(
'test-case',
Vue.defineCustomElement({
compi... | 2021-09-17T15:05:54 | 2021-09-17T15:05:54 | {
"+1": 1
} | MEMBER |
vuejs | core | 922,238,412 | 4,627 | Rudeus3Greyrat | Directive created hook is invoked before prop is patched on el, try other hooks instead. | 2021-09-18T08:12:09 | 2021-09-18T08:12:09 | {} | CONTRIBUTOR |
vuejs | core | 923,001,539 | 4,633 | LinusBorg | > Why is there no autocomplete attribute on vue? It's **standard html** [...]
From the MDN page you linked to:
> This attribute on a `<button>` is **nonstandard** and Firefox-specific.
Also I'd like to verify: you have an issue with this attribute being missing from the types here?
https://github.com/vuejs... | 2021-09-20T14:53:12 | 2021-09-20T14:53:40 | {} | MEMBER |
vuejs | core | 924,152,707 | 4,642 | yyx990803 | @dependabot ignore this dependency | 2021-09-21T16:28:37 | 2021-09-21T16:28:37 | {} | MEMBER |
vuejs | core | 924,154,297 | 4,562 | yyx990803 | This is unnecessary. TS infers the type based on default value. | 2021-09-21T16:30:30 | 2021-09-21T16:30:30 | {} | MEMBER |
vuejs | core | 925,041,147 | 4,654 | dsine-de | I got the same problem with the latest version. | 2021-09-22T15:30:35 | 2021-09-22T15:30:35 | {
"+1": 1
} | NONE |
vuejs | core | 921,554,389 | 4,617 | vue-bot | Hello, thank you for taking time filling this issue!
However, we kindly ask you to use our [Issue Helper](https://new-issue.vuejs.org/?repo=vuejs/vue-next) 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 automatic... | 2021-09-17T07:09:52 | 2021-09-17T07:09:52 | {} | CONTRIBUTOR |
vuejs | core | 922,497,705 | 4,619 | unbyte | Some thoughts:
1. implicit checking function.length can lead to bugs that are difficult to troubleshoot (for plugin authors).
2. Murphy's law. 🤯
3. at present, the general practice of registering unmount hooks is to replace the original `app.mount` function; I think `app.onUnmount` is better, since it's more in lin... | 2021-09-19T16:08:12 | 2021-09-19T16:08:12 | {} | CONTRIBUTOR |
vuejs | core | 922,549,639 | 2,860 | bjkippax | > This is now fixed by [vitejs/vite@316d7af](https://github.com/vitejs/vite/commit/316d7afc0c84e51359938a12ebe1b09ca34ea8bd) + [cb2d7c0](https://github.com/vuejs/vue-next/commit/cb2d7c0e3c2ccbfd92eb7d19e2cfddad30bcaf62)
>
> Will need `@vitejs/plugin-vue` >= 1.8.1.
>
> `vue-loader@next` will get similar fix soon.
... | 2021-09-19T22:52:35 | 2021-09-19T22:52:35 | {} | NONE |
vuejs | core | 923,045,788 | 4,634 | yyx990803 | You are saying it's aways an object but initializing it with an `undefined` value, that's just wrong code. | 2021-09-20T15:41:33 | 2021-09-20T15:41:33 | {} | MEMBER |
vuejs | core | 924,152,733 | 4,642 | dependabot[bot] | OK, I won't notify you about tmpl again, unless you re-open this PR or update it yourself. 😢 | 2021-09-21T16:28:39 | 2021-09-21T16:28:39 | {} | CONTRIBUTOR |
vuejs | core | 924,587,762 | 4,644 | henribru | The RFC specifies _setup scope_. My variables are defined in a regular script block so they're in module scope.
(And as mentioned it used to work fine) | 2021-09-22T05:06:53 | 2021-09-22T06:18:02 | {} | NONE |
vuejs | core | 924,661,685 | 4,616 | heng1025 | 
Still have the same problem | 2021-09-22T07:29:32 | 2021-09-22T07:29:32 | {} | NONE |
vuejs | core | 924,744,819 | 4,616 | ygj6 | ```ts
import type { ComponentPublicInstance } from 'vue'
function setItemRef(ref: Element | ComponentPublicInstance ) {
if(ref) {
liRefs.push(ref)
}
}
``` | 2021-09-22T09:22:36 | 2021-09-22T09:22:36 | {} | MEMBER |
vuejs | core | 924,826,190 | 4,651 | posva | Do you have a reproduction? This doesn't look like the right fix | 2021-09-22T11:06:40 | 2021-09-22T11:06:40 | {} | MEMBER |
vuejs | core | 925,373,214 | 4,654 | yyx990803 | Should be fixed in `vue-loader@16.8.1`. | 2021-09-22T22:25:07 | 2021-09-22T22:25:07 | {
"+1": 6
} | MEMBER |
vuejs | core | 921,453,638 | 4,605 | edison1105 | @WJCHumble Good catch.
I will check it later. | 2021-09-17T04:29:20 | 2021-09-17T04:29:20 | {} | MEMBER |
vuejs | core | 923,892,649 | 4,511 | gnuletik | Your issue seems to address two issues :
- app context
- global components
For app context, you can use `provide` in a root web component and use `inject` inside your child components.
However, if you use intermediate Vue components (which are not rendered as Custom Elements), the `inject` API would fail becaus... | 2021-09-21T11:31:08 | 2021-09-21T11:31:08 | {} | NONE |
vuejs | core | 923,897,614 | 4,404 | gnuletik | There is a current limitation when not using Shadow DOM : using slot inside web components is not working :
```html
<my-comp>
<div>Some content</div>
</my-comp>
```
The `div` is rendered after the element instead of replacing `my-comp`-defined slot.
This is because [slot elements are not natively supported wi... | 2021-09-21T11:38:09 | 2021-09-21T11:38:09 | {} | NONE |
vuejs | core | 924,645,731 | 4,646 | zhangenming | 
This will only be run once but I don't know if it's necessary | 2021-09-22T07:04:36 | 2021-09-22T07:04:36 | {} | CONTRIBUTOR |
vuejs | core | 924,651,640 | 4,638 | catsmeatman | Did i understand correctly? Read this doc https://v3.vuejs.org/guide/web-components.html#passing-dom-properties, that in case i must use
`<test-case :test-value.prop="true"></test-case>` or `<test-case .test-value="true"></test-case>`
| 2021-09-22T07:13:20 | 2021-09-22T07:13:20 | {} | NONE |
vuejs | core | 925,330,431 | 4,654 | yyx990803 | This is a regression caused by `vue-loader@16.6+`. For now, please pin vue-loader to 16.5.x (e.g. using Yarn's resolution field) | 2021-09-22T21:06:53 | 2021-09-22T21:06:53 | {} | MEMBER |
vuejs | core | 921,808,359 | 4,476 | yyx990803 | To clarify, what is the case that is currently **not** working? Can you provide a code sample demonstrating a simplified case of what you intend to do? | 2021-09-17T13:43:49 | 2021-09-17T13:43:49 | {} | MEMBER |
vuejs | core | 924,369,831 | 4,527 | amw | I have ran same the same problem and can confirm that using `ref<HTMLElement>()` or `ref<HTMLElement | undefined>()` does not help.
@posva Please re-open this issue. | 2021-09-21T20:44:46 | 2021-09-21T20:44:46 | {} | NONE |
vuejs | core | 924,944,244 | 4,651 | zhangenming | 
```
const react = reactive({})
effect(() => {
react.a
})
react.b = 2
``` | 2021-09-22T13:43:26 | 2021-09-22T13:43:26 | {} | CONTRIBUTOR |
vuejs | core | 923,750,351 | 4,497 | StarHosea | @posva can you see that ? Please | 2021-09-21T08:19:56 | 2021-09-21T08:19:56 | {} | NONE |
vuejs | core | 923,902,743 | 1,359 | Shinigami92 | https://twitter.com/youyuxi/status/1439304854028029953 | 2021-09-21T11:45:35 | 2021-09-21T11:45:35 | {
"hooray": 2
} | CONTRIBUTOR |
vuejs | core | 924,164,106 | 4,641 | yyx990803 | Yeah, it's probably better to move it to `reactive.ts` | 2021-09-21T16:42:24 | 2021-09-21T16:42:24 | {} | MEMBER |
vuejs | core | 924,218,140 | 4,619 | LinusBorg | I agree with your comments and will adjust the PR accordingly | 2021-09-21T17:48:17 | 2021-09-21T17:48:17 | {} | MEMBER |
vuejs | core | 924,380,087 | 4,646 | sqal | see https://github.com/vuejs/vue-next/issues/4084 | 2021-09-21T21:01:04 | 2021-09-21T21:01:04 | {} | CONTRIBUTOR |
vuejs | core | 924,771,462 | 4,616 | heng1025 | > ```ts
> import type { ComponentPublicInstance } from 'vue'
> function setItemRef(ref: Element | ComponentPublicInstance ) {
> if(ref) {
> liRefs.push(ref)
> }
> }
> ```
Yes, i know that ,just i think it's too verbose. | 2021-09-22T09:56:15 | 2021-09-22T09:56:54 | {} | NONE |
vuejs | core | 924,822,151 | 4,646 | cyfung1031 | If the programmers do not know :ref="someFunc" is called for any change including the value of `ref`, it would be a disaster of the whole application.
[Recursive Calling due to this issue](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHRlbXBsYXRlPiBcbiAgPGRpdiBpZD1cImNvbnRhaW5lclwiPlxuICAgIDxkaXYgaWQ9XCJjb25zb2xlXCI+PC9ka... | 2021-09-22T11:00:34 | 2021-09-22T11:00:34 | {} | NONE |
vuejs | core | 921,629,313 | 4,618 | LinusBorg | $slots isn't reactive either and never has been. This would also not work and never worked in Vue 2 as well:
```vue
<script>
export default {
computed: {
hasFooter() {
return !!this.$slots.footer
}
}
}
</script>
<template>
<div>
<div>
<slot />
</div>
<div>
... | 2021-09-17T08:58:14 | 2021-09-17T08:58:54 | {
"+1": 1
} | MEMBER |
vuejs | core | 921,654,280 | 3,173 | LinusBorg | The issue is that `normalizeClass` will always coerce the `:class` value to a string.
https://github.com/vuejs/vue-next/blob/cac6ab5bdb712a3872dfa2b1cd4751d80cb4f38c/packages/shared/src/normalizeProp.ts#L65-L66
and `patchClass` will only remove the attribute when it's nullish:
https://github.com/vuejs/vue-next... | 2021-09-17T09:33:55 | 2021-09-17T09:33:55 | {} | MEMBER |
vuejs | core | 921,809,140 | 1,558 | pearofducks | @zangtian2 - here's a working version - https://jsfiddle.net/j9vp0uy3/
As Underfin mentioned, I was missing the component registration - e.g. `components: { TransitionWrapper }` | 2021-09-17T13:45:00 | 2021-09-17T13:45:00 | {} | NONE |
vuejs | core | 922,353,453 | 4,624 | OneSeven | > see [sfc](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHNjcmlwdCBzZXR1cD5cbmltcG9ydCB7IHJlZiB9IGZyb20gJ3Z1ZSdcblxuY29uc3QgaGVpZ2h0ID0gcmVmKDEwMClcbjwvc2NyaXB0PlxuXG48dGVtcGxhdGU+XG4gIDxoMSBjbGFzcz1cImNvbnRlbnRcIj57eyBoZWlnaHQgfX08L2gxPlxuPC90ZW1wbGF0ZT5cblxuPHN0eWxlPlxuLmNvbnRlbnR7XG4gIGhlaWdodDogdi1iaW5kKGAke2hlaWdodH1we... | 2021-09-18T18:37:59 | 2021-09-18T18:37:59 | {} | NONE |
vuejs | core | 922,538,336 | 4,630 | LinusBorg | In Vite, JSX support for Vue is provided with a separate plugin:
https://vitejs.dev/plugins/#vitejs-plugin-vue-jsx
the normal "react-ish" JSX output is not working on its own. | 2021-09-19T21:17:30 | 2021-09-19T21:17:38 | {} | MEMBER |
vuejs | core | 923,741,319 | 4,633 | Pentadome | Does the bug described on the MDN page affect Javascript frameworks? | 2021-09-21T08:08:19 | 2021-09-21T08:08:19 | {} | CONTRIBUTOR |
vuejs | core | 923,822,927 | 1,359 | chojnicki | > I just read that Evan has recently enabled TS in templates, so 🎉
@jods4 where did you read this? I'm really waiting for TS in templates... | 2021-09-21T09:57:48 | 2021-09-21T09:57:48 | {
"laugh": 1
} | NONE |
vuejs | core | 925,314,805 | 4,655 | yyx990803 | I know. Turns out the TS transpiler used in SFC playground (sucrase) is able to parse invalid TS syntax generated by the compiler... but `esbuild` will throw an error in this case. | 2021-09-22T20:42:33 | 2021-09-22T20:42:33 | {} | MEMBER |
vuejs | core | 921,432,171 | 4,614 | yyx990803 | `^` is **not** a documented shorthand.
The only supported shorthands for v-bind are `:` and `.`.
`^` is only supported as a **prefix** when using manual render functions because there are no modifiers when using render functions. | 2021-09-17T03:46:06 | 2021-09-17T03:46:06 | {} | MEMBER |
vuejs | core | 921,634,258 | 4,618 | pearofducks | Thanks for the explanation and workaround @LinusBorg - sorry for the bad issue report! | 2021-09-17T09:05:21 | 2021-09-17T09:05:21 | {} | NONE |
vuejs | core | 924,909,255 | 4,638 | yyx990803 | This is only possible when **using custom elements inside Vue templates**, because it's Vue's binding syntax.
You are not using the custom element inside a Vue template. You are using it inside plain HTML. | 2021-09-22T13:03:45 | 2021-09-22T13:03:45 | {} | MEMBER |
vuejs | core | 921,630,035 | 4,616 | LinusBorg | ```ts
function setItemRef(ref: Element | null) {
if(ref) {
liRefs.push(ref)
}
}
``` | 2021-09-17T08:59:26 | 2021-09-17T08:59:26 | {
"confused": 1
} | MEMBER |
vuejs | core | 922,270,821 | 4,624 | edison1105 | see [sfc](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHNjcmlwdCBzZXR1cD5cbmltcG9ydCB7IHJlZiB9IGZyb20gJ3Z1ZSdcblxuY29uc3QgaGVpZ2h0ID0gcmVmKDEwMClcbjwvc2NyaXB0PlxuXG48dGVtcGxhdGU+XG4gIDxoMSBjbGFzcz1cImNvbnRlbnRcIj57eyBoZWlnaHQgfX08L2gxPlxuPC90ZW1wbGF0ZT5cblxuPHN0eWxlPlxuLmNvbnRlbnR7XG4gIGhlaWdodDogdi1iaW5kKGAke2hlaWdodH1weGA... | 2021-09-18T12:40:17 | 2021-09-18T12:40:51 | {} | MEMBER |
vuejs | core | 922,502,897 | 4,590 | mnlipp | Well, thanks for the "thumbs up". I've pondered some time whether to add another comment. Here it is: I think the requirement for a higher typescript version *should* have been mentioned as a [breaking change](https://blog.vuejs.org/posts/vue-3.2.html).
I don't know why google didn't show [this one](https://stackove... | 2021-09-19T16:46:14 | 2021-09-19T16:46:14 | {
"+1": 3
} | NONE |
vuejs | core | 923,822,380 | 1,359 | keithbrink | @jods4 Can you like to where you read that? Curious to know more. | 2021-09-21T09:57:08 | 2021-09-21T09:57:08 | {} | NONE |
vuejs | core | 924,160,230 | 4,588 | yyx990803 | This seems unnecessary. Also excluding `script/*` is unsafe. | 2021-09-21T16:37:02 | 2021-09-21T16:37:02 | {} | MEMBER |
vuejs | core | 924,184,632 | 4,628 | yyx990803 | see 6171aecd | 2021-09-21T17:07:12 | 2021-09-21T17:07:12 | {} | MEMBER |
vuejs | core | 924,187,802 | 4,619 | yyx990803 | I also think the length check seems a bit unnecessary/incomplete.
`app.onUnmount` is safer and also more generic as it can be used even in non-plugin scenarios. | 2021-09-21T17:11:06 | 2021-09-21T17:11:06 | {} | MEMBER |
vuejs | core | 925,100,245 | 4,654 | Sun3 | Same issue here... | 2021-09-22T16:42:46 | 2021-09-22T16:42:46 | {} | NONE |
vuejs | core | 925,310,725 | 4,655 | yyx990803 | On the Volar side it seems its bundled compiler hasn't updated to incorporate d23fde3d yet. /cc @johnsoncodehk | 2021-09-22T20:36:49 | 2021-09-22T20:37:08 | {} | MEMBER |
vuejs | core | 922,238,354 | 4,626 | yanbowe | Thanks！ | 2021-09-18T08:11:46 | 2021-09-18T08:11:46 | {} | NONE |
vuejs | core | 923,115,328 | 4,564 | imadx | Closing this MR, since this might not be useful. https://github.com/vuejs/vue/pull/12275 | 2021-09-20T17:08:47 | 2021-09-20T17:08:47 | {} | NONE |
vuejs | core | 924,174,866 | 4,615 | yyx990803 | This is unnecessary. | 2021-09-21T16:56:13 | 2021-09-21T16:56:13 | {} | MEMBER |
vuejs | core | 922,212,769 | 4,626 | yanbowe | 
| 2021-09-18T06:26:48 | 2021-09-18T06:26:48 | {} | NONE |
vuejs | core | 922,280,780 | 4,628 | Justineo | [`HTMLSelectElement`](https://developer.mozilla.org/en-US/docs/Web/API/HTMLSelectElement) has a `value` property. | 2021-09-18T14:01:37 | 2021-09-18T14:01:37 | {
"+1": 2
} | MEMBER |
vuejs | core | 924,762,647 | 4,646 | LinusBorg | The issue is that the assignment of the ref is done *during rendering*, where we still collect reactive dependencies of the render/template.
In the provided example, you *read* `input.value`, which makes it a reactive dependency of the template.
Then you *change* `input.value`, which causes a re-render, as a react... | 2021-09-22T09:43:47 | 2021-09-22T09:45:10 | {
"+1": 1
} | MEMBER |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.