docs(v2): fix docusaurus init issue when not using @latest #3803
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
slorber
added
the
pr: documentation
|
Deploy preview for docusaurus-2 ready! Built with commit f408f77 |
|
Size Change: +21 B (0%) Total Size: 153 kB ℹ️ View Unchanged
|
|
@slorber thanks! |
1 similar comment
|
@slorber thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
npx @docusaurus/initseems to fail on some older Node versions, as npx tries to run a localinitbinary (the part after the /).See also the output of
npx @docusaurus/echo teston holder node here:As we don't plan to require newer node versions, we now document to use
npx @docusaurus/init@latestinstead, as it seems to work fine even in older node versions.Note: previously we installed with the
@nexttag (which we removed), so now we are just changing the dist tag from next to latest.Related to #3799