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 | 481,498,712 | 9 | yyx990803 | Closing in favor of https://github.com/vuejs/rfcs/pull/8 and https://github.com/vuejs/rfcs/pull/31 | 2019-04-10T01:30:52 | 2019-04-10T01:30:52 | {} | MEMBER |
vuejs | core | 481,647,202 | 33 | yyx990803 | @posva making the first argument `Element | Array<Element>` is still a breaking change, in fact it requires heavier refactoring to make sure existing directives work properly. It's also not clear what a directive should do in the case of receiving multiple elements: what should `v-focus` or `v-clickaway` do in such cas... | 2019-04-10T11:12:03 | 2019-04-10T11:12:24 | {} | MEMBER |
vuejs | core | 499,529,209 | 35 | posva | > I don't understand the question. Watchers have always been working this way. If you want to trigger watcher with nested mutations you should be using deep: true.
I'm realizing I have been teaching a way of doing this that is more complicated than it should because using an array also works 😅. It may trigger more ... | 2019-06-06T14:54:05 | 2019-06-06T14:54:05 | {} | MEMBER |
vuejs | core | 499,788,404 | 35 | yyx990803 | > I think that practice has shown us that people don't read the documentation, no matter how good it is.
I don't think that's true at all. People probably don't read the API listing in full details, but they definitely read the guide when they first learn Vue. The point is - anyone learning the new API will have to... | 2019-06-07T07:36:09 | 2019-06-07T07:36:09 | {} | MEMBER |
vuejs | core | 514,420,522 | 41 | gustojs | Point 3) is fine as long as it's an addition and not a replacement.
If it is a replacement of the current API, it will be treated as a betrayal of the "we won't drop Object API" promise, regardless of the changes making sense or not. Users want to keep using computed and methods as separate options.
Even making i... | 2019-07-23T23:31:10 | 2019-07-23T23:39:00 | {} | MEMBER |
vuejs | core | 514,574,276 | 41 | posva | > Regarding this, we could document it as the context too, so no $context necessary and no context switching?
But that could be very confusing because `context` do not have access to everything in `create`, eg: `$refs` aren't there yet | 2019-07-24T10:21:54 | 2019-07-24T10:21:54 | {} | MEMBER |
vuejs | core | 514,627,544 | 41 | Akryum | 👍 | 2019-07-24T13:16:37 | 2019-07-24T13:16:37 | {} | MEMBER |
vuejs | core | 514,655,064 | 41 | Akryum | Shouldn't just put `this` as the context in `create` too and remove the arg? 😅 | 2019-07-24T14:26:35 | 2019-07-24T14:26:35 | {} | MEMBER |
vuejs | core | 476,118,814 | 27 | yyx990803 | @posva
> if $attrs contains onListeners, if you do <div v-bind="$attrs"/>, we are binding a dom property onClick (which doesn't exist) to the div
That's what I mentioned in the "Unresolved questions".
> is v-bind going to handle onAttribute properties automatically as events?
Yes. This is not really a brea... | 2019-03-25T09:34:58 | 2019-03-25T09:34:58 | {
"+1": 1
} | MEMBER |
vuejs | core | 476,142,974 | 29 | posva | I enjoy destructuring arguments in the render function, it makes it easier to ignore unused arguments. Is it really better to have multiple parameters? It's to avoid allocating an extra object every time we call render, isn't it? | 2019-03-25T10:46:58 | 2019-03-25T10:46:58 | {} | MEMBER |
vuejs | core | 480,720,115 | 30 | posva | but what is the deal with global plugin install? it only worked while prototyping | 2019-04-08T07:40:55 | 2019-04-08T07:40:55 | {} | MEMBER |
vuejs | core | 480,745,552 | 29 | yyx990803 | Published: https://github.com/vuejs/rfcs/pull/28 | 2019-04-08T08:57:26 | 2019-04-08T08:57:26 | {} | MEMBER |
vuejs | core | 481,601,878 | 33 | posva | I think it will make sense to still support directives on components, even if we receive an array of elements. Some DOM manipulations like v-focus or v-clickaway are still valid for components. This will also make the adoption strategy a bit harder | 2019-04-10T08:52:28 | 2019-04-10T08:52:28 | {
"+1": 2
} | MEMBER |
vuejs | core | 499,445,180 | 35 | shentao | Kinda agree on the drawback @posva mentioned. Thought the `setup` would be intended to go along the object properties and not entirely replacing them. | 2019-06-06T10:46:30 | 2019-06-06T10:46:30 | {} | MEMBER |
vuejs | core | 499,941,615 | 35 | yyx990803 | @KaelWD it's more like `beforeCreate`. It will be called only after `beforeCreate` and props resolution, but before all other 2.x options. | 2019-06-07T15:58:44 | 2019-06-07T15:58:44 | {} | MEMBER |
vuejs | core | 503,736,666 | 37 | LinusBorg | Thanks , that makes sense.
how would the compiler be included in bundler projects? | 2019-06-19T20:36:13 | 2019-06-19T20:37:18 | {} | MEMBER |
vuejs | core | 514,518,308 | 41 | nekosaur | Touching on @gustojs comment on point 4, I actually think users _won't_ swallow having to type e.g. `this.$context.$vuex` every time very easily.
I do like the other points, especially the renaming. My only concern with regard to point 3 is that while it resembles both the function api and the object api, it's still... | 2019-07-24T07:40:50 | 2019-07-24T07:40:50 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 514,674,858 | 41 | chrisvfritz | > But if the user cannot inject anything into the parameter, they already know it comes from the API.
@posva They technically _could_ in `onBeforeCreate` or by adding properties to the prototype, _if_ we make `context` the exact same object as `this` in other options, which I think we should do to guarantee consiste... | 2019-07-24T15:13:27 | 2019-07-24T15:16:24 | {} | CONTRIBUTOR |
vuejs | core | 515,218,060 | 41 | gustojs | Imho we *can* touch it, cause we're touching it anyways with other RFCs. Just not to this point. | 2019-07-25T21:17:43 | 2019-07-25T21:18:26 | {} | MEMBER |
vuejs | core | 499,925,661 | 35 | KaelWD | > `const plusOne = computed(() => count.value + 1)`
Could that also be `const plusOne = computed(() => this.count + 1)` or is `setup` more like `beforeCreate`? | 2019-06-07T15:17:15 | 2019-06-07T15:17:15 | {} | CONTRIBUTOR |
vuejs | core | 515,219,778 | 41 | shentao | IMO we should try to just add the API without really touching the Object syntax at all and have it inside the "advanced components" section or create an entirely new docs section (that talks about component composition, code reuse, what to use instead of mixins etc. Not "alternative-component-format").
And I think ... | 2019-07-25T21:23:27 | 2019-07-25T21:25:04 | {} | MEMBER |
vuejs | core | 516,615,551 | 41 | yyx990803 | @chrisvfritz
> A) They'll have to completely rewrite their existing apps when migrating. (Or even if a codemod does it for them, they'll have to spend a lot of time and energy relearning concepts.)
No one will have to rewrite their code. This proposal does not change anything about that.
> B) Vue is moving to ... | 2019-07-30T22:11:19 | 2019-07-30T22:11:50 | {
"confused": 2
} | MEMBER |
vuejs | core | 476,581,797 | 25 | yyx990803 | Published: https://github.com/vuejs/rfcs/pull/23 | 2019-03-26T11:16:35 | 2019-03-26T11:16:35 | {} | MEMBER |
vuejs | core | 476,603,282 | 24 | LinusBorg | I don't see why not. We do it with `Vue.observable()` today as well, basically. | 2019-03-26T12:28:14 | 2019-03-26T12:28:14 | {} | MEMBER |
vuejs | core | 514,629,524 | 41 | posva | Can we properly type that by providing a `this` parameter to the different hooks like `create`, `onCreated` and others? eg: right now `$el` is always an element but it's undefined in `beforeCreate`.
I really don't like having a `$context`, I do believe people will find that to be very verbose. Having `this` seems to... | 2019-07-24T13:21:59 | 2019-07-24T13:21:59 | {} | MEMBER |
vuejs | core | 514,634,670 | 41 | chrisvfritz | > Can we properly type that by providing a this parameter to the different hooks like create, onCreated and others? eg: right now $el is always an element but it's undefined in beforeCreate.
I _think_ we probably can, at least as intellisense provided by Vetur - but many users either don't code in environments where... | 2019-07-24T13:35:34 | 2019-07-24T13:40:25 | {} | CONTRIBUTOR |
vuejs | core | 514,645,791 | 41 | chrisvfritz | @posva I can understand why that would be confusing - sorry about that! 😅 I'm _not_ suggesting `this` be available in `create`. Instead, I'd prefer they learn that the `context` argument in `create` is the same object (but earlier in the lifecycle, so not as many properties) as `this` in _other_ options like `onCreate... | 2019-07-24T14:03:45 | 2019-07-24T14:06:28 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 480,708,987 | 31 | LinusBorg | Great. | 2019-04-08T07:02:12 | 2019-04-08T07:02:12 | {} | MEMBER |
vuejs | core | 482,405,796 | 33 | yyx990803 | Revised and published: https://github.com/vuejs/rfcs/pull/32 | 2019-04-12T01:55:36 | 2019-04-12T01:55:36 | {} | MEMBER |
vuejs | core | 499,439,359 | 35 | posva | ## Motivation > Bundle Size
The returned object in `setup` will still keep the original names, wouldn't it? I was wondering if it's possible to mangle those in production with some activable option, it could reduce the size of apps even more.
## Detailed Design > State
is `state` dropped in favor of always usi... | 2019-06-06T10:26:06 | 2019-06-06T10:49:00 | {} | MEMBER |
vuejs | core | 514,571,199 | 41 | Akryum | > I do like the other points, especially the renaming. My only concern with regard to point 3 is that while it resembles both the function api and the object api, it's still a 3rd way of doing things, which will potentially increase the amount of context switching done.
@nekosaur There is actually only one way. It's... | 2019-07-24T10:12:28 | 2019-07-24T10:12:28 | {} | MEMBER |
vuejs | core | 480,380,952 | 30 | Jinjiang | Will it break the auto-installation feature like `vuex` or `vue-i18n`?
``` html
<script src="/path/to/vue.js"></script>
<script src="/path/to/vuex.js"></script>
```
If I don't misunderstand we couldn't "install" or "use" a feature before an app created. Does it mean this kind of global installation would be ba... | 2019-04-05T18:38:59 | 2019-04-05T18:40:39 | {} | MEMBER |
vuejs | core | 480,490,227 | 30 | yyx990803 | @LinusBorg most plugins should be able to remain unchanged, with some exceptions:
- implicit global installations won't work anymore
- if a plugin relies on [tree-shakable global APIs](https://github.com/vuejs/rfcs/pull/19) (e.g. `nextTick`), these won't be available on the passed app instance anymore and must be... | 2019-04-06T09:38:48 | 2019-04-06T09:38:48 | {} | MEMBER |
vuejs | core | 480,724,237 | 30 | LinusBorg | > it only worked while prototyping
Not sure what you mean.
I'm sure there are a ton of production apps out there that use Vue in server-rendered pages and include it from a CDN, along with plugins:
```
<script src="http://unpkg.com/vue/dist/vue.min.js"></script>
<script src="http://unpkg.com/some-plugin.min... | 2019-04-08T07:53:36 | 2019-04-08T07:53:36 | {} | MEMBER |
vuejs | core | 481,146,855 | 2 | yyx990803 | Closing in favor of public RFCs. | 2019-04-09T08:04:32 | 2019-04-09T08:04:32 | {} | MEMBER |
vuejs | core | 499,955,218 | 35 | gustojs | ```
const writableComputed = computed(
// read
() => count.value + 1,
// write
val => {
count.value = val - 1
}
)
```
I like how it's much easier to switch between a read-only and writeable computed properties without having to rewrite between an object and functions. | 2019-06-07T16:40:37 | 2019-06-07T17:22:45 | {} | MEMBER |
vuejs | core | 504,018,008 | 38 | HcySunYang | Oh, it makes sense. | 2019-06-20T13:05:01 | 2019-06-20T13:05:01 | {} | MEMBER |
vuejs | core | 514,421,094 | 41 | Akryum | I like it. 🐈 | 2019-07-23T23:33:51 | 2019-07-23T23:33:51 | {} | MEMBER |
vuejs | core | 514,626,192 | 41 | chrisvfritz | > the last example there should be explained in a very detailed manner. I have some concerns about using asynchronous logic there as it might create a cognitive overload for newer developers.
@NataliaTepluhina I agree 100%! I think we can also think up some even simpler examples at that point in the docs, since we w... | 2019-07-24T13:12:47 | 2019-07-24T13:13:00 | {} | CONTRIBUTOR |
vuejs | core | 722,159,461 | 2,349 | shameleo | Yep, but I need event, not just property. | 2020-11-05T05:55:11 | 2020-11-05T05:55:11 | {
"+1": 5
} | NONE |
vuejs | core | 722,169,552 | 2,349 | justintaddei | Same thing here. I'm using the activated hook to tell when I need to record the position of the elements and animate from their previous state. Simply haven't a property would not work for my case. | 2020-11-05T06:22:40 | 2020-11-05T06:22:40 | {} | NONE |
vuejs | core | 722,912,353 | 2,562 | LinusBorg | I'll reopen this for now to explore this. This is a bit of an edge case where in Vue 2, `vnode.context` would have given you `ComponentB` indeed, as the vnode context gives you the instance that the elements belongs to.
`binding.instance` gives you the instance whose template contains the directive, and I'd think th... | 2020-11-06T06:55:47 | 2020-11-06T06:55:47 | {} | MEMBER |
vuejs | core | 723,891,792 | 2,549 | luwuer | Why attribute inheritance is not supported on fragments,is it limited by the difficulty of implementation? @LinusBorg | 2020-11-09T09:36:27 | 2020-11-09T09:36:27 | {} | CONTRIBUTOR |
vuejs | core | 723,951,222 | 2,566 | asoglovo | Oh, didn't know that :) Thanks for the clarification | 2020-11-09T11:22:36 | 2020-11-09T11:22:36 | {} | NONE |
vuejs | core | 725,926,858 | 2,594 | LinusBorg | > maintain its own state,
functional components in Vue are stateless | 2020-11-12T08:33:24 | 2020-11-12T08:33:24 | {
"+1": 1
} | MEMBER |
vuejs | core | 725,928,057 | 2,595 | posva | Duplicate of https://github.com/vuejs/vue-next/issues/2474 | 2020-11-12T08:35:33 | 2020-11-12T08:35:33 | {} | MEMBER |
vuejs | core | 723,422,548 | 2,570 | posva | This is normal and to avoid it you need to link vue in both libraries and applications that use linked libraries. There will be a note on docs.
You can also use yarn pack to avoid the issue, you should take a look at existing issues for a full command | 2020-11-07T09:23:01 | 2020-11-07T09:23:01 | {
"heart": 1
} | MEMBER |
vuejs | core | 723,783,441 | 1,991 | anming-john | @posva i have the same warn , and then it output an error like
i seem like a vue error , how can i fixed it ? thank a lot | 2020-11-09T06:12:10 | 2020-11-09T06:12:10 | {} | NONE |
vuejs | core | 723,952,346 | 2,549 | LinusBorg | Because its unclear on which element to inherit.
* Only the first one?
* Or all?
The latter would create invalid HTML for an `id` attribute, for example, but it could be useful for a `class`. | 2020-11-09T11:24:50 | 2020-11-09T11:24:50 | {} | MEMBER |
vuejs | core | 724,234,008 | 2,579 | 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... | 2020-11-09T19:39:24 | 2020-11-09T19:39:24 | {} | CONTRIBUTOR |
vuejs | core | 724,761,055 | 2,215 | jods4 | Got hit by this as well, I had a `<Suspense>` around `<RouterView>`.
My goal was of course to load async routes but it doesn't work anymore since the component directly inside `<Suspense>` must change to go back to pending state.
What would _really_ help here is to put a warning in dev mode when this happens, right... | 2020-11-10T15:05:59 | 2020-11-10T15:05:59 | {
"+1": 3
} | CONTRIBUTOR |
vuejs | core | 725,861,566 | 2,027 | luchaoqun123 | vue3 中，这个是devtools 6.0.0 beta 2打印的，我把devtools关闭，这个waring就消失了 | 2020-11-12T06:10:40 | 2020-11-12T06:10:40 | {
"+1": 7,
"-1": 10,
"confused": 8,
"eyes": 5,
"heart": 2,
"hooray": 1,
"laugh": 3,
"rocket": 1
} | NONE |
vuejs | core | 726,243,117 | 2,598 | jods4 | @vhoyer saying it's consistent with JS is implying you know the underlying implementation.
Javascript has `Number()` ctor, which is a far better tool to parse numbers.
How is it consistent with javascript that `.number` returns a different result from `Number()`?
The modifier isn't called `.parseFloat` so I'd say I... | 2020-11-12T18:02:49 | 2020-11-12T18:02:49 | {
"+1": 2
} | CONTRIBUTOR |
vuejs | core | 722,963,976 | 2,566 | haoqunjiang | A temporary workaround: use `:lang="''"`, because the SFC parser only checks for the static `lang` attribute, so a dynamic one can circumvent this check. | 2020-11-06T09:03:37 | 2020-11-06T09:04:26 | {} | MEMBER |
vuejs | core | 723,886,255 | 2,571 | 101arrowz | Tree shaking doesn't work with HMR, hence ESM is useless when developing with HMR and transpiling ESM to CommonJS, which is ultimately used in the final build, only slows the build down.
You can't assume ESM is bundler and CJS is Node anymore; Node supports ESM loading. Instead, the `"browser"` field of package.json ... | 2020-11-09T09:26:56 | 2020-11-09T09:26:56 | {} | NONE |
vuejs | core | 724,248,910 | 2,571 | mischnic | > If you really want to force Parcel to unnecessarily transpile ESM in development, setting the "browser" field to the ESM version will fix the issue.
👍
<br>
(The modern way for different builds for esm/cjs/node is the `exports` field: https://webpack.js.org/guides/package-exports/#target-environment.)
| 2020-11-09T20:07:00 | 2020-11-09T20:11:40 | {} | NONE |
vuejs | core | 724,523,066 | 2,569 | edison1105 | > hi @edison1105 , could you rebase the code? if you rebase your fork repo's master branch, then you won't get redundant commit logs in your new PR :)
I will do it , Thanks! | 2020-11-10T07:40:09 | 2020-11-10T07:40:09 | {} | MEMBER |
vuejs | core | 725,457,060 | 1,539 | phaust | I agree with @aztalbot.
I'd love to keep using SFCs `<style scoped>` section along with render functions. I have some components which have such dynamic template code (e.g. conditional event listeners and props) that using `<template>` would probably be a bad decision. Having all the styles encapsulated in the `<sty... | 2020-11-11T14:34:11 | 2020-11-11T14:49:55 | {
"+1": 3
} | NONE |
vuejs | core | 725,934,259 | 2,593 | skirtles-code | An alternative workaround is to put `transition: none;` in `.test-leave-from`. | 2020-11-12T08:47:21 | 2020-11-12T08:47:21 | {} | CONTRIBUTOR |
vuejs | core | 721,559,561 | 2,553 | posva | Forgot to say it only happens in production! Updated the issue to reflect it | 2020-11-04T07:24:06 | 2020-11-04T07:24:06 | {
"+1": 1
} | MEMBER |
vuejs | core | 721,576,999 | 2,349 | shameleo | My use case is [v-keep-scroll](https://github.com/mark-hahn/vue-keep-scroll/blob/master/src/vue-keep-scroll.coffee) directive.
In Chrome elements loose their scroll positions when detouched from DOM, so the directive fixes it. It saves scroll positions in attributes and restores it when component is activated. Can't ... | 2020-11-04T08:07:00 | 2020-11-04T08:07:00 | {} | NONE |
vuejs | core | 721,669,001 | 2,550 | LinusBorg | As a workaround, pass a new array on every change instead of mutating the same one. | 2020-11-04T11:10:08 | 2020-11-04T11:10:08 | {
"+1": 1
} | MEMBER |
vuejs | core | 723,964,137 | 2,549 | luwuer | I got it, thx. | 2020-11-09T11:48:15 | 2020-11-09T11:48:15 | {} | CONTRIBUTOR |
vuejs | core | 724,603,104 | 2,573 | LongTengDao | the main problem won't happen in components, and the root component rarely has props, so this PR is not necessary. | 2020-11-10T10:10:15 | 2020-11-10T10:10:15 | {} | CONTRIBUTOR |
vuejs | core | 725,314,440 | 2,587 | 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). | 2020-11-11T09:34:17 | 2020-11-11T09:34:17 | {} | MEMBER |
vuejs | core | 719,802,505 | 2,532 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | -------------------- |
| vue.global.prod.js | 40.15 KB (-0.35% 🔽) |
| runtime-dom.global.prod.js | 26.44 KB (0%) |
| size-check.global.prod.js | 15.95 KB (0%) | | 2020-10-30T21:13:49 | 2020-11-11T15:39:40 | {} | NONE |
vuejs | core | 725,895,318 | 2,594 | StarFishing | > 1. browsers don't support jsx
> 2. in html you need to use kebab-case for tag names
> 3. move `value = Vue.ref(1)` outside the render function or don't use functional components
>
> https://jsfiddle.net/bpzsqf2k/
Does the function component support ref or other ways to maintain its own state, like react use... | 2020-11-12T07:30:54 | 2020-11-12T07:30:54 | {} | NONE |
vuejs | core | 726,318,153 | 2,571 | 101arrowz | As far as I know, only bundlers support the `"browser"` key, and since bundlers can replace the environment variables, it should work... | 2020-11-12T20:18:50 | 2020-11-12T20:18:50 | {} | NONE |
vuejs | core | 721,535,468 | 2,555 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.15 KB (0%) |
| runtime-dom.global.prod.js | 26.43 KB (0%) |
| size-check.global.prod.js | 15.95 KB (0%) | | 2020-11-04T06:20:42 | 2020-11-04T06:20:42 | {} | NONE |
vuejs | core | 721,659,651 | 2,551 | lgd8981289 | Thanks, but I want to know how I can solve this problem in the existing version。 | 2020-11-04T10:50:23 | 2020-11-04T10:50:54 | {} | NONE |
vuejs | core | 722,168,340 | 2,559 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.15 KB (0%) |
| runtime-dom.global.prod.js | 26.43 KB (0%) |
| size-check.global.prod.js | 15.95 KB (0%) | | 2020-11-05T06:19:28 | 2020-11-05T06:19:28 | {} | NONE |
vuejs | core | 725,752,292 | 2,591 | edison1105 | It's call `serverPrefetch` in vue3 | 2020-11-12T00:59:09 | 2020-11-12T00:59:09 | {} | MEMBER |
vuejs | core | 726,203,016 | 2,598 | posva | I would say this is expected. It is consistent with Vue 2. Changing it would create trouble for users when migrating.
If you want to handle the string yourself, then it's better not to use the v-model number modifier and use a computed property instead to format the value as you wish.
You can also use custom v-mode... | 2020-11-12T16:54:43 | 2020-11-12T16:54:43 | {
"+1": 1
} | MEMBER |
vuejs | core | 726,314,801 | 2,571 | posva | If I recall correctly, using "browser" for the ESM breaks other things because it's not a browser module, it contains environment variables | 2020-11-12T20:12:16 | 2020-11-12T20:12:16 | {} | MEMBER |
vuejs | core | 722,432,232 | 2,562 | LinusBorg | the vnode represents the element, not the component.
The corrent way to access the component ìn Vue 3 is `binding.instance` | 2020-11-05T15:00:15 | 2020-11-05T15:00:15 | {} | MEMBER |
vuejs | core | 722,918,081 | 2,532 | antfu | Build with Vite is not working (Dev OK). Repro: https://github.com/antfu/vite-starter-ref-sugar
```vue
<script setup>
import { computed } from 'vue'
ref: count = 0
ref: doubled = computed(() => count * 2)
const inc = () => count++
const dec = () => count -= 1
</script>
<template>
<div>{{ count }} *... | 2020-11-06T07:09:17 | 2020-11-06T07:09:17 | {
"confused": 1
} | MEMBER |
vuejs | core | 722,962,805 | 2,566 | haoqunjiang | It's a bug in `@vue/compiler-sfc`.
https://github.com/vuejs/vue-next/blob/43579a8de358846de96d0d789eebbebf95b2f391/packages/compiler-sfc/src/parse.ts#L114-L121 | 2020-11-06T09:01:12 | 2020-11-06T09:01:12 | {} | MEMBER |
vuejs | core | 723,933,846 | 2,566 | asoglovo | For a case like this where you add attributes to native elements, wouldn't the `data-*` [html attributes](https://developer.mozilla.org/en-US/docs/Learn/HTML/Howto/Use_data_attributes) be a better fit? | 2020-11-09T10:49:31 | 2020-11-09T10:49:31 | {} | NONE |
vuejs | core | 723,949,523 | 2,566 | xPaw | `lang` is a HTML attribute. https://developer.mozilla.org/en-US/docs/Web/HTML/Global_attributes/lang | 2020-11-09T11:19:12 | 2020-11-09T11:19:12 | {} | NONE |
vuejs | core | 725,316,703 | 2,585 | posva | When reporting a bug please provide a boiled down reproduction with **only** what is necessary to reproduce the bug (https://new-issue.vuejs.org/?repo=vuejs/vue#why-repro)
Open a new issue once you have a boiled down reproduction (eg no tests, no ts, no docker, etc) | 2020-11-11T09:38:44 | 2020-11-11T09:38:44 | {
"+1": 1
} | MEMBER |
vuejs | core | 725,353,857 | 2,531 | luwuer | I find that this issue should be added a `bug` label @LinusBorg , here is my analysis:
Suppose the user-defined direcitve looks like following(similar to `v-show`), pay attention to the comments(`step 1` & `step 2`) and now let's look at the classes change.
```javascript
const visibility = {
beforeMount(el, ... | 2020-11-11T10:53:42 | 2020-11-12T05:56:58 | {} | CONTRIBUTOR |
vuejs | core | 725,892,842 | 2,594 | jacekkarczmarczyk | 1. browsers don't support jsx
2. in html you need to use kebab-case for tag names
3. move `value = Vue.ref(1)` outside the render function or don't use functional components
https://jsfiddle.net/bpzsqf2k/ | 2020-11-12T07:25:12 | 2020-11-12T07:25:12 | {} | CONTRIBUTOR |
vuejs | core | 723,733,298 | 2,027 | anming-john | > `watch(route)` is implicitly `deep: true`, which traverses arbitrarily deep properties. So technically, this is expected behavior. Also, deep traversing a complex object when you only care about a few properties is wasteful.
>
> Your use case can and **should** be rewritten using a computed property instead:
>
... | 2020-11-09T03:30:30 | 2020-11-09T03:30:30 | {
"+1": 2,
"-1": 1
} | NONE |
vuejs | core | 723,915,478 | 2,573 | LongTengDao | doc said the only rule is not to use key start with `_` or `$`, if this is intended and won't be fix, I think it will be good to write in doc and make a warn check in Vue, not treat it as if it not happen | 2020-11-09T10:16:37 | 2020-11-09T10:16:37 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 721,729,377 | 2,349 | LinusBorg | Note: at least for Browser environments, you should be able to use [`Node.isConnected`](https://developer.mozilla.org/en-US/docs/Web/API/Node/isConnected) (at least for some use cases) to check wether the element is in the DOM (=component is active) or not (=component is deactivatdd by keep-alive) | 2020-11-04T13:24:09 | 2020-11-04T13:29:18 | {
"eyes": 2
} | MEMBER |
vuejs | core | 722,532,566 | 2,557 | LinusBorg | The problem is located here:
https://github.com/vuejs/vue-next/blob/a15ec11d03e6a41a975bf2daa72c87f01bd5bd32/packages/reactivity/src/ref.ts#L251
The index signature makes TS loose the `Person` type and only contains public properties.
Plain TS example:
[TS Playground Repro](https://www.typescriptlang.org/pl... | 2020-11-05T17:44:09 | 2020-11-05T17:48:46 | {} | MEMBER |
vuejs | core | 723,658,300 | 2,572 | LinusBorg | You have to import this component from Vue now.
```js
import { TransitionGroup } from 'vue'
...
h(TransitionGroup ....
```
When using templates, the compiler does this for you.
In case you wonder why: this is so that the component can be tree-shaken form your bundled app if you don't actually use it. | 2020-11-08T20:02:20 | 2020-11-08T21:18:12 | {
"+1": 4,
"hooray": 1
} | MEMBER |
vuejs | core | 724,054,410 | 1,600 | martinbean | Any one…? | 2020-11-09T14:39:39 | 2020-11-09T14:39:39 | {
"+1": 6
} | NONE |
vuejs | core | 725,928,237 | 2,595 | posva | @silkwromzf transfered to the correct repository | 2020-11-12T08:35:54 | 2020-11-12T08:35:54 | {} | MEMBER |
vuejs | core | 722,168,504 | 2,560 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.15 KB (0%) |
| runtime-dom.global.prod.js | 26.43 KB (0%) |
| size-check.global.prod.js | 15.95 KB (0%) | | 2020-11-05T06:19:51 | 2020-11-05T06:19:51 | {} | NONE |
vuejs | core | 722,549,340 | 1,409 | LinusBorg | > correct me if I'm wrong but tree-shaking happens after module resolution. So I don't think it would help at all. If a dependency is missing -> module resolution fails -> build fails before tree-shaking.
By making vue-router a dependency of your component library, it will never be missing. and tree-shaking will rem... | 2020-11-05T18:12:43 | 2020-11-05T18:12:58 | {} | MEMBER |
vuejs | core | 722,736,601 | 2,562 | zq8024 | > the vnode represents the element, not the component.
>
> The corrent way to access the component ìn Vue 3 is `binding.instance`
I want get CompB component instance in directive, but `binding.instance` is App component instance, how can i get CompB instance in directive? | 2020-11-06T00:58:54 | 2020-11-06T00:58:54 | {} | NONE |
vuejs | core | 723,817,492 | 2,578 | 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... | 2020-11-09T07:25:11 | 2020-11-09T07:25:11 | {} | CONTRIBUTOR |
vuejs | core | 724,485,139 | 2,581 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.15 KB (0%) |
| runtime-dom.global.prod.js | 26.44 KB (0%) |
| size-check.global.prod.js | 15.95 KB (0%) | | 2020-11-10T06:22:03 | 2020-11-10T06:22:03 | {} | NONE |
vuejs | core | 725,223,007 | 2,586 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.15 KB (0%) |
| runtime-dom.global.prod.js | 26.44 KB (0%) |
| size-check.global.prod.js | 15.95 KB (0%) | | 2020-11-11T06:11:04 | 2020-11-11T06:11:04 | {} | NONE |
vuejs | core | 725,951,829 | 2,593 | luwuer | Thanks in the first place.
In fact, i create this example on purpose. Because i find current logic does not deal with this scence when im dealing with another issue. | 2020-11-12T09:18:48 | 2020-11-12T09:24:07 | {} | CONTRIBUTOR |
vuejs | core | 722,168,172 | 2,558 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.15 KB (0%) |
| runtime-dom.global.prod.js | 26.43 KB (0%) |
| size-check.global.prod.js | 15.95 KB (0%) | | 2020-11-05T06:19:00 | 2020-11-05T06:19:00 | {} | NONE |
vuejs | core | 722,962,284 | 2,566 | haoqunjiang | Sorry for closing the other issue too soon. As the original reproduction was too big, I tried to reproduce with a hello-world project. When I tried `div lang=""` on that project, it worked.
It is because I missed a critical part of the bug - besides the `lang=""` attribute, the content of the element needs contain a... | 2020-11-06T09:00:08 | 2020-11-06T09:00:08 | {} | MEMBER |
vuejs | core | 723,534,220 | 2,195 | basvanmeurs | It would be a nice feature to be able to reuse a previously created effect scope.
Use case: global utilities such as localizations might want to use reactivity as well. For example, translations data may be made reactive, and lookups may be cached using a computed internally. Those computeds may be lazily created.
... | 2020-11-08T05:44:48 | 2020-11-08T05:44:48 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 723,888,456 | 2,578 | underfin | Same as https://github.com/vuejs/vue-next/pull/2567 | 2020-11-09T09:30:46 | 2020-11-09T09:30:46 | {} | MEMBER |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.