-
-
Notifications
You must be signed in to change notification settings - Fork 8.5k
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
Print out directory tree during docusaurus-init #665
Conversation
Run docusaurus-init Even by deleting text here, it still shows up? Confused.
Deploy preview for docusaurus-preview ready! Built with commit 4fb727f |
@amyrlam I patched it locally and tested it. This should be good to go! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested it locally. Seems fine!
Sorry, I'm confused. Trying to reproduce locally. What am I doing wrong? Not seeing the tree but
|
You'll have to be within $ node ../lib/copy-examples.js to simulate the |
confused...
|
I think you missed out on installing |
Sorry, I could have sworn I had done that on multiple occasions. Having a lot of issues today locally! Appreciate the help debugging |
Hope it works for you now! You will see more extra stuff because you're printing out the Docusaurus working directory, which is different from a clean slate |
yeap! I finally saw the tree in Docusaurus for the first time 😅 |
cc @yangshun This might be way off...wondering if there is anything wrong at first glance.
I
rm -rf website/
in Docusaurus.I tried replacing an existing
console.log
with new text.When I run
docusaurus-init
, the old text appears, even though it's been deleted from the codebase. Is the repo readingdocusaurus-init
from npm or something and not from localcopy-examples.js
?