Where does FCC store challanges code?

I started the react challenges using MS Edge browser. This turned out to be a mistake as any code with a console.log message in will not run in Edge. And F12 does nothing useful either. But it was many challenges before I reached code where console was a necessary part of the code.

When I had to run console, I cut and pasted to Firefox and it worked fine.

But here is the weird thing. With Edge, I can logout, log back in and my changes are in the challenges. But logging in via Firefox, and none of my code is there. So it as if the changes are not associated with my username. Rather they are held in cookies within Edge. But that can’t be the case.

Can it?

There are two different types of saved progress for Free Code Camp: your profile and your browser cache.

A list of your completed challenges is saved to your account in the FCC database. You can see the list of completed challenges by looking at your public portfolio. With a growing curriculum already over 1,400 lessons and a growing user base several times that size, FCC does not store every solution to every challenge in its database. When you complete a challenge, there is a popup that gives you the option to download your solution. This gives you the option to save copy of any solution that you may want to reference later. There are some challenges which are classified as projects required for certifications. Your solutions to those can be viewed on your settings page.

Your in-editor code is saved in your browser’s local storage. Recent in-progress code from the challenge editor is also saved in your local browser cache when you run tests. Because FCC rolled out a completely new application, the old cached values are no longer valid. This is the same effect you would have if you cleared your browser cache. If you are completing lessons and do not see your recent code, then something is preventing FCC from writing to your browser’s storage. This could be a browser setting, a privacy extension, or a browser version incompatibility. Especially as you get to more complicated challenges that may take multiple sessions, I strongly recommend saving your in-progress work outside of the browser cache.

This is a good opportunity to learn the ins and outs of your GitHub account, but you can also just save locally or use a service like repl.it which allows for versioning.

1 Like