Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 3 years ago

Vue.Js

Chris Paschall•440
@ChrisP1108
A solution to the Product feedback app challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


So I got everything to work during development. However, it has been a challenge with Vue.JS when it comes to deployment. It's my first time using Vue and its been a great framework, but the deployment to my github pages was a bit of a pain. The images of the user avatars won't load with the build version that is deployed to the github pages link, despite them loading just fine on the development version.

If anyone can help me getting the images to load on the avatar, it would be appreciated.

On another note, I did simulate fake errors occuring to show that I've kept error messages in mind. Local storage is used and I used setTimeout to 2000ms to give it a server like loading simulation without any actual back end server running, and utilizing math.random that when it generates 5 (1 through 5 being the range) will show the error message, so you can just refresh the page again and it should work again.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Chris Paschall•440
    @ChrisP1108
    Posted over 3 years ago

    Just to give an update on the images not loading. I got the avatar images to load. I essentially had to change all the image path to permalink paths, which is not the most ideal way to do it since it's not migration friendly, but I'm not planning on moving it to another domain other than github anytime soon, so I'll keep it at this for now.

Join our Discord community

Join thousands of Frontend Mentor community members taking the challenges, sharing resources, helping each other, and chatting about all things front-end!

Join our Discord
Frontend Mentor logo

Stay up to datewith new challenges, featured solutions, selected articles, and our latest news

Frontend Mentor

  • Unlock Pro
  • Contact us
  • FAQs
  • Become a partner

Explore

  • Learning paths
  • Challenges
  • Solutions
  • Articles

Community

  • Discord
  • Guidelines

For companies

  • Hire developers
  • Train developers
© Frontend Mentor 2019 - 2025
  • Terms
  • Cookie Policy
  • Privacy Policy
  • License

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

How does the accessibility report work?

When a solution is submitted, we use axe-core to run an automated audit of your code.

This picks out common accessibility issues like not using semantic HTML and not having proper heading hierarchies, among others.

This automated audit is fairly surface level, so we encourage to you review the project and code in more detail with accessibility best practices in mind.

How does the CSS report work?

When a solution is submitted, we use stylelint to run an automated check on the CSS code.

We've added some of our own linting rules based on recommended best practices. These rules are prefixed with frontend-mentor/ which you'll see at the top of each issue in the report.

The report will audit all CSS, SCSS and Less files in your repository.

How does the HTML validation report work?

When a solution is submitted, we use html-validate to run an automated check on the HTML code.

The report picks out common HTML issues such as not using headings within section elements and incorrect nesting of elements, among others.

Note that the report can pick up “invalid” attributes, which some frameworks automatically add to the HTML. These attributes are crucial for how the frameworks function, although they’re technically not valid HTML. As such, some projects can show up with many HTML validation errors, which are benign and are a necessary part of the framework.

How does the JavaScript validation report work?

When a solution is submitted, we use eslint to run an automated check on the JavaScript code.

The report picks out common JavaScript issues such as not using semicolons and using var instead of let or const, among others.

The report will audit all JS and JSX files in your repository. We currently do not support Typescript or other frontend frameworks.

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub