-
-
Notifications
You must be signed in to change notification settings - Fork 33.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Inconsistent Warning For Named Slot in "is" Components #10168
Comments
use The minified version is meant for production and doesn't contain warnings. This is documented. |
@LinusBorg , this may be same as issues #10152. |
@LinusBorg Thanks for pointing that out. But that isn't the fix. Thanks for pointing to the related issue @zrh122 that's exactly what I'm dealing with. |
Oh, I see. I thought the issue was about the error message not appearing in the codepen. Thanks for the correction. In that case: closed as duplicte of #10152 |
Oh, I see. I thought the issue was about the error message not appearing in the codepen. Thanks for the correction. In that case: closed as duplicte of #10152 |
Using |
you should use |
Version
2.6.10
Reproduction link
https://codepen.io/jameswee/pen/gNwZxJ?editors=1010
Steps to reproduce
In the pen provided above, you can't see the warning because there's no build step.
However if you put this through Webpack you'll see this error
<template v-slot> can only appear at the root level inside the receiving the component
What is expected?
You will see
<template v-slot> can only appear at the root level inside the receiving the component
What is actually happening?
I'm seeking explanation here as well. LOL
Additional Comments
There's an inconsistency in the old and new slot syntax.
The new syntax caused warning when used with the special
is
attribute.Both the HTML below are server rendered by a CMS and is compiled by Vue compiler.
Error message:
The old syntax works without error. 👍
Can we treat
is
attributed DOM element as vue components like how the old slot syntax works?I'd like to point out that the default slot works without errors. But ideally we should be able to use named slots here as well.
The text was updated successfully, but these errors were encountered: