Profile Image

[troygolden]

For some reason, i cant get the profile image to show.

[abonmassip]

I'm having the same problem, and not only the profile image but all images are not showing. The weird thing is it was working before, I could see the default images, but as soon as I tried adding my profile image all the images broke. And now even if I delete everything and start again step by step using the guide it doesn't work.

if I right click the missing image and select "View Image" I get this page

[abonmassip]

I attach also what I get on the terminal after running npm start

I don't understand why suddenly it doesn't work anymore. I would really appreciate some help

[alexmonteil]

I'm having the same issue, none of the pictures show.

Based on the activity on the repo, clearly it broke after the author updated some packages on 12/08/19.

major package updates were :

css-loader

file-loader

style-loader

bootstrap

I'm a bit busy these days, but if I have time I'll try to identify which package update broke the app and find a fix.

If someone does it earlier than that, even better !

[alexmonteil]

It is most likely the file loader package update from 4.2.0 to 5.0.2 that broke the app.

For the time being, until someone fixes it, if you need the portfolio to work right now just change the following package versions in your package.json file to the following :

"css-loader": "^3.2.0"

"file-loader": "^4.2.0"

"style-loader": "^1.0.0"

"bootstrap": "^4.3.1"

and run npm install in your terminal.

[amberchisholm]

I'm having the same issues. None of the pictures, or any of the CSS shows up. Even after following the README and installing using sudo, no dice. Also getting a ton of console errors when loaded into my browser....mostly about "Cannot find module 'node-sass'.

[amberchisholm]

Nevermind...I got it working. Needed to run this command in my terminal

sudo npm install --save-dev --unsafe-perm node-sass

[troygolden]

It works changing the package.json file versions...

[cobiwave]

@abonmassip @troygolden @amberchisholm @alexmonteil hello!

Sorry for coming late in order to solve this issue. As Alex said, I update some packages in December, so webpack started to crash because the config was not following some parameters to have working the file-loader.

{
  loader: "file-loader",
    options: {
      name: "[name].[hash].[ext]",
      outputPath: "assets",
      esModule: false // <- I needed to add this prop
    }
}

For the time being, the project is working 🙂