Referencing any files from CSS (even placed in /public) appear to get packaged and then referenced incorrectly (using /static/css as the root).
I have tried using: /public/main.css as well as just /src/main.css and referencing an image in /public or even in /src but both end up improperly referenced. So having a line like:
background-image: url("/images/example.jpg");
No matter what was used as the image path, %PUBLIC_URL%/images/example.jpg or ./images/example.jpg, etc. the actual referenced file ends up being something like /static/css/static/media/example.907d6572.jpg because the path is relative to the CSS file so static/media/example.907d6572.jpg gets appended to /static/css where the stylesheet lives.
Environment
Using with Gitlab CI to deploy to Gitlab Pages
node -v: v18.17.
npm -v: 10.1.0
yarn --version (if you use Yarn): n/a
npm ls create-elm-app -g (if you haven’t ejected): create-elm-app@5.22.0
Is this a bug report?
Referencing any files from CSS (even placed in
/public
) appear to get packaged and then referenced incorrectly (using/static/css
as the root).I have tried using:
/public/main.css
as well as just/src/main.css
and referencing an image in/public
or even in/src
but both end up improperly referenced. So having a line like:No matter what was used as the image path,
%PUBLIC_URL%/images/example.jpg
or./images/example.jpg
, etc. the actual referenced file ends up being something like/static/css/static/media/example.907d6572.jpg
because the path is relative to the CSS file sostatic/media/example.907d6572.jpg
gets appended to/static/css
where the stylesheet lives.Environment
Using with Gitlab CI to deploy to Gitlab Pages
node -v
: v18.17.npm -v
: 10.1.0yarn --version
(if you use Yarn): n/anpm ls create-elm-app -g
(if you haven’t ejected):create-elm-app@5.22.0
Then, specify: