Fix: Output folder issue fix #7
Open
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
hyqshr
changed the title
Run Locally to README
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.
In this PR:
1. Add
Run Locallysection to READMENew
Run Locallysection provides step-by-step instructions for setting up and running the extension on local machines.2. Resolve Output Folder Bug
Issue
After setting up using the
Run Locallyinstructions, the webview will keep loading indefinitely. Additionally, VSCode will output the following error:I noticed that in
tsconfig.json:while in
package.json:This is the source of the bug.
Solution
I resolved the issue by updating
package.json:This adjustment ensures consistency between the specified output directory in the tsconfig.json file and the main entry point defined in the package.json. This is crucial for the extension to load correctly without errors in VSCode.