yarn content move errors
See original GitHub issueOn latest yari, do a move like
yarn content move Web/API/DocumentOrShadowRoot/fullscreenElement Web/API/Document/fullscreenElement
Output:
Will move 1 documents from Web/API/DocumentOrShadowRoot/fullscreenElement to Web/API/Document/fullscreenElement for en-US
Web/API/DocumentOrShadowRoot/fullscreenElement → Web/API/Document/fullscreenElement
? Proceed? Yes
Trying to resolve a non-en-us path for /zh-CN/docs/Web without CONTENT_TRANSLATED_ROOT set.
Trying to resolve a non-en-us path for /zh-CN/docs/Web/JavaScript/Reference/Global_Objects/Object/create without CONTENT_TRANSLATED_ROOT set.
Trying to resolve a non-en-us path for /zh-CN/docs/Web/JavaScript/Reference/Global_Objects/Object/seal without CONTENT_TRANSLATED_ROOT set.
Trying to resolve a non-en-us path for /zh-CN/docs/Web/JavaScript/Reference/Global_Objects/Object/isSealed without CONTENT_TRANSLATED_ROOT set.
Trying to resolve a non-en-us path for /zh-CN/docs/Web/JavaScript/Reference/Global_Objects/Object/preventExtensions without CONTENT_TRANSLATED_ROOT set.
Trying to resolve a non-en-us path for /zh-CN/docs/Web/JavaScript/Reference/Global_Objects/Object/freeze without CONTENT_TRANSLATED_ROOT set.
Trying to resolve a non-en-us path for /zh-CN/docs/Web/JavaScript/Reference/Global_Objects/Object/isFrozen without CONTENT_TRANSLATED_ROOT set.
error: To-URL has to resolve to a file (/en-US/docs/Web/API/DocumentOrShadowRoot/fullscreenElement)
error Command failed with exit code 1.
Questions:
- Are there docs on what to do regarding CONTENT_TRANSLATED_ROOT? Do I need to set this even though I don’t want to do anything with translations?
error: To-URL has to resolve to a file (/en-US/docs/Web/API/DocumentOrShadowRoot/fullscreenElement)
makes no sense to me. DocumentOrShadowRoot/fullscreenElement is the file that was moved and so, yes, that file doesn’t exit anymore.
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
Yarn check reports errors after yarn install #6427 - GitHub
I used yarn check in CI to ensure that the lockfile is up to date, to catch things like forgetting to commit the...
Read more >Common Beginner Mistake: Forgetting to Move Your Yarn
When you forget to move the yarn correctly, you end up with an extra loop of yarn over your needle. This makes a...
Read more >error Command failed with exit code 1. when I try to run yarn
I am learning reactjs - nodejs I was trying to run the server so I installed yarn, nodemon, express but when I try...
Read more >Migration | Yarn - Package Manager
This error appears when Node is executed without the proper environment variables. In such a case, the underlying application won't be able to...
Read more >4 Common Knitting Mistakes—and How to Quickly Fix Them
... dropped a stitch, added extra stitches, or had an accidental yarn over? Here's how to catch and correct those common knitting mistakes....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
It happens because the tool that validates redirects gets invoked as part of the
move
CLI. This was a recent addition and the problem persists within theyari
repo too (ie.yarn tool move ...
).To get yourself unstuck, since @fiji-flo is on PTO today, consider cloning the whole
mdn/translated-content
repo somewhere and run:Thanks @fiji-flo, this works now as discussed in #2982.
Great work, I really appreciate you fixing this 😃