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 | 873,646,993 | 4,060 | LinusBorg | The thing is, it's inconsistent. Vue 3 *does* trigger watch callbacks when provided a normal object. Like Vue 2. But for $attrs it doesnt work. | 2021-07-04T19:20:25 | 2021-07-04T19:20:25 | {} | MEMBER |
vuejs | core | 873,674,845 | 4,055 | yyx990803 | Exposed instance should not expose global properties, because they are also injected by the user.
The exposed proxy only exposes two types of properties:
1. Explicitly exposed ones
2. Vue built-in public properties | 2021-07-04T22:30:48 | 2021-07-04T22:30:48 | {} | MEMBER |
vuejs | core | 873,992,047 | 4,064 | way2ex | Sorry to bother, I have found that I can use alias to let `@vue/compiler-doc` redirect to `@vue/compiler-doc/dist/compiler-dom.cjs` | 2021-07-05T10:14:54 | 2021-07-05T10:14:54 | {
"+1": 1
} | NONE |
vuejs | core | 874,278,575 | 4,061 | yyx990803 | This is expected behavior. `v-if` destroys the component and remounts it when toggled back. If you don't want to destroy the component, use `v-show`. | 2021-07-05T18:44:51 | 2021-07-05T18:44:51 | {} | MEMBER |
vuejs | core | 874,347,785 | 2,195 | yyx990803 | Did some major refactoring in dabfeaf and 464bd59:
- Use class-based implementation for memory-efficiency (also removed the options object, `detached` is now simply a constructor argument)
- ~~`effectScope()`~~ -> `new EffectScope(detached?)`
- ~~`scope.extend`~~ -> `scope.run()`
- The scope itself now ex... | 2021-07-05T22:08:02 | 2021-07-06T01:21:51 | {
"+1": 17,
"heart": 11,
"rocket": 5
} | MEMBER |
vuejs | core | 875,172,193 | 4,017 | yyx990803 | I rebase 3.2 branch on top of latest `master` which seems to cause some unintentional conflicts... could you please rebase your branch? | 2021-07-07T00:25:56 | 2021-07-07T00:25:56 | {} | MEMBER |
vuejs | core | 875,430,362 | 3,930 | xsdream | @qmhc 我刚刚解决了这个问题，我修改了两个地方。1.rollup.config 中增加 resolve: { dedupe: ['vue'] } （这个是从vite，尤大回复别人的一个问题） 2.把vue从dependencies 改为 devDependencies 。不知道是哪个起作用了，但是确实解决了 | 2021-07-07T09:06:45 | 2021-07-07T09:06:45 | {
"+1": 3
} | NONE |
vuejs | core | 872,439,075 | 4,046 | yyx990803 | @dependabot ignore this dependency | 2021-07-01T17:52:34 | 2021-07-01T17:52:34 | {} | MEMBER |
vuejs | core | 872,773,052 | 4,052 | zhangyuang | maybe it's caused by rollup
3.1.3
3.1.2
| 2021-07-02T07:09:07 | 2021-07-02T07:09:21 | {} | CONTRIBUTOR |
vuejs | core | 873,359,444 | 2,195 | 0x009922 | It would be great feature! When developing various reactive functionality, every now and then I came across the fact that scopes are tied strictly to the components' lifecycle, which is rather a special case, and this RFC seems to be an integral part of the entire vue reactivity API.
Btw, I don't like "Forward retur... | 2021-07-03T07:03:42 | 2021-07-03T07:03:42 | {} | NONE |
vuejs | core | 873,574,035 | 4,060 | LinusBorg | you need a `deep: true` watcher, because the value of `$attrs` doesn't change - it's the same object - only a property on that object changes | 2021-07-04T11:52:34 | 2021-07-04T11:52:34 | {} | MEMBER |
vuejs | core | 874,037,495 | 4,061 | attackam | The first entry is OK, and V-IF triggers twice | 2021-07-05T11:25:25 | 2021-07-05T11:25:25 | {} | NONE |
vuejs | core | 874,827,469 | 4,065 | yyx990803 | I have something planned that may address this problem. Automating v-for blocks into components has a different set of trade-offs (e.g. what if the list is largely static and should be optimized for initial render speed?) so it's more complicated than that. | 2021-07-06T14:48:42 | 2021-07-06T14:48:42 | {
"heart": 5
} | MEMBER |
vuejs | core | 875,017,094 | 4,074 | 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-07-06T19:15:06 | 2021-07-06T19:15:06 | {} | CONTRIBUTOR |
vuejs | core | 875,333,128 | 3,930 | xsdream | @qmhc | 2021-07-07T06:45:55 | 2021-07-07T06:45:55 | {} | NONE |
vuejs | core | 875,408,396 | 3,930 | qmhc | @xsdream 现在解决办法就是不用 link 协议，如果不方便发布到 npm 的你可以自己部署一个本地的包管理平台来进行发布与安装。 | 2021-07-07T08:36:44 | 2021-07-07T08:36:44 | {} | NONE |
vuejs | core | 872,497,011 | 3,971 | neal2018 | > Thanks for the PR - this is addressed in #4019 which also bumps puppeteer.
Hey, thanks for the respond.
I am just wondering how to get the PR merged instead of being shadowed by another later PR? Do I need to directly notify someone to review? I can not find any relevant information in the [contribution guide](ht... | 2021-07-01T19:29:56 | 2021-07-01T19:29:56 | {} | NONE |
vuejs | core | 872,542,249 | 2,195 | antfu | @basvanmeurs I have resolved the conflict.
> getActiveEffectScope
I have add the new API `getEffectScope` to the RFC. Will implement it later
> warning should be thrown when an effect is created outside of any effectScope
There are may cases we could have effect outside of an effectScope, for example, modul... | 2021-07-01T20:51:50 | 2021-07-01T20:51:50 | {} | MEMBER |
vuejs | core | 872,742,269 | 3,930 | qmhc | 这个问题在最新的 3.1.3 仍然存在，我是否应该开启一个新的 issue 来追踪这个问题？ | 2021-07-02T06:07:40 | 2021-07-02T06:07:40 | {} | NONE |
vuejs | core | 873,943,139 | 1,991 | mehdinourollah | 
I have to save my component ( forms) to store and it gives me this | 2021-07-05T09:07:28 | 2021-07-05T09:07:28 | {
"+1": 1
} | NONE |
vuejs | core | 874,822,454 | 4,068 | yyx990803 | Please use https://github.com/vuejs/rfcs for ideas like this. | 2021-07-06T14:42:42 | 2021-07-06T14:42:42 | {} | MEMBER |
vuejs | core | 875,143,080 | 4,065 | robertmoura | @yyx990803 sounds great. Makes sense, thanks for the update. | 2021-07-06T23:13:15 | 2021-07-06T23:13:15 | {} | NONE |
vuejs | core | 872,395,889 | 4,037 | posva | Thanks, I added a repro without the router at #4023 | 2021-07-01T16:42:16 | 2021-07-01T16:42:16 | {
"+1": 1
} | MEMBER |
vuejs | core | 872,750,487 | 4,052 | bodograumann | I think this only affects vue-cli-4. I have upgraded to vue-3.1.3 in the context of vue-cli-5.beta successfully. | 2021-07-02T06:25:03 | 2021-07-02T06:25:03 | {} | NONE |
vuejs | core | 872,933,261 | 4,033 | FabianSchwartau |
Thanks a lot for your elaboration and I can (have to?) accept when you say that you cannot do much about this. I'm completely new to Vue and JS, so I don't understand a lot of things.
I know this is not a forum to answer usage-questions, but I would appreciate a small explanation why a watch is such expensive. I had... | 2021-07-02T11:38:23 | 2021-07-02T11:38:23 | {} | NONE |
vuejs | core | 874,775,953 | 3,992 | DV8FromTheWorld | Bump | 2021-07-06T13:48:11 | 2021-07-06T13:48:11 | {} | CONTRIBUTOR |
vuejs | core | 874,830,825 | 4,071 | DV8FromTheWorld | To be clear, this issue is not opened with the hope that something will be fixed. It is opened to help explain this functionality problem for other users that are upgrading. | 2021-07-06T14:52:48 | 2021-07-06T14:58:53 | {} | CONTRIBUTOR |
vuejs | core | 875,214,269 | 4,068 | danelowe | If anyone comes across this wanting to do something similar, I created a quick and dirty vite plugin to be placed after the vue plugin. It modifies the SFC code to load the `<style critical>` CSS into the ssrContext, which can then be retrieved and injected into the html after `renderToString`
```
function performa... | 2021-07-07T02:10:09 | 2021-07-07T02:10:44 | {} | NONE |
vuejs | core | 875,331,891 | 3,930 | xsdream | 我遇到了相同的问题，请问你解决了吗 | 2021-07-07T06:43:34 | 2021-07-07T06:43:34 | {} | NONE |
vuejs | core | 872,264,721 | 4,036 | LinusBorg | No, it can't be avoided, and is no workaround - this is how slots work. In this specific case, you can make it a tad more succinct as `Child` only has one default slot:
```html
<script setup>
import Child from './Child.vue'
</script>
<template>
<Child v-slot="{ value }">
<slot name="option" :value="val... | 2021-07-01T13:50:50 | 2021-07-01T13:54:59 | {} | MEMBER |
vuejs | core | 873,632,998 | 4,060 | posva | I would say this is an improvement over Vue 2 | 2021-07-04T17:51:08 | 2021-07-04T17:51:08 | {} | MEMBER |
vuejs | core | 873,870,393 | 4,061 | LinusBorg | The link is broken | 2021-07-05T07:22:03 | 2021-07-05T07:22:03 | {} | MEMBER |
vuejs | core | 872,440,890 | 3,983 | yyx990803 | `preinstall` should also cover other possible package managers like Yarn 2 or pnpm. Relying on `.npmrc` may not cover those cases. | 2021-07-01T17:55:53 | 2021-07-01T17:55:53 | {} | MEMBER |
vuejs | core | 872,816,663 | 3,183 | jods4 | This impacts types, which you can work-around by using `import type`; and const enums, which you can't work around in a practical way (both `import` and `import type` create errors, in different places).
One solution to this problem could be to check what is actually used by the template and not export identifiers t... | 2021-07-02T08:24:09 | 2021-07-02T08:24:09 | {} | CONTRIBUTOR |
vuejs | core | 872,841,453 | 4,052 | czl0325 | 学习了！！！感谢！！！！ | 2021-07-02T09:03:30 | 2021-07-02T09:03:30 | {} | NONE |
vuejs | core | 873,944,700 | 2,027 | mehdinourollah | 
Even in the store when I save my current form ( vue component as form) it gives me this...And in the production it removes it so I can't go further | 2021-07-05T09:09:14 | 2021-07-05T09:09:14 | {
"+1": 1
} | NONE |
vuejs | core | 874,277,851 | 4,066 | yyx990803 | Thanks for the PR - but I think it's better to avoid walking identifiers in type AST altogether: 6fad2093 | 2021-07-05T18:42:32 | 2021-07-05T18:42:32 | {} | MEMBER |
vuejs | core | 874,673,703 | 3,258 | IS-Kuan | Just want to know the progression of review on this PR? Waiting for this feature for months, currently still do this in setup() manually. | 2021-07-06T11:15:28 | 2021-07-06T11:15:28 | {} | NONE |
vuejs | core | 875,456,810 | 3,993 | shadoWalker89 | Using the return value of a function in v-model used to work in vue 2.
I encountered this problem after upgrading my app to vue 3 | 2021-07-07T09:43:07 | 2021-07-07T09:43:07 | {} | NONE |
vuejs | core | 726,914,887 | 2,603 | jods4 | While adding Suspense warnings, for as long that #2215 isn't fixed is it possible to also add a warning when a `Suspense` catches a nested async setup but doesn't recede to pending. I mentioned it in the comments of that other issue, the code that needs a warning is here:
https://github.com/vuejs/vue-next/blob/0227b... | 2020-11-13T17:49:33 | 2020-11-13T17:49:33 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 726,975,658 | 1,766 | vhoyer | Should we add this to the docs? I think the [Custom Events](https://github.com/vuejs/docs-next/blob/master/src/guide/component-custom-events.md) page should be the best location for this, right? (I'm willing to write it :eyes:) | 2020-11-13T19:00:53 | 2020-11-13T19:00:53 | {} | NONE |
vuejs | core | 727,654,136 | 2,608 | jakedohm | Not possible in this case, and either way this is still a bug. | 2020-11-15T23:11:57 | 2020-11-15T23:11:57 | {} | NONE |
vuejs | core | 727,717,421 | 2,515 | sajuthankathurai | This issue is just mentioned in #2513 , But is there a workaround to fix this issue? | 2020-11-16T03:44:55 | 2020-11-16T03:44:55 | {} | NONE |
vuejs | core | 727,767,485 | 2,617 | 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-16T06:32:42 | 2020-11-16T06:32:42 | {} | NONE |
vuejs | core | 729,283,307 | 2,626 | arpowers | > Note - Do not use Async components for routes. Async components can still be used inside route components but route component themselves are just dynamic imports.
Ah! Didn't see this. Thanks you @posva . I'd suggest a warning log or similar for this edge case.
In any case, there is a typing bug in Vue Core a... | 2020-11-17T23:50:07 | 2020-11-17T23:52:44 | {} | NONE |
vuejs | core | 729,455,431 | 2,622 | dependabot-preview[bot] | Superseded by #2630. | 2020-11-18T06:13:03 | 2020-11-18T06:13:03 | {} | CONTRIBUTOR |
vuejs | core | 730,879,187 | 2,644 | edison1105 | This will be a awesome feature.
I opened a rfc: https://github.com/vuejs/rfcs/issues/237 | 2020-11-20T06:20:11 | 2020-11-20T06:20:11 | {
"+1": 1
} | MEMBER |
vuejs | core | 731,010,418 | 2,644 | posva | This is something to be implemented as a babel transform or similar like https://github.com/nuxt/components
Note: open issues in English so everybody can participate | 2020-11-20T08:06:00 | 2020-11-20T08:06:00 | {} | MEMBER |
vuejs | core | 726,271,540 | 2,598 | jods4 | I agree with you, it's strange that `.number` returns a string, sometimes, and I'd also prefer NaN.
_But_ that would be massively breaking for v2 users, much more so than just being more strict at parsing bogus inputs.
Fun fact: `v-model` implicitly use `.number` if your input is of `type="number"`. Given that this... | 2020-11-12T18:53:51 | 2020-11-12T22:17:44 | {} | CONTRIBUTOR |
vuejs | core | 726,567,366 | 2,600 | luwuer | > Because you have two instances of vue.
Yes, if memory serves it doesn't exist in vue2, so it's maybe a bug about compiler.
In the example above, the "app" directory build rely on "../test-componnet/node_modules" directory. It's mean that import-on-demand irrealizable. | 2020-11-13T07:11:09 | 2020-11-13T07:22:34 | {} | CONTRIBUTOR |
vuejs | core | 726,850,778 | 2,603 | posva | You have to use Suspense on the parent (App.vue) of hello world.
There use to be a warning for that, It's weird it's gone | 2020-11-13T16:09:37 | 2020-11-13T16:09:37 | {} | MEMBER |
vuejs | core | 728,715,050 | 2,622 | dependabot-preview[bot] | One of your CI runs failed on this pull request, so Dependabot won't merge it.
- [ci/circleci: test](https://circleci.com/gh/vuejs/vue-next/10853?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link)
Dependabot will still automatically merge this pull request if you amend it and your tes... | 2020-11-17T06:24:19 | 2020-11-17T06:24:19 | {} | CONTRIBUTOR |
vuejs | core | 729,515,183 | 2,625 | yangmingshan | As I said I'm using `@vue/reactivity` to building my own `watch`, it's just like `watch` in Vue but without Vue special runtime binding. In [this commit](https://github.com/vuejs/vue-next/commit/390589ec6d977675c5cef2807fbf3e930a25eef0#diff-59e3ee98b310f26c42283eaed3c0d4b53eee884d097d9fa89b7e1b546453b411) Evan use `_sh... | 2020-11-18T08:17:18 | 2020-11-18T08:19:07 | {} | CONTRIBUTOR |
vuejs | core | 729,868,920 | 2,634 | posva | Your Tabs component is empty. If you provide a boiled down repro we can take a look
---
Remember to use the [forum](http://forum.vuejs.org/) or the [Discord chat](https://vue-land.js.org/) to ask questions! | 2020-11-18T18:24:38 | 2020-11-18T18:24:38 | {} | MEMBER |
vuejs | core | 729,928,514 | 2,634 | camwhite | sorry @posva I've updated with a working link. although, it seems you must refresh the example once for it to display. | 2020-11-18T20:16:48 | 2020-11-18T20:18:12 | {} | NONE |
vuejs | core | 730,055,917 | 2,605 | luwuer | I create a PR to assert if expression is a function by wraping it into a IIFE when the expression is a Instance member, but i think it's not a recommendable way, so you can just ignore the PR above. | 2020-11-19T01:05:22 | 2020-11-19T01:05:22 | {} | CONTRIBUTOR |
vuejs | core | 730,104,517 | 2,636 | luwuer | I'd rather say that `<p> test </p>` is expected, because the text (`test`) exists in a new line:
```html
<HelloWorld msg="Hello Vue 3 in CodeSandbox!">
<template #test>
test
</template>
test
</HelloWorld>
```
To meet your expectations, you can remove newline like below:
```html
<H... | 2020-11-19T03:24:56 | 2020-11-19T03:30:55 | {} | CONTRIBUTOR |
vuejs | core | 730,313,955 | 2,220 | boussadjra | i found the solution in stackoverflow https://stackoverflow.com/a/64189046/8172857 but i forgot to add it here | 2020-11-19T11:33:43 | 2020-11-19T11:33:43 | {} | NONE |
vuejs | core | 730,400,064 | 2,641 | posva | Don't open issues without reproduction. Thanks. You can use https://github.com/vitejs/vite. I imagine you read the existing RFC as well: https://github.com/vuejs/rfcs/blob/scoped-styles-changes/active-rfcs/0023-scoped-styles-changes.md | 2020-11-19T14:09:28 | 2020-11-19T14:09:28 | {
"+1": 1
} | MEMBER |
vuejs | core | 726,454,933 | 2,597 | luwuer | May i ask is there any information of reviewing time? @LinusBorg @posva
I need you help to verify if I've handled both issues correctly. | 2020-11-13T01:49:24 | 2020-11-13T01:49:24 | {} | CONTRIBUTOR |
vuejs | core | 727,208,275 | 2,345 | jods4 | Looked at your code and there's another thing that you could do on top of my previous comment.
`trigger` currently snapshots (i.e. copies into an array) dependencies, so it's not impacted by their unlikely mutation.
With some additional cleverness the copy is not required.
When a trigger effect runs, other effec... | 2020-11-14T13:35:44 | 2020-11-14T13:35:44 | {
"+1": 3,
"heart": 1
} | CONTRIBUTOR |
vuejs | core | 729,281,784 | 2,626 | posva | Note you shouldn't use `defineAsyncComponent` with lazy routes: https://next.router.vuejs.org/guide/advanced/lazy-loading.html | 2020-11-17T23:46:09 | 2020-11-17T23:46:09 | {} | MEMBER |
vuejs | core | 729,947,124 | 2,627 | posva | I tried on a fresh project and there are no TS errors.
---
Remember we have a [forum](http://forum.vuejs.org/) and a [Discord chat](https://vue-land.js.org/) to ask questions! | 2020-11-18T20:53:33 | 2020-11-18T20:53:33 | {} | MEMBER |
vuejs | core | 731,015,703 | 2,643 | posva | I tried on a fiddle and it works. Please, do provide real reproductions when opening bug reports: https://new-issue.vuejs.org/?repo=vuejs/vue#why-repro | 2020-11-20T08:13:12 | 2020-11-20T08:13:12 | {} | MEMBER |
vuejs | core | 728,714,483 | 2,622 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.17 KB (0%) |
| runtime-dom.global.prod.js | 26.45 KB (0%) |
| size-check.global.prod.js | 15.95 KB (0%) | | 2020-11-17T06:22:59 | 2020-11-17T06:22:59 | {} | NONE |
vuejs | core | 728,750,321 | 2,620 | posva | It's probably not compatible with Vue 3 yet, yeah.
https://new-issue.vuejs.org/?repo=vuejs/vue-next#why-repro | 2020-11-17T07:49:09 | 2020-11-17T07:49:09 | {} | MEMBER |
vuejs | core | 726,464,660 | 2,596 | nxl3477 | Thank you, you are right, I tried to filter vue in the packaging, and introduced in index.html by cdn to solve this problem
vue.config.js
```
externals: {
vue: 'Vue',
},
```
index.html
```
<script src="https://unpkg.com/vue@next"></script>
```
| 2020-11-13T02:19:00 | 2020-11-13T02:19:00 | {} | NONE |
vuejs | core | 726,851,883 | 2,602 | posva | This was added at https://github.com/vuejs/vue-next/pull/1858 | 2020-11-13T16:11:36 | 2020-11-13T16:11:36 | {} | MEMBER |
vuejs | core | 730,971,046 | 2,647 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.41 KB (0%) |
| runtime-dom.global.prod.js | 26.5 KB (0%) |
| size-check.global.prod.js | 16.08 KB (0%) | | 2020-11-20T07:44:42 | 2020-11-20T07:44:42 | {} | NONE |
vuejs | core | 727,092,757 | 2,606 | posva | Please open this on the docs-next repository | 2020-11-14T00:03:21 | 2020-11-14T00:03:21 | {} | MEMBER |
vuejs | core | 727,200,679 | 2,345 | jods4 | @basvanmeurs Thank you very much for tackling this. ❤️
Reactive perf is at the heart of everything in Vue. Even small improvements will compound to larger benefits in big, intensive apps.
Like you, I noticed there was room for improvement in the reactivity package and wanted to create a PR. Couldn't manage to actu... | 2020-11-14T12:28:46 | 2020-11-14T12:28:46 | {
"+1": 4
} | CONTRIBUTOR |
vuejs | core | 727,262,922 | 2,598 | jods4 | @LinusBorg 100% agree with that.
It's only if you support them in 2-way scenarios that they bring something new to the table. | 2020-11-14T20:44:38 | 2020-11-14T20:44:38 | {} | CONTRIBUTOR |
vuejs | core | 727,559,873 | 2,612 | posva | Use a `watch` to explicitly define its dependencies, it's even clearer and shorter than the change you proposed with `watchEffect` | 2020-11-15T12:09:03 | 2020-11-15T12:09:03 | {} | MEMBER |
vuejs | core | 727,932,182 | 2,345 | jods4 | > Your algorithm is simple, but we have to take into account that effects are triggered recursively. So during the run of an effect, other effects will be ran as well, and the run id is incremented and decremented multiple times before the cleanup takes place.
To clarify: run id is a monotone sequence, always increa... | 2020-11-16T11:54:31 | 2020-11-16T11:54:31 | {
"laugh": 3
} | CONTRIBUTOR |
vuejs | core | 729,949,374 | 2,624 | posva | Thanks but see https://github.com/vuejs/vue-next/issues/2623#issuecomment-729949228 | 2020-11-18T20:58:00 | 2020-11-18T20:58:00 | {} | MEMBER |
vuejs | core | 729,950,988 | 2,626 | posva | the warning would be on the router | 2020-11-18T21:01:25 | 2020-11-18T21:01:25 | {} | MEMBER |
vuejs | core | 730,241,420 | 2,608 | posva | > This seems like it's going to cause lots of problems for Vue 2 users who are migrating... in Vue 2 the behavior was to just ignore the script/style not to fail the template compilation.
It was giving a warning already, which shouldn't be ignored
If the style tag is ignored, it should be removed altogether inste... | 2020-11-19T09:22:10 | 2020-11-19T09:22:10 | {} | MEMBER |
vuejs | core | 730,970,808 | 2,646 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.41 KB (0%) |
| runtime-dom.global.prod.js | 26.5 KB (0%) |
| size-check.global.prod.js | 16.08 KB (0%) | | 2020-11-20T07:44:08 | 2020-11-20T07:44:08 | {} | NONE |
vuejs | core | 727,857,792 | 2,615 | Alanscut | Hi @privatenumber , as a workaround, use `setup` maybe solve this issue?
https://codepen.io/alanscut/pen/rNLRWqB?editors=0010 | 2020-11-16T09:34:24 | 2020-11-16T09:34:24 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 728,168,905 | 2,615 | privatenumber | I'm aware but thanks for reminding me. I meant to mention that as a reason for why it's expected to work. | 2020-11-16T16:23:19 | 2020-11-16T16:23:19 | {} | CONTRIBUTOR |
vuejs | core | 729,456,375 | 2,630 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.39 KB (0%) |
| runtime-dom.global.prod.js | 26.5 KB (0%) |
| size-check.global.prod.js | 16.08 KB (0%) | | 2020-11-18T06:15:23 | 2020-11-18T06:15:23 | {} | NONE |
vuejs | core | 729,917,609 | 2,635 | posva | This is expected behavior but it's unrelated to Vue, it happens in vanilla JS as well | 2020-11-18T19:55:17 | 2020-11-18T19:55:17 | {} | MEMBER |
vuejs | core | 730,154,917 | 2,637 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.41 KB (0%) |
| runtime-dom.global.prod.js | 26.5 KB (0%) |
| size-check.global.prod.js | 16.08 KB (0%) | | 2020-11-19T06:16:07 | 2020-11-19T06:16:07 | {} | NONE |
vuejs | core | 730,369,562 | 2,610 | posva | Please open a new issue with a boiled down reproduction using the jsfiddle link provided on the issue helper and proper reproduction steps. Remember to use the [forum](http://forum.vuejs.org/) or the [Discord chat](https://vue-land.js.org/) to ask questions! | 2020-11-19T13:19:38 | 2020-11-19T13:19:38 | {} | MEMBER |
vuejs | core | 730,699,408 | 2,642 | dnlsndr | This has been a nuisance for me, since PCSS 8 came out. It would be really nice to have v8 running as default in vue, so one doesn't have to always take care which old PCSS plugin versions to install. Would be great to have this! | 2020-11-19T23:21:44 | 2020-11-20T08:14:24 | {} | NONE |
vuejs | core | 726,329,641 | 2,599 | skirtles-code | I think you have a typo in your test case. It should be `emits`, not `emit`. | 2020-11-12T20:40:00 | 2020-11-12T20:40:00 | {
"+1": 2
} | CONTRIBUTOR |
vuejs | core | 726,928,380 | 1,766 | MiniGod | I find this a bit confusing, and at least unclear in the docs.
Without the `emits` option, Vue implicitly accepts `update:modelValue` without warning, but as soon as I want to emit other events, I have to specify `update:modelValue` explicitly.
Wouldn't it make sense if for every prop, `update:${prop}` was implic... | 2020-11-13T18:07:56 | 2020-11-13T18:07:56 | {} | NONE |
vuejs | core | 729,943,868 | 2,626 | posva | Closing as using the proper import solves the issue. A PR for the warning with a test would be appreciated! 🙂 | 2020-11-18T20:47:03 | 2020-11-18T20:47:03 | {} | MEMBER |
vuejs | core | 726,752,950 | 2,598 | jods4 | I wasn't aware Vue 2 only had one-way filters. Yeah, it's just functions then.
Interesting it never had two-way filters as that's a nice useful primitive that everyone else (who does 2-way bindings) has: e.g. WPF (binding converters), Angular (pipes), Aurelia (value converters).
ref factories is ok-ish. Although if... | 2020-11-13T13:03:17 | 2020-11-13T13:03:17 | {} | CONTRIBUTOR |
vuejs | core | 727,237,959 | 2,607 | LinusBorg | There could be many things that went wrong in your implementation. But we won't debug a complete front- and backend application for you.
Bug reports require a *minimal* runnable reproduction, a complete app repository is *not* minmal.
I suggest to visit chat.vuejs.org and ask the friendly folk there for help in ... | 2020-11-14T17:19:48 | 2020-11-14T17:19:48 | {} | MEMBER |
vuejs | core | 728,973,424 | 2,621 | edison1105 | > ```js
> Object.prototype.hasOwnProperty.call(obj, 'a')
> ```
This will not be tracked and I am not sure that this PR is the best solution. | 2020-11-17T14:42:46 | 2020-11-17T14:46:42 | {} | MEMBER |
vuejs | core | 729,977,777 | 2,497 | posva | @fimion A better warning should indeed help migration! Feel free to give it a try | 2020-11-18T21:49:25 | 2020-11-18T21:49:25 | {} | MEMBER |
vuejs | core | 731,018,509 | 2,648 | posva | Can you provide a repro using one of the templates at https://new-issue.vuejs.org/?repo=vuejs/vue-next | 2020-11-20T08:19:43 | 2020-11-20T08:19:43 | {} | MEMBER |
vuejs | core | 731,019,577 | 2,642 | posva | Do not comment +1 on issues, use the reactions.
Locking to prevent spam since there isn't anything left to discuss but people can still track the progress of the issue 🙂 | 2020-11-20T08:22:06 | 2020-11-20T08:22:06 | {} | MEMBER |
vuejs | core | 726,522,387 | 2,600 | edison1105 | here is the bug.
The type of `v-for` VNode is not equal to `Fragment`. The switch went to `default`.
![image](https://user-images.githubusercontent.com/3705199/99032237-00a3ae00-25b4-11eb-8111-34d42af1... | 2020-11-13T05:23:59 | 2020-11-13T05:27:53 | {} | MEMBER |
vuejs | core | 726,560,597 | 2,600 | KaelWD | Because you have two instances of vue. | 2020-11-13T06:53:36 | 2020-11-13T06:53:36 | {
"+1": 4
} | CONTRIBUTOR |
vuejs | core | 727,519,184 | 2,608 | edison1105 | I think it’s better to put `<header>` outside the `#app`.
Why put it in the `#app` if it doesn't need to be rendered by Vue? | 2020-11-15T05:42:10 | 2020-11-15T05:44:32 | {} | MEMBER |
vuejs | core | 729,066,028 | 1,414 | ip7e | I'm still getting the error when using custom webpack build
**Failed to resolve component: xyz**
Versions:
```
"vue": "^3.0.2",
"vue-loader": "^16.0.0-rc.1"
```
Webpack:
```
{
...
rules: [
{
test: /\.vue$/,
loader: 'vue-loader',
options: {
compilerOptions... | 2020-11-17T17:04:02 | 2020-11-17T17:38:38 | {
"+1": 1
} | NONE |
vuejs | core | 730,238,274 | 2,638 | posva | Duplicate of https://github.com/vuejs/vue-next/issues/2540
---
Please, search existing issues and pull requests before opening issues, it saves maintainers a lot of time 🙏 | 2020-11-19T09:16:59 | 2020-11-19T09:16:59 | {} | MEMBER |
vuejs | core | 730,351,854 | 2,633 | LongTengDao | https://github.com/vuejs/docs-next/issues/698
And,
1. how should `NaN` `-0` be treated?
2. I saw `v-if/v-else` is auto compiled to `key:0` `key:1` in the source. won't that cause error when the sibling is `key=0` `key=1` or other `v-if/v-else` also compiled to `key:0` `key:1`?
| 2020-11-19T12:44:32 | 2020-11-19T12:46:35 | {} | CONTRIBUTOR |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.