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 | 789,833,694 | 2,774 | dependabot-preview[bot] | OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting `@dependabot ignore this major version` or `@dependabot ignore this minor version`.
If you change your mind, just re-... | 2021-03-03T16:16:31 | 2021-03-03T16:16:31 | {} | CONTRIBUTOR |
vuejs | core | 788,645,546 | 3,291 | dependabot-preview[bot] | Superseded by #3336. | 2021-03-02T06:15:52 | 2021-03-02T06:15:52 | {} | CONTRIBUTOR |
vuejs | core | 789,834,770 | 3,195 | dependabot-preview[bot] | OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting `@dependabot ignore this major version` or `@dependabot ignore this minor version`.
If you change your mind, just re-... | 2021-03-03T16:17:58 | 2021-03-03T16:17:58 | {} | CONTRIBUTOR |
vuejs | core | 790,265,646 | 3,347 | edison1105 | a tip here:
return `false` in `shouldUpdateComponent()`
maybe `patchFlag` is incorrect.
too busy to look into deep. | 2021-03-04T03:40:36 | 2021-03-04T03:40:36 | {} | MEMBER |
vuejs | core | 790,440,613 | 1,221 | Mount-Isaac | Hey, I have a js file and within it, I've created a template where I have placed my HTML code contained in component Product. in the HTML file I have imported the js file directory and likewise configured the product component in the App div. when I reload my page, I don't get my page but by logging in to console, the ... | 2021-03-04T08:46:06 | 2021-03-04T08:46:06 | {} | NONE |
vuejs | core | 790,543,299 | 3,348 | 07akioni | I've thought of another scene in which vNode props can be modified without template props specified.
eg. We have a popover component. It's api looks like:
```html
<popover trigger="hover">
<template #trigger>
<button>show</button>
</template>
Popover content
</popover>
```
It is a common api pattern.
E... | 2021-03-04T11:24:06 | 2021-03-04T11:24:06 | {} | CONTRIBUTOR |
vuejs | core | 787,591,615 | 3,326 | tjk | Hm, sort of wish I could call `genNode(props)` and just see if it returns empty... (it wouldn't make sense to delay the defaulting to `_` into codegen internals I imagine)
Ooh, there is `stringifyExpression` but not exported. | 2021-03-01T02:27:52 | 2021-03-01T02:32:24 | {} | CONTRIBUTOR |
vuejs | core | 789,201,581 | 2,892 | yyx990803 | Update: the root cause of this is flawed implementation of `:slotted` scoped id logic. Currently, the following fails:
```html
<Comp>
<slot/>
</Comp>
<style scoped>
:slotted(*) { color: red }
</style>
```
#3150 only special cases internal components like Transition, but the ideal behavior is for `:slot... | 2021-03-02T20:41:51 | 2021-03-02T20:42:33 | {} | MEMBER |
vuejs | core | 789,358,834 | 3,334 | HcySunYang | > mergeProps already performs class and style normalization so normalizeProps here seems unnecessary.
Alright, didn't notice it | 2021-03-03T01:39:42 | 2021-03-03T01:39:42 | {} | MEMBER |
vuejs | core | 789,500,887 | 3,338 | shameleo | I not sure which policy you are talking about. Vue already has dual handling of similar cases. From docs:
> When used on components, custom directive will always apply to component's root node, similarly to non-prop attributes.
> Unlike attributes, directives can't be passed to a different element with v-bind="$att... | 2021-03-03T07:23:52 | 2021-03-03T07:23:52 | {} | NONE |
vuejs | core | 789,833,801 | 2,858 | dependabot-preview[bot] | OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting `@dependabot ignore this major version` or `@dependabot ignore this minor version`.
If you change your mind, just re-... | 2021-03-03T16:16:40 | 2021-03-03T16:16:40 | {} | CONTRIBUTOR |
vuejs | core | 789,842,566 | 3,284 | dependabot-preview[bot] | OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting `@dependabot ignore this major version` or `@dependabot ignore this minor version`.
If you change your mind, just re-... | 2021-03-03T16:25:33 | 2021-03-03T16:25:33 | {} | CONTRIBUTOR |
vuejs | core | 790,325,843 | 3,356 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.74 KB (0%) |
| runtime-dom.global.prod.js | 27.08 KB (0%) |
| size-check.global.prod.js | 16.4 KB (0%) | | 2021-03-04T06:14:10 | 2021-03-04T06:14:10 | {} | NONE |
vuejs | core | 787,616,977 | 3,323 | tjk | @HcySunYang thanks for that pointer... much better place for it! Let me know if anything else should be touched up. | 2021-03-01T03:52:36 | 2021-03-01T03:52:36 | {} | CONTRIBUTOR |
vuejs | core | 787,897,168 | 3,332 | Fuzzyma | @LinusBorg Sure thing. Do you know any website where I can execute node scripts as esm modules? I couldn't find any. I tried to make it as reproducible as possible. I just don't know any way to give you a link. Sure - I can create a github repo with 2 files. If that helps? | 2021-03-01T12:03:59 | 2021-03-01T12:03:59 | {} | NONE |
vuejs | core | 788,778,240 | 3,338 | posva | You need one element at the root of your container for the transition to apply the classes: https://jsfiddle.net/1ax56d9p/
Maybe we should change the wording in the warning:
```
Component inside <Transition> renders non-element root node that cannot be animated.
``` | 2021-03-02T09:52:27 | 2021-03-02T09:52:27 | {} | MEMBER |
vuejs | core | 789,736,617 | 3,348 | edison1105 | should full diff props in `updateProps` when patchFlag is `PatchFlags.DYNAMIC_SLOTS` ?
```javascript
export function updateProps(
instance: ComponentInternalInstance,
rawProps: Data | null,
rawPrevProps: Data | null,
optimized: boolean
) {
...
if (
// always force full diff in dev
// ... | 2021-03-03T14:03:59 | 2021-03-03T14:03:59 | {} | MEMBER |
vuejs | core | 790,324,823 | 3,354 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.74 KB (0%) |
| runtime-dom.global.prod.js | 27.08 KB (0%) |
| size-check.global.prod.js | 16.4 KB (0%) | | 2021-03-04T06:12:20 | 2021-03-04T06:12:20 | {} | NONE |
vuejs | core | 787,699,560 | 2,775 | bobohuochai | > I'm having the same problem, but with `data` instead of `props`. I don't have any validators or anything like that, and it works just fine when using javascript.
>
> ```
> <script lang="ts">
> export default {
> data() {
> return {
> platform: "x86_64"
> };
> },
> computed: {
> sho... | 2021-03-01T06:52:49 | 2021-03-01T06:52:49 | {} | NONE |
vuejs | core | 787,909,174 | 3,332 | LinusBorg | Already deleted my comment as I didn't read your description carefully enough - I still had you mentioning ts-node etc. on discord in my head.
Could reproduce the issue successfully. Pretty dumbfounded though as to what the reason could be.
We didn't really change anything about the build process, and the entry ... | 2021-03-01T12:23:48 | 2021-03-01T12:23:48 | {} | MEMBER |
vuejs | core | 788,650,051 | 3,304 | mika76 | @CarterLi watch #3308 - but in the meantime put the `keyframes` definitions in their own non-scoped `<style>` tag. Should solve your issue for the moment. | 2021-03-02T06:25:38 | 2021-03-02T06:27:04 | {} | NONE |
vuejs | core | 790,138,725 | 2,948 | ChronicLynx | I was able to test this fix out, and it seems to work perfectly! Please merge this! | 2021-03-03T23:08:58 | 2021-03-03T23:08:58 | {} | NONE |
vuejs | core | 787,402,173 | 3,323 | tjk | @HcySunYang thanks for the feedback, that actually makes sense! I'll do another pass. Do you have a suggestion for improving the test?
PS: Edited the patch (much better!) | 2021-02-28T06:06:47 | 2021-02-28T06:17:02 | {} | CONTRIBUTOR |
vuejs | core | 787,465,964 | 3,325 | LinusBorg | > It should render the valid vnodes after **having rendered an invalid vnode**.
Not sure how to interpret that.
What do you expect Vue to render/do when it receives a "functional component" that really isn't one? just render nothing, and essentially silently fail? Throw a warning? an error?
I think we can imp... | 2021-02-28T15:00:54 | 2021-02-28T15:00:54 | {
"+1": 1
} | MEMBER |
vuejs | core | 741,561,425 | 2,774 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.65 KB (0%) |
| runtime-dom.global.prod.js | 26.98 KB (0%) |
| size-check.global.prod.js | 16.34 KB (0%) | | 2020-12-09T06:26:06 | 2021-03-01T16:04:28 | {} | NONE |
vuejs | core | 789,218,060 | 2,343 | bjankord | Stencil has released a new output target `dist-custom-elements` in version 2.4.0 that allows loading of the custom element without stencil lazy loading them. I've found that by using these imports with the `.prop` modifier in Vue that it appears to work with Vue 3 in regards to passing objects or arrays. | 2021-03-02T21:10:41 | 2021-03-02T21:10:41 | {
"+1": 1
} | NONE |
vuejs | core | 790,296,167 | 3,352 | HcySunYang | I cannot point out the problem you encountered unless you provide a minimal and runnable reproduction. But it seems that you have encountered a multi-instance problem, you can check out these two:
https://github.com/vuejs/vue-next/issues/1870
https://github.com/vuejs/vue-next/issues/2108 | 2021-03-04T05:09:43 | 2021-03-04T05:09:43 | {} | MEMBER |
vuejs | core | 790,552,436 | 3,348 | HcySunYang | I can get your point, I'm discussing how to solve this kind of needs. I have a two ideas, just hint here:
1. Proxy the `vnode.props`
Intercept the user's operations on `vnode.props`, so that we can correctly adjust the corresponding `patchFlags` and `dynamicProps`. But this brings extra `VNode creation` and runti... | 2021-03-04T11:40:20 | 2021-03-04T11:40:20 | {} | MEMBER |
vuejs | core | 788,027,348 | 3,332 | yyx990803 | I looked into this and it is caused by output change due to bumping Rollup to 2.39.0, which then breaks re-exports static analysis in Node.js, where the static analysis is done by `cjs-module-lexer`.
I've created an issue in `cjs-module-lexer`: https://github.com/guybedford/cjs-module-lexer/issues/38
For now we h... | 2021-03-01T15:17:12 | 2021-03-01T15:17:12 | {} | MEMBER |
vuejs | core | 784,816,223 | 3,291 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.65 KB (0%) |
| runtime-dom.global.prod.js | 26.98 KB (0%) |
| size-check.global.prod.js | 16.34 KB (0%) | | 2021-02-24T06:13:57 | 2021-03-01T16:04:22 | {} | NONE |
vuejs | core | 788,133,738 | 3,332 | yyx990803 | Note: we should probably introduce a dedicated Node ESM build and `exports` field at some point to unblock future Rollup upgrades, however introducing `exports` can be a risky thing so we need to do it carefully. | 2021-03-01T17:35:49 | 2021-03-01T17:36:01 | {
"+1": 2
} | MEMBER |
vuejs | core | 788,668,086 | 3,317 | Mister-Hope |
Full code logic here, `useA` is a composable.
```vue
<script lang="ts">
import { DeepReadonly, defineComponent, readonly, Ref, ref } from "vue";
interface AResult {
a: DeepReadonly<Ref<number>... | 2021-03-02T06:59:53 | 2021-03-02T06:59:53 | {} | NONE |
vuejs | core | 788,754,986 | 992 | zyxm5 | > > The target element cannot be a part of the same component... It needs to be outside of `<div id="app">`.
>
> It is not work
I put the endofbody element before the app,it worked. I guess it is because the endofbody element has not rendered when resolve teleport element
![Snipaste_2021-03-02_17-16-55](https://us... | 2021-03-02T09:17:31 | 2021-03-02T09:17:31 | {} | NONE |
vuejs | core | 788,773,083 | 3,337 | posva | This is intended because `<component someProp="" />` is the same as just `<component someProp />` and the order of the array matters. This is also consistent with Vue 2 | 2021-03-02T09:44:05 | 2021-03-02T09:44:05 | {} | MEMBER |
vuejs | core | 789,422,807 | 3,344 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.68 KB (0%) |
| runtime-dom.global.prod.js | 27.01 KB (0%) |
| size-check.global.prod.js | 16.37 KB (0%) | | 2021-03-03T04:39:40 | 2021-03-03T04:39:40 | {} | NONE |
vuejs | core | 789,479,202 | 3,327 | HcySunYang | @LinusBorg What do you think about this. | 2021-03-03T06:42:53 | 2021-03-03T06:42:53 | {} | MEMBER |
vuejs | core | 789,724,907 | 3,345 | flozero | I have updated the steps thanks | 2021-03-03T13:46:25 | 2021-03-03T13:46:25 | {} | NONE |
vuejs | core | 789,836,027 | 3,343 | dependabot-preview[bot] | OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting `@dependabot ignore this major version` or `@dependabot ignore this minor version`.
If you change your mind, just re-... | 2021-03-03T16:19:43 | 2021-03-03T16:19:43 | {} | CONTRIBUTOR |
vuejs | core | 789,842,829 | 3,336 | dependabot-preview[bot] | OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting `@dependabot ignore this major version` or `@dependabot ignore this minor version`.
If you change your mind, just re-... | 2021-03-03T16:25:46 | 2021-03-03T16:25:46 | {} | CONTRIBUTOR |
vuejs | core | 801,919,211 | 3,445 | zhangenming | ```js
<template>
<button @click="test">...</button>
</template>
<script setup>
ref: x = 1
function test() {
const x = { value: 2 }
console.log(x) //will show 1, should show 2
}
</script>
```
that is all
quite clearly, not necessary at all reproduction ...
scope mistake, compiler has a bug | 2021-03-18T13:18:08 | 2021-03-18T13:18:08 | {} | CONTRIBUTOR |
vuejs | core | 802,030,574 | 3,445 | LinusBorg | You are misunderstanding how `ref:` works:
```
ref: x = 1
function test() {
x = 2
console.log(x) //will show 2
}
``` | 2021-03-18T15:40:45 | 2021-03-18T15:40:57 | {} | MEMBER |
vuejs | core | 802,504,723 | 3,444 | HcySunYang | Duplicate of https://github.com/vuejs/vue-next/issues/2863 | 2021-03-19T02:57:33 | 2021-03-19T02:57:33 | {} | MEMBER |
vuejs | core | 803,516,071 | 3,453 | hzsrc | This is just a `feature requests`, not a `question`.
Please take a second to see the content . | 2021-03-21T05:29:26 | 2021-03-21T05:29:26 | {} | NONE |
vuejs | core | 803,748,130 | 3,455 | trainiac | Using [jsx-next](https://github.com/vuejs/jsx-next), [recommended here](https://v3.vuejs.org/guide/render-function.html#jsx), for writing tsx files and using this syntax.
```tsx
import { defineComponent } from "vue";
defineComponent({
setup() {
const dom = ref(null)
return () => (
<div ref={d... | 2021-03-22T04:16:51 | 2021-03-22T04:20:26 | {
"+1": 1
} | NONE |
vuejs | core | 804,320,896 | 3,460 | ferdinando-ferreira | Here are the steps to test this proposed change
```
git clone git@github.com:ferdinando-ferreira/vue-next.git --single-branch vue-next-basic-renderer
cd vue-next-basic-renderer
yarn
yarn build
```
This builds (using the current source with this PR merged) the vue packages, including the newly created
```
... | 2021-03-22T19:08:02 | 2021-03-22T19:08:02 | {} | NONE |
vuejs | core | 804,713,121 | 3,462 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.92 KB (0%) |
| runtime-dom.global.prod.js | 27.17 KB (0%) |
| size-check.global.prod.js | 16.47 KB (0%) | | 2021-03-23T08:24:32 | 2021-03-23T08:24:32 | {} | NONE |
vuejs | core | 801,355,349 | 3,437 | LeonVlad | Thanks for the answer,
Everything was decided | 2021-03-17T19:35:17 | 2021-03-17T19:35:17 | {} | NONE |
vuejs | core | 802,056,128 | 3,445 | jacekkarczmarczyk | @LinusBorg you're using the "outside" `x`, OP is using another var defined inside the function
```js
const x = 1
function test() {
const x = 2
console.log(x) // 2
}
```
but
```js
ref: x = 1
function test() {
const x = 2
console.log(x) // 1
}
```
| 2021-03-18T16:12:02 | 2021-03-18T16:17:52 | {} | CONTRIBUTOR |
vuejs | core | 803,426,695 | 3,119 | 07akioni | Any progress? | 2021-03-20T17:11:48 | 2021-03-20T17:11:48 | {} | CONTRIBUTOR |
vuejs | core | 803,943,870 | 3,451 | posva | It doesn't make sense to use an async component as the root of the app though because it's displayed right away. You should wait for the dynamic import instead and then create the app **if the component is only known at runtime**. Otherwise, you should really remove the dynamic import because it will have a negative im... | 2021-03-22T10:12:54 | 2021-03-22T10:12:54 | {} | MEMBER |
vuejs | core | 804,307,310 | 3,451 | rhengles | @posva Thank you for your insightful input, and for listening and taking your time to respond.
I want to emphasize that you do not need to be concerned with performance, because when the app is shipped to production, they will be cached inside the app and the "load" won't have to make any network requests. So the as... | 2021-03-22T18:47:10 | 2021-03-22T18:47:10 | {} | NONE |
vuejs | core | 801,992,084 | 3,379 | reinink | @HcySunYang How does using `createSSRApp` in `browser.js` help with the server render (in `server.js`)?
I am trying to get SSR working in Vue 3 with Webpack, and running into the same error:
```
> node public/js/ssr.js
/Users/jonathan/Sites/inertia-ssr-vue3/public/js/ssr.js:15239
const { createComponentInsta... | 2021-03-18T14:51:30 | 2021-03-18T14:51:30 | {} | NONE |
vuejs | core | 803,741,494 | 3,456 | HcySunYang | Change this:
```js
const app = createApp(MainApp).use(store).use(router).mount("#app");
```
to:
```js
const app = createApp(MainApp)
app.use(store).use(router).mount("#app");
``` | 2021-03-22T03:50:38 | 2021-03-22T03:50:38 | {
"+1": 1
} | MEMBER |
vuejs | core | 804,711,972 | 3,428 | dependabot-preview[bot] | Superseded by #3462. | 2021-03-23T08:22:31 | 2021-03-23T08:22:31 | {} | CONTRIBUTOR |
vuejs | core | 804,804,210 | 3,466 | posva | Thanks but code is automatically formatted | 2021-03-23T10:50:24 | 2021-03-23T10:50:24 | {} | MEMBER |
vuejs | core | 805,050,588 | 3,469 | posva | That happens because the option being selected does not reflect the actual value being sent:
you are setting `"null"` or `""` instead of actually setting `null` which updates the value to no option on the other custom select while keeping the option you just clicked selected. But that's because the browser keeps it ... | 2021-03-23T16:35:11 | 2021-03-23T16:35:11 | {} | MEMBER |
vuejs | core | 801,202,236 | 3,437 | posva | Please read and follow https://new-issue.vuejs.org/?repo=vuejs/vue#why-repro | 2021-03-17T16:00:33 | 2021-03-17T16:00:33 | {} | MEMBER |
vuejs | core | 801,796,891 | 3,444 | posva | I think this is a duplicate of https://github.com/vuejs/vue-next/issues/2863 | 2021-03-18T10:11:06 | 2021-03-18T10:11:06 | {
"+1": 1
} | MEMBER |
vuejs | core | 803,210,087 | 3,451 | rhengles | @posva @HcySunYang
Here it is, without VueRouter: http://vue-next-example.arijs.org/no-router/
And here's the git repo: https://github.com/arijs/vue-next-example
Thank you for looking into this. | 2021-03-20T00:47:43 | 2021-03-20T00:55:25 | {} | NONE |
vuejs | core | 803,559,748 | 3,432 | zouyaoji | > Currently, if an event is declared as `emits`, then we have no way to access its listener, neither through `$props` nor `$attrs`. Most of the time it’s okay, but it’s a little uncomfortable in recursive components, see #3361
Here is a way to get the listener, which can be obtained through `instance.vnode.props`.
| 2021-03-21T11:30:17 | 2021-03-21T11:30:43 | {} | NONE |
vuejs | core | 803,717,405 | 3,455 | HcySunYang | This should work:
```js
defineComponent({
setup() {
const dom = ref(null)
return {
dom
}
},
render() {
return <div ref="dom"></div>
}
})
```
what do you actually mean? | 2021-03-22T02:18:59 | 2021-03-22T02:18:59 | {} | MEMBER |
vuejs | core | 803,725,406 | 1,531 | HcySunYang | This only happens when using `TransitionGroup` nested, the inner `TransitionGroup` applies transition to the child nodes, and the outer `TransitionGroup` applies transition to the parent node. These two transition effects are superimposed:
 ?
I explained it: it's not a good practice. Async components (as well as code splitting) are designed for the ... | 2021-03-22T19:01:05 | 2021-03-22T19:01:05 | {
"+1": 1,
"-1": 2
} | MEMBER |
vuejs | core | 804,325,224 | 3,460 | ferdinando-ferreira | ### Testing
The requirements to test these two php-v8 SSR versions are:
* php installed and in the path
* The extension [`v8js`](https://github.com/phpv8/v8js) available for this php install
Here is the result of both tests
`npm run start:phpv8-current` results in
```
> use-case@1.0.0 start:phpv8-curr... | 2021-03-22T19:11:47 | 2021-03-22T19:11:47 | {} | NONE |
vuejs | core | 804,603,693 | 994 | houfeng0923 | @yyx990803 @jods4 Sorry for appending comments in a closed issue .
Although I do understand component life-cycle considerations, **but i also like that 'unmounted' after 'after leave' is "intuitive".**
I had a similar problem with Vue2 and Vue3, and had to solve it in other ways. For example:
child componen... | 2021-03-23T04:15:24 | 2021-03-23T04:16:22 | {
"+1": 1
} | NONE |
vuejs | core | 805,054,094 | 3,470 | f-p-g | Well, this is a bug that occurs when using Vue 3.0.7.
If it helps, here is teh stack trace that I get in my version of the code (I am not sure how to get that in jsfiddle):
```
runtime-core.esm-bundler.js:38 [Vue warn]: Unhandled error during execution of scheduler flush. This is likely a Vue internals bug. Please o... | 2021-03-23T16:39:52 | 2021-03-23T16:45:18 | {} | NONE |
vuejs | core | 800,860,327 | 3,308 | ArthurSuz | > Why not merge this commit for so long time since it's already approved?
I also encountered the same problem. I have been waiting for the new version to be released, but I wrote a plugin before the release to temporarily solve this problem.
try: https://www.npmjs.com/package/keyframes-scoped-fix | 2021-03-17T07:26:23 | 2021-03-17T07:26:23 | {
"+1": 1
} | NONE |
vuejs | core | 800,914,152 | 3,308 | HcySunYang | You can all use [Knightly build](https://www.npmjs.com/package/@knightly/vue/v/pr3308) until the PR is merged | 2021-03-17T08:59:20 | 2021-03-17T08:59:20 | {} | MEMBER |
vuejs | core | 801,181,901 | 2,084 | HcySunYang | Closed, tracking here https://github.com/vuejs/rfcs/pull/284 | 2021-03-17T15:34:36 | 2021-03-17T15:34:36 | {} | MEMBER |
vuejs | core | 801,663,564 | 3,439 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.89 KB (0%) |
| runtime-dom.global.prod.js | 27.16 KB (0%) |
| size-check.global.prod.js | 16.47 KB (0%) | | 2021-03-18T06:21:33 | 2021-03-18T06:21:33 | {} | NONE |
vuejs | core | 803,372,692 | 3,377 | LinusBorg | @HcySunYang I did the change you proposed, can you have a look? Thanks! | 2021-03-20T15:10:01 | 2021-03-20T15:10:01 | {} | MEMBER |
vuejs | core | 804,626,743 | 2,513 | niqingyang | I have the same problem in 3.0.7. Is there a solution now？[the reproduce](https://stackblitz.com/edit/vue3-iframe-teleport-demo?file=src%2FApp.vue) | 2021-03-23T05:25:17 | 2021-03-23T05:44:06 | {} | NONE |
vuejs | core | 804,714,315 | 3,464 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.92 KB (0%) |
| runtime-dom.global.prod.js | 27.17 KB (0%) |
| size-check.global.prod.js | 16.47 KB (0%) | | 2021-03-23T08:26:37 | 2021-03-23T08:26:37 | {} | NONE |
vuejs | core | 804,201,470 | 3,457 | arpowers | @posva ok. But the original context behind the warning is lost (dynamic slots?) All I know is it's breaking SSR. | 2021-03-22T16:20:55 | 2021-03-22T16:20:55 | {} | NONE |
vuejs | core | 804,507,889 | 3,459 | HcySunYang | This is not a problem with vue, as shown in the figure below:
The jsx snippet you gave:
```html
<span innerHTML={msg.value}>{1 + 2}</span>
```
The equivalent template code is:
```html
<span ... | 2021-03-23T01:07:35 | 2021-03-23T01:07:35 | {} | MEMBER |
vuejs | core | 804,713,880 | 3,463 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.92 KB (0%) |
| runtime-dom.global.prod.js | 27.17 KB (0%) |
| size-check.global.prod.js | 16.47 KB (0%) | | 2021-03-23T08:25:53 | 2021-03-23T08:25:53 | {} | NONE |
vuejs | core | 802,499,160 | 3,445 | zhangenming | > @LinusBorg you're using the "outside" `x`, OP is using another var defined inside the function
>
> ```js
> const x = 1
> function test() {
> const x = 2
> console.log(x) // 2
> }
> ```
>
> but
>
> ```js
> ref: x = 1
> function test() {
> const x = 2
> console.log(x) // 1
> }
> ```
Not ... | 2021-03-19T02:46:37 | 2021-03-19T02:46:37 | {} | CONTRIBUTOR |
vuejs | core | 804,994,320 | 3,469 | Livijn | How is it normal that two components that are exactly the same, but just with a fewer amount of options, are rendered differently? | 2021-03-23T15:23:48 | 2021-03-23T15:23:48 | {} | NONE |
vuejs | core | 803,498,091 | 3,452 | HcySunYang | You can use functional components for that purpose
```js
import { FunctionalComponent } from 'vue'
const MyInput: FunctionalComponent<InputHTMLAttributes & { foo?: string}> = (props) => {
return <input {...props}/>
}
const el = <MyInput foo="str" autofocus type="xxx" />
```
For `defineComponent`, it ... | 2021-03-21T01:48:53 | 2021-03-21T01:48:53 | {
"+1": 3
} | MEMBER |
vuejs | core | 804,092,744 | 3,459 | kerm1it | Do we need to handle `null/undefined` when `unmountChildren`?
ref: https://github.com/vuejs/vue-next/blob/aea88c32804e95e99aa8c50f4e916713d49fd686/packages/runtime-core/src/renderer.ts#L2248 | 2021-03-22T14:10:36 | 2021-03-22T14:10:36 | {} | NONE |
vuejs | core | 804,329,113 | 3,460 | ferdinando-ferreira | ## Testing without php
Even without `php` and `v8js` it is possible to analyze the output of the proposed solution.
Here is the diff between dist/phpv8/current/index.js and dist/phpv8/proposed/index.js: it is essentially only the removal of `renderToStream` and their requirements from the build.
```patch
7104,... | 2021-03-22T19:17:49 | 2021-03-22T19:17:49 | {} | NONE |
vuejs | core | 804,350,678 | 3,451 | rhengles | Please just give me my footgun, I promise not to point it any dangerous ways 😅
But see, I know what I'm doing, I would very much like that the framework i'm using would not fight me back and make my job harder.
If Vue wants to hand-hold novice users, maybe that enforcement should be made in a higher level, like ... | 2021-03-22T19:53:56 | 2021-03-22T19:53:56 | {
"+1": 3
} | NONE |
vuejs | core | 804,518,736 | 3,459 | HcySunYang | I mean you should submit this issue in jsx-next, not here | 2021-03-23T01:38:30 | 2021-03-23T01:38:30 | {} | MEMBER |
vuejs | core | 800,863,432 | 3,434 | shen-zhao | > It’s better to use the first solution because it’s easier to understand
OK, I resubmit pr~ | 2021-03-17T07:31:42 | 2021-03-17T07:31:42 | {} | CONTRIBUTOR |
vuejs | core | 801,850,801 | 3,445 | LinusBorg | reproduction missing, also don't use `let` | 2021-03-18T11:39:13 | 2021-03-18T11:39:13 | {} | MEMBER |
vuejs | core | 802,655,032 | 3,441 | HcySunYang | Can be fixed in https://github.com/vuejs/vue-next/pull/3374, not released yet | 2021-03-19T08:39:56 | 2021-03-19T08:40:43 | {
"+1": 1
} | MEMBER |
vuejs | core | 802,996,363 | 2,626 | rhengles | @posva
I'm still having this problem. I'm not using Vite (yet), this is pure Vue v3.0.7.
Before I was passing a `Vue.defineAsyncComponent()` to the VueRouter configuration, but I already replaced that with a function that return a promise that returns the component definition.
I also am enhancing the `Vue.reso... | 2021-03-19T17:31:55 | 2021-03-19T17:31:55 | {} | NONE |
vuejs | core | 803,549,531 | 2,779 | florianrusch | Only adding the workaround from @edison1105 didn't work for me. (Reproduction Projekt: https://github.com/florianrusch/Foobar3)
I use `@vue/cli`. If I understand correctly the PR of @Xenonym (https://github.com/vuejs/docs-next/pull/779) and the note he added to the docs, I have to use `vue-loader` and thus a custom ... | 2021-03-21T10:23:27 | 2021-03-21T10:23:27 | {} | NONE |
vuejs | core | 804,185,941 | 3,451 | posva | > The sense is that I treat every single component as async in my app.
You should absolutely avoid treating **all** components as async ones. Only do it for components that are not always displayed right away, e.g. a modal, or the `v-else` branch that contains a heavy component like an inline editor.
> I'm just s... | 2021-03-22T16:01:56 | 2021-03-22T16:01:56 | {} | MEMBER |
vuejs | core | 805,008,786 | 2,943 | haoqunjiang | @jjdive I'm on my phone so I can't test it. But here's my guess:
It's because your jest version is outdated. Jest 24 uses jsdom v11 by default https://github.com/facebook/jest/blob/v24.0.0/packages/jest-environment-jsdom/package.json#L14 But Shadow DOM support was added in jsdom v12 https://github.com/jsdom/jsdom/pull/... | 2021-03-23T15:42:07 | 2021-03-23T15:42:07 | {} | MEMBER |
vuejs | core | 805,011,002 | 2,943 | haoqunjiang | You can either update your jest version or change the configuration to use a different testEnvironment, like what we do in Vue CLI v4 https://github.com/vuejs/vue-cli/blob/b0de229e78ae860c6ebc1e53f4bb481d7549cde7/packages/%40vue/cli-plugin-unit-jest/presets/default/jest-preset.js#L21 | 2021-03-23T15:45:00 | 2021-03-23T15:45:00 | {
"+1": 1
} | MEMBER |
vuejs | core | 801,074,572 | 3,436 | LinusBorg | That's already supported:
`import { toRaw } from 'vue'`
https://v3.vuejs.org/api/basic-reactivity.html#toraw | 2021-03-17T13:20:21 | 2021-03-17T13:20:21 | {
"rocket": 1
} | MEMBER |
vuejs | core | 801,877,925 | 3,445 | posva | Read https://new-issue.vuejs.org/?repo=vuejs/vue-next#why-repro. There are links too | 2021-03-18T12:13:41 | 2021-03-18T12:13:41 | {} | MEMBER |
vuejs | core | 802,001,027 | 3,379 | reinink | @carlosmaniero THANK YOU SO MUCH. That worked! 🙌 | 2021-03-18T15:03:05 | 2021-03-18T15:03:05 | {
"heart": 1
} | NONE |
vuejs | core | 802,495,711 | 3,445 | zhangenming | > You are misunderstanding how `ref:` works:
>
> ```
> ref: x = 1
> function test() {
> x = 2
> console.log(x) //will show 2
> }
> ```
你应该没明白我的意思
我是说
我用ref申请了一个变量x
然后在函数内也申请了一个变量, 名字叫x, 恰巧和外面的ref相同了
那么 编译器就会把函数内部的x 当成ref的x
这意味着 我x是全局的了 内部不能有相同的名字
难道这是正常的?
这应该是一个bug
You may not understand what ... | 2021-03-19T02:39:41 | 2021-03-19T03:16:21 | {} | CONTRIBUTOR |
vuejs | core | 802,912,905 | 3,445 | edison1105 | @zhangenming yes, see test case in the PR. | 2021-03-19T15:24:11 | 2021-03-19T15:25:24 | {} | MEMBER |
vuejs | core | 803,556,778 | 2,779 | edison1105 | > I have to use vue-loader and thus a custom webpack configuration to set the compiler option
@florianrusch yes | 2021-03-21T11:12:26 | 2021-03-21T11:12:26 | {} | MEMBER |
vuejs | core | 803,560,403 | 3,432 | HcySunYang | @zouyaoji Sure, but it is not for the users, we are talking about the user interface | 2021-03-21T11:33:58 | 2021-03-21T11:33:58 | {} | MEMBER |
vuejs | core | 803,698,755 | 2,019 | xSeek-Neo | When Is Vue3 Compatible with Internet Explorer 11? | 2021-03-22T01:04:28 | 2021-03-22T01:04:28 | {} | NONE |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.