You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: active-rfcs/0040-script-setup.md
+4-4Lines changed: 4 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -444,11 +444,11 @@ Vue 3 SFCs automatically infers the component's name from the component's **file
444
444
- DevTools inspection
445
445
- Recursive self-reference. E.g. a file named `FooBar.vue` can refer to itself as `<FooBar/>` in its template.
446
446
447
-
This has lower priority than explicity registered/imported components. If you have a named import that conflicts with the component's inferred name, you can alias it:
447
+
This has lower priority than explicity registered/imported components. If you have a named import that conflicts with the component's inferred name, you can alias it:
448
448
449
-
```js
450
-
import { FooBarasFooBarChild } from'./components'
451
-
```
449
+
```js
450
+
import { FooBarasFooBarChild } from'./components'
451
+
```
452
452
453
453
In most cases, explicit `name` declaration is not needed. The only cases where you do need it is when you need the `name` for `<keep-alive>` inclusion / exclusion or direct inspection of the component's options.
0 commit comments