How do I describe the relative path when I write the common processing of multiple pages in a website?

Suppose you create a service with the following URL:
https://example.com/hoge-service/←This is the top screen
https://example.com/hoge-service/favorite
https://example.com/hoge-service/user/123456User Page
https://example.com/hoge-service/js/common.js
https://example.com/hoge-service/image/banner.png

https://example.com/hoge-service/ is the front page and never goes above it
https://example.com/hoge-service-help←This is not available

At this time, how do I create a relative path to any URL, such as /hoge-service/js/common.js, no matter which page I am viewing?

For example, <script src="./js/common.js"> is fine, but
The user page should say <script src="./../js/common.js">.
You can be careful when you write the template engine with only the script tag, but
Actually, when you call api on fetch from js, or
When accessing url (./image/banner.png) in the style sheet, or
When writing img tags in html, or
There are countless places to write paths, so it's hard to dynamically create them all on the server side.

Assume that the hoge-service portion is dynamically changed in the environment variable.
The server side is node+express+ejs, which has some freedom, but
I don't want to replace all paths in html css js dynamically when responding.