Update +page.markdoc #1477
Merged
Update +page.markdoc #1477
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
Issue: 'npm create svelte' has been replaced with 'npx sv create' Replaced old script with new, updated script. This will prevent users following your instructions from running into this error now and in the future.
loks0n
approved these changes
Nov 11, 2024
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.
Issue: 'npm create svelte' has been replaced with 'npx sv create'
Replaced old script with new, updated script. This will prevent users following your instructions from running into this error now and in the future.
What does this PR do?
Updates the SvleteKit walkthrough documentation to fix an issue with the walkthrough that will be a roadblock to every user currently trying to follow the existing instructions.
Test Plan
No test plan required. You can try
npm create svelteon your own to see the issue.Related PRs and Issues
No issue was created. This seemed like a quick, simple fix that didn't require one.
Have you read the Contributing Guidelines on issues?
Sure.