TheOdinProject / curriculum

The open curriculum for learning web development
https://www.theodinproject.com/
Other
9.99k stars 13.35k forks source link

Setting Up A React Environment: Correct expected terminal output in the lesson #26817

Closed Grisoly closed 10 months ago

Grisoly commented 10 months ago

Checks

Describe your suggestion

The output expected with the lesson differs from the actual output for someone who follows the steps. Screenshot from 2023-11-25 12-18-45 Screenshot from 2023-11-25 12-20-41

Path

Other / NA

Lesson Url

https://www.theodinproject.com/lessons/node-path-react-new-setting-up-a-react-environment

(Optional) Discord Name

No response

(Optional) Additional Comments

No response

wise-king-sullyman commented 10 months ago

Is the framework selection what you weren't expecting?

If so can you confirm that you passed the --template react flag when you ran it? From my understanding, that's what should've automatically selected the React template.

Grisoly commented 10 months ago

Correct, I wasn't expecting the framework selection. Then I manually passed the --template react flag.

wise-king-sullyman commented 10 months ago

So just to confirm, even with the --template react flag it's bringing up the framework selection menu?

Grisoly commented 10 months ago

Yes, I confirm that I wrote this code and it gave me the framework selection menu. Screenshot from 2023-11-27 15-38-50

wise-king-sullyman commented 10 months ago

Hmmm not sure what's going on here as when I test it everything seems to work as expected

image

Can anyone else replicate this?

Grisoly commented 10 months ago

I replicated it 2 times and it worked. I am not sure why it did it the first time and also asked me to select the variant. I just found why it may have happened, it's because I didn't check that I used the LTS version of Node and used the v21.1.0. Now it works fine. Thanks a lot Screenshot from 2023-11-27 16-03-54

wise-king-sullyman commented 10 months ago

👍 thanks for following up @Grisoly!

I'm going to go ahead and close this issue since it sounds like it's resolved, but if it starts happening again for some reason feel free to reopen.