Behavioral change in relative publicPath in app-webpack v4

[GrishinAV]

What happened?

In Quasar 2.16 publicPath by default with vueRouterMode: 'hash' was relative (resource files in index.html were created with no / at the beginning). Now after upgrading Webpack and Quasar to 2.18 I can't set the relative path. PublicPath values: "./", "", undefined result in publicPath equal to "/".
We deploy many instances of our SPA application on relative paths with vueRouterMode: hash , but with different configs. And it makes no sense for us to build each instance with a different public path. After the update, we were forced to roll back. I think a similar problem may arise not only with us.
What is the explanation for the change in publicPath behavior? Is there any way to set a relative publicPath?
The setting does not work according to the documentation https://cli.vuejs.org/config/#publicpath

What did you expect to happen?

I want to set the relative publicPath as it was before

Reproduction URL

No

How to reproduce?

Build project

Flavour

Quasar CLI with Webpack (@quasar/cli | @quasar/app-webpack)

Areas

Quasar CLI Commands/Configuration (@quasar/cli | @quasar/app-webpack | @quasar/app-vite)

Platforms/Browsers

Chrome

Quasar info output

Relevant log output

Additional context

No response

[github-actions]

Hi @GrishinAV! 👋

It looks like you provided an invalid or unsupported reproduction URL.
Do not use any service other than Codepen, jsFiddle, StackBlitz, CodeSandbox, and GitHub.
Make sure the URL you provided is correct and reachable. You can test it by visiting it in a private tab, another device, etc.
Please edit your original post above and provide a valid reproduction URL as explained.

Without a proper reproduction, your issue will have to get closed.

Thank you for your collaboration. 👏

[yusufkandemir]

Quasar(quasar) version is not related to CLI behavior. Please clarify which version of @quasar/app-webpack you were using previously and which version you upgraded to.

The link you've sent(cli.vuejs.org/config#publicpath) is for Vue CLI, which is deprecated, and not relevant to us. So, please clarify if you are using Quasar CLI with Webpack or Vue CLI to begin with.

[GrishinAV]

I am using Quasar CLI with Webpack. In @quasar/app-webpack version 3.15.1 publicPath works correctly, but I have a problem in @quasar/app-webpack version 4.1.2

[yusufkandemir]

Here's the relevant piece of logic:

quasar/app-webpack/lib/quasar-config-file.js

Lines 61 to 79 in cc1bf89

	function formatPublicPath (publicPath) {
	if (!publicPath) {
	return '/'
	}
	if (!publicPath.endsWith('/')) {
	publicPath = `${ publicPath }/`
	}
	if (urlRegex.test(publicPath) === true) {
	return publicPath
	}
	if (!publicPath.startsWith('/')) {
	publicPath = `/${ publicPath }`
	}
	return publicPath
	}

To clearly understand you, you want to do publicPath: '' or publicPath: 'foo/', but they end up being / and /foo/ respectively. Is that right?

[GrishinAV]

I want to do publicPath "" or "./", but a get "/" and "/./".

The Quasar has very strange and unnecessary logic.

I needed to solve the problem quickly, I left Webpack and started using Vite with
extendViteConf(viteConf) {viteConf.base = ""; }
I didn't find a similar setting in webpack.