Moving from Glitch to

Due to recent problems with Glitch, we are recommending everyone to start using for the back-end Node challenges and certification projects. We have already merged this pull request to update all the existing Glitch demo projects and boilerplates used in the challenges to the corresponding equivalent.

If you have already started the challenges or projects in Glitch, you can continue to do so but be aware the tests may fail unexpectedly and/or you may not be able to access your project code. We highly suggest moving your existing code to the corresponding boilerplate to avoid further problems.

There are some differences between Glitch and that could cause some confusion:

  • does not appear to have something like nodemon implemented, so you must click Stop and click Run each time to see your changes and before resubmitting the solution (“live”) url of the back-end challenges.

  • Discovering the solution url (that needs to be submitted) is less straightforward. To access it, you need to click the Run button the first time which will run npm install and then npm start. Next, you will finally see something like the following. You then click the Open in new tab button located near the upper right-hand corner, which will open the solution url in a new browser tab.

In the above example, the solution url would be:

If you experience any issues after this change is implemented, please let us know via the Contributor category or create a new issue on GitHub if it has not already been created.

Thank you for your understanding while we make this change.


Finally! Now I can go back to learning Node on Freecodecamp. :smile:

1 Like

Many thanks to the freeCodeCamp team for making the switch to the platform. A wise choice of platforms - performant, reliable, and good value for money, IMO, if you want private repls. Oh, and I forgot to mention the tight github integration - this feature alone is worth the effort of making the switch (for those of us who prefer offline editing, committing, and pushing).


FYI: Command/Control+Enter will restart the server and it’s pretty quick. It’s also possible to do nodemon but we’ve find that the restart experience to be good enough and doesn’t suffer from the problem of thrashing the server on every keystroke.


Thanks a lot @amasad! I did not know it was that easy, (in fact our practice challenges use the same shortcut, so this really works in everyones favor).

I think we will document this on the challenges for everyone’s benefit.

Good to know. I was about to start the QA certificate projects.
I also experienced some issues with testing my QA learning projects I just stubbornly imported and ran on glitch, so far only managed to pass 95% of course tests(and had to edit fcctesting.js in order to make the verification process pass most Advanced Node and Express sections).