-
-
Notifications
You must be signed in to change notification settings - Fork 33.7k
Cannot create property 'default' on boolean 'true'" #9863
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
Comments
default is a reserved keyword and therefore cannot be used in specific places in JS |
@posva I am not using This code fails
This does not fail
It fails when slot is inside slot Are you sure it is not a bug in vue-loader? I know that default is a keyword, not my first rodeo ... |
ah, sorry looking at the title it looked like you wanted to use default in your code. |
@posva thanks This is only happening on vue 2.6.10. |
What does the stack trace look like when you encounter that error? I am going to guess you have a boolean literal |
Here is the full stack trace. The problem occurs when i use scoped slot inside component scoped slot For example
It seems that when i have scoped slot in scoped slot the third argument of the render function which should be component or element is set to boolean
|
Hmmm, since you're not able to reproduce it in Codesandbox, that is going to make it nearly impossible for me to help. I can only guess that maybe your Please report back if you can get a minimal reproduction. |
You probably have either own code or 3rd party code that was compiled using an outdated version of |
@yyx990803 @sirlancelot @posva |
No worries, glad it's working! 🎉 |
Version
2.6.10
Reproduction link
https://codesandbox.io/s/v8r388y7y
Steps to reproduce
When i use scope slot inside scope slot i get this error. In condsandbox i could not reproduce it, but the same code i have is there
It happened when i upgraded from vue 2.6.7 -> 2.6.10
What is expected?
Not to fail
What is actually happening?
The code i have in sandbox is compiled like this
The text was updated successfully, but these errors were encountered: