New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bug(curriculum): Advanced Node Challenges fail when using localhost for url #36739
Comments
Update: I used a working Glitch project url for both the beta site and locally and get the same results. I did not check any other of the challenges in this sections, but I have a feeling none of them work. |
Curriculum is independent of the release label. That's kept for platform mostly. |
@raisedadead I added the |
It is all of the curriculum challenges in this section and not just one challenge. To me, this is a show-stopper and must be fixed before the next release to production. |
This is a platform issue, which I brought in with 56d78a1 |
Don't be so hard on yourself @raisedadead. It is as @RandellDawson guessed. The CORS in the boilerplate is where the error is coming from. Currently the boilerplate only excepts requests from In short, not a blocker for the For developing the challenges locally, update the cors in the boilerplate to accept |
🤦♂Thanks a ton @Bouncey ! You are life saver. 15 months worth of dev has definitely kept me on the edge for a while. Lol. :) |
@raisedadead Should we close this? |
Not sure if this will actually be a bug once we go to production, but I noticed if I use
http://localhost:3001
(my local running version of the first challenge in theAdvanced Node Challenges
, none of the tests pass and there are several errors in the console. This also happens when I run everything locally.Using the same url on the current production site for the same challenge does not fail any of the tests.
I have validated the solution is correct.
This is annoying if you are trying to make changes to a challenge to validate the tests are working as they should (without having to run
npm run:test:curriculum
) after every code change while working on challenge tests.The text was updated successfully, but these errors were encountered: