docs(quickstart): fix JavaScript initialization and update guides to include full file paths #4322
+334
−334
Conversation
This file contains hidden or 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
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
brandyscarney
commented
Nov 13, 2025
| ## View the App Component | ||
|
|
||
| The root of your app is defined in `app.component.ts`: | ||
| The root of your app is defined in `src/app/app.component.ts`: |
Member
Author
There was a problem hiding this comment.
I thought it would be more clear to put the full path but if we want to only show the full path in the title of the code block I'm fine with that.
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.
Relates to #446
What is the current behavior?
A user reported in this comment that the JavaScript Quickstart does not work with
npm run preview. I confirmed that this does not work following the existing guide.Additionally, all of the guides do not list file paths starting from the root, nor do the code blocks have titles, making it somewhat trickier to find which files to update.
What is the new behavior?
npm run dev,npm run build && npm run previewand Capacitortitleto all code blocks with the full file pathPreviews