-
Notifications
You must be signed in to change notification settings - Fork 999
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]: Compatibility Check Error Message with the wrong link (Page Not Found error) #8224
Comments
Gah! This explains the massive amount of errors we're getting right now. I vaguely recall running across something like this in the past — it's possible there's something busted between the yarn version reported in the console output and the yarn version (different bin path) that's used for the semver check. Here's where the semver check code lives: Any chance you have time today to help diagnose? |
Oh, one more thing you can do to help @ahaywood From the parent directory you are attempting to install into (probably I feel like this could also be the case where you've installed Yarn 3 globally and our semver check gets messed up. PS: don't you know that it's a part of developer lore to never put your repos inside Dropbox cause sync fights with git?? 😉 |
Update: Worked with @jtoar The error message being reported by If I set Node to v18 and try again it works like a champ. |
I can't reproduce the link being wrong yet in my terminal; here it is in the source:
If you copy paste that it's right, so maybe something is going wrong with |
Reopening till we get the link sorted out |
Sounds similar to sindresorhus/terminal-link#18 |
I can reproduce this in hyper, thanks @ahaywood! |
What's not working?
If there's a compatibility issue when installing Redwood, the link in the error message goes to the wrong place.
How do we reproduce the bug?
I ran
yarn create redwood-app my-successful-app
I ran into a compatibility issue:
When I click on the link, it takes me here: https://redwoodjs.com/docs/tutorial/chapter1/prerequisites%E2%80%8B
which does not exist.
It looks like the printed link is correct, but somehow I zero-width space character
%E2%80%8B
is tacked on and encoded at the end of the URL.What's your environment? (If it applies)
No response
Are you interested in working on this?
The text was updated successfully, but these errors were encountered: