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
Theme makers may not want to register global components, but still want to have a components dir in the root path of their theme. (As I did in my own theme based on vuepress@0.x)
How should this be implemented in your opinion?
In my opinion, theme makers should use @vuepress/plugin-register-components themselves to control global components registration.
So I propose to remove line 123 above, i.e path.resolve(this.themePath, 'components'), and use another @vuepress/plugin-register-components in @vuepress/theme-default.
Are you willing to work on this yourself?**
Yes if admitted
The text was updated successfully, but these errors were encountered:
Feature request
For version: 1.0.0-alpha.1
What problem does this feature solve?
All
.vue
files inthemePath/components
are registerd as global components by default:vuepress/packages/@vuepress/core/lib/prepare/AppContext.js
Lines 120 to 125 in ace3aec
Theme makers may not want to register global components, but still want to have a
components
dir in the root path of their theme. (As I did in my own theme based onvuepress@0.x
)How should this be implemented in your opinion?
In my opinion, theme makers should use
@vuepress/plugin-register-components
themselves to control global components registration.So I propose to remove line 123 above, i.e
path.resolve(this.themePath, 'components')
, and use another@vuepress/plugin-register-components
in@vuepress/theme-default
.Are you willing to work on this yourself?**
Yes if admitted
The text was updated successfully, but these errors were encountered: