Base property of userConfig object does not prefix css imports

[rudyflores]

I am having this issue when deploying my project into GitHub pages, I am currently setting my object base value to the name of my repo for example /my-project/ and have an import in the head property that links to a css stylesheet. but when running vuepress build my-project it seems to not prefix the css imports from /assets/mystyles.css to /my-project/assets/mystyles.css. Any idea if this may be a bug since I am currently using vuepress 2.0.0-beta.36?

[Mister-Hope]

Minimal reproduction repo required when you are taling about bugs, or at least please describe how you are importing that css. Do not start dicussion like this with little details.

And if you are importing that useing head option ,please note that we are keeping them as is.

As an example, it's resonable for a person who want access to /favicon.ico when he is delopying some thing to a sub folder called /docs/

[rudyflores]

For my default config I am importing CSS inside the head property for example:

base: `/github-user/my-repo/`

...

head: [
      [
                  "link",
                  {
                      rel: "stylesheet",
                      href: "/assets/css/custom.css"
                  }
      ]
]

but it seems to not append to the start of the href link the repo base name upon deployment

[rudyflores]

I also wanted to mention this is a typescript based config file and not a javascript based file

[Mister-Hope]

And if you are importing that useing head option ,please note that we are keeping them as is.

As an example, it's resonable for a person who want access to /favicon.ico when he is delopying some thing to a sub folder called /docs/

Google translate:

如果您使用 head 选项导入，请注意我们将它们保持原样。

例如，对于将某些内容部署到名为 /docs/ 的子文件夹人来说，想要访问 /favicon.ico 这是合理的。

Read it PLZ

[rudyflores]

I see that makes sense, so would you recommend to either use a relative path instead for adding these css files instead since an absolute path seems to not be the right direction?

[Mister-Hope]

??? How can a relative path correct when you are in different pages, e.g: /a.html and /a/b.html?

[rudyflores]

I think im getting this mixed up from what you're saying, I understood relative paths will become prefixed since the documentation you lined seems to suggest using relative paths over absolute paths. In my case I need the absolute paths because I have a base property set to my gh-pages repo. if I wanted to use the $withBase variable with my project to prefix myself, how can I add my css links to my html file since the head is generated through the conifg?

[Mister-Hope]

Nope, the docs I provide is just telling you we are actually not pending prefix for absolute links in markdown files either.

Forget it if it's confusing you, I am just curious about the thought of pending base prefix.

We are keeping them as is, which means the url you fill in is the final url, so you should make them valid. So you should use /base/link/to-your-css if you want that url be correct. And as describe above, we will not adding any options to special deal with them (e.g.: adding base as prefix) , because an option leading to total different behavior would confuse a lot of users.

[Mister-Hope]

Or in another word, since we donot mention in the docs that absolute link in proejct will be pended with base as prefix, you are supposed to not have confusion like this.