I’m not sure where the redirect is meant to be implemented at to be honest. I wanna work on this issue and combine it with another PR I’m working on (the one where the redirect test itself is updated to Typescript)
Hmm, my local copy is completely up to date and I am able to access challenges in es6. Anytime things are working the way they should I usually start off with npm run clean-and-develop.
When you type: https://www.freecodecamp.org/learn/javascript-algorithms-and-data-structures/es6/explore-differences-between-the-var-and-let-keywords
into the browser it redirects you to https://www.freecodecamp.org/learn/javascript-algorithms-and-data-structures/basic-javascript/explore-differences-between-the-var-and-let-keywords.
Yet on my local copy no proper redirect occurs and it takes you to that 404 page. I will happily give the clean and develop a try however.
To be honest, I have no idea how Cypress is supposed to pull in that config. You can see what happens in CI:
Also, you can see the Cypress tests (bar one unrelated) are passing on your PR. So, the issue seems more with your local config when you run the tests.
Since you are using Gatsby pages, could we perhaps leverage something like this so local clients have a chance at performing redirects using the redirects.json? Or some other recipe listed in here.
Would it be worthwhile for me to try to figure out how to add redirects for those particular set of routes and would there be some sort of error detection in the event things inadvertently go sideways?