We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
1.0.0-alpha.17
Use a custom theme by creating a .vuepress/theme folder Repo: https://github.com/Gostwow/test-vuepress-custom-theme Deploy url: https://hungry-wilson-87db4e.netlify.com/
.vuepress/theme
A single stylesheet included in the html head
2 extra stylesheets are included, one is empty and another one includes only .icon.outbound{color:#aaa;display:inline-block}
.icon.outbound{color:#aaa;display:inline-block}
As for the JS assets, there is this and also the 404 from default theme seems to be prefetched...
I've included the dist folder in the repo: https://github.com/Gostwow/test-vuepress-custom-theme/tree/master/dist
Arch
v10.12
local
yarn
The text was updated successfully, but these errors were encountered:
Doesn't seem to be an issue after upgrading to [email protected]
[email protected]
Sorry, something went wrong.
No branches or pull requests
Bug report
Version
1.0.0-alpha.17
Steps to reproduce
Use a custom theme by creating a
.vuepress/theme
folderRepo: https://github.com/Gostwow/test-vuepress-custom-theme
Deploy url: https://hungry-wilson-87db4e.netlify.com/
What is expected?
A single stylesheet included in the html head
What is actually happening?
2 extra stylesheets are included, one is empty and another one includes only
.icon.outbound{color:#aaa;display:inline-block}
As for the JS assets, there is this and also the 404 from default theme seems to be prefetched...
I've included the dist folder in the repo: https://github.com/Gostwow/test-vuepress-custom-theme/tree/master/dist
Other relevant information
Arch
v10.12
local
yarn
The text was updated successfully, but these errors were encountered: