grainne6

grainne6

When I add background-image: url(../images/my-image.png) to phoenix.css, the image displays correctly but the console shows an error

Uncaught Error: Module build failed: ModuleParseError: Module parse failed: Unexpected character '�' (1:0)
You may need an appropriate loader to handle this file type.
(Source code omitted for this binary file)
    at handleParseError (c:\projects\Phoenix\filmhub\assets\node_modules\webpack\lib\NormalModule.js:364:19)

This also happens with a brand new project so I know it’s not a change I made.

I also tried using background-image: url(“<%= Routes.static_path(@conn, “/images/my-image.png”) %>”); but that doesn’t work at all.

I am new to phoenix so I’m not sure what else to try, what is the correct way to display background images in phoenix? Thanks

Showing Posts 1 to 10

adrianrl

adrianrl

Hi,

body {
  background-image: url('/images/my-image.png');
}

<%= %> tags only works inside eex templates.

patrickdm

patrickdm

Hello and welcome!

In the thread how-to-put-background-picture-to-phoenix-html-page you should find the answer to your question.

grainne6

grainne6 OP

Yes, I have tried this. Like I said the images shows up when I put background-image: url(‘../images/my-picture.png’) but there is an error in the developer tools console.
Is there any way to get rid of this error

grainne6

grainne6 OP

I have looked at this, the problem isn’t displaying the image, the problem is that while the image displays there is an error in the console.

patrickdm

patrickdm

sorry, you clearly reported it.

Hmm, a strange character somewhere in the background-image in the css ? maybe from a cut&paste ?

grainne6

grainne6 OP

No, I have tried several images, it doesn’t make any difference. I have tried creating a new mix project and the error appears as soon as I add a background image.

adrianrl

adrianrl

Can you share your configuration for Webpack?

grainne6

grainne6 OP

It’s just the default config file - I haven’t changed anything

const path = require('path');
const glob = require('glob');
const MiniCssExtractPlugin = require('mini-css-extract-plugin');
const UglifyJsPlugin = require('uglifyjs-webpack-plugin');
const OptimizeCSSAssetsPlugin = require('optimize-css-assets-webpack-plugin');
const CopyWebpackPlugin = require('copy-webpack-plugin');

module.exports = (env, options) => ({
  optimization: {
    minimizer: [
      new UglifyJsPlugin({ cache: true, parallel: true, sourceMap: false }),
      new OptimizeCSSAssetsPlugin({})
    ]
  },
  entry: {
      './js/app.js': ['./js/app.js'].concat(glob.sync('./vendor/**/*.js'))
  },
  output: {
    filename: 'app.js',
    path: path.resolve(__dirname, '../priv/static/js')
  },
  module: {
    rules: [
      {
        test: /\.js$/,
        exclude: /node_modules/,
        use: {
          loader: 'babel-loader'
        }
      },
      {
        test: /\.css$/,
        use: [MiniCssExtractPlugin.loader, 'css-loader']
      }
    ]
  },
  plugins: [
    new MiniCssExtractPlugin({ filename: '../css/app.css' }),
    new CopyWebpackPlugin([{ from: 'static/', to: '../' }])
  ]
});
adrianrl

adrianrl

This may be because you need url-loader to process the image. In your assets folder run:

npm i -D url-loader

Then add this line to the rules array inside your Webpack configuration:

//...
{ test: /\.(png|woff|woff2|eot|ttf|svg)$/, loader: 'url-loader?limit=100000' }
grainne6

grainne6 OP

I tried this but there is a different error now

Uncaught Error: Module build failed: ModuleBuildError: Module build failed: Error: Cannot find module 'file-loader'
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:582:15)
    at Function.Module._load (internal/modules/cjs/loader.js:508:25)
    at Module.require (internal/modules/cjs/loader.js:637:17)
    at require (c:\projects\Phoenix\filmhub\assets\node_modules\v8-compile-cache\v8-compile-cache.js:161:20)

Where Next? Top

Trending in Questions Top

katta
I having some trouble figuring out if I have set myself too strict of standards for my production server. Currently I can handle 75% of r...
New
brecabral
Documentation While reading the Scoped Routes section, I noticed that the documentation currently refers to a problem without explainin...
New
nseaSeb
Hello, I know there is an approach for handling lists that allows for optimized traversal, but I can’t recall the specific method (somet...
New
kpanic
Hi everyone, I am toying with the idea of building a “match maker” for giving personal help to people that wants to start coding. I sta...
New
velrest
So my question is quite simple and i have found no conclusive answer on forum, google or AI. Should we use :erlang.float for Integer to ...
New
asweet-confluent
I recently noticed that Elixir’s Logger defaults its primary log level to :debug when no :logger, :level application configuration is pre...
New
apz
I’m new to elixir and just tried to install the elixirLS extension for VScode(ium) and it is throwing some errors that I would like help ...
New

Other Trending Topics Top

woylie
LetMe 3.0.4 has been released. Changed Log the policy module and the check module in the message of the warning for a rule that does n...
New
GenericJam
Edit: 2026 May 15 - This post is archived. Mob is alive!! Main docs: mob v0.7.11 — Documentation A bit of explanation for the slightly c...
New
JesseHerrick
Hey, I’m Jesse and I’m the main contributor behind Dexter, a full-featured, lightning-fast Elixir LSP optimized for large codebases. It s...
New
mudasobwa
I am happy to introduce the very α version of the new programming language compiled to BEAM. Welcome Cure. It has literally three kille...
New
garrison
Hobbes is a low-level distributed database for the Elixir programming language. Hobbes provides a simple, safe, and scalable storage lay...
New
mhanberg
Hi everyone! The first release candidate for the Expert language server project is now available! We’ve published a press release detai...
New

We're in Beta

About us Mission Statement

Options

Thread Display Mode




Thread Preview

Skip Thread Previews