docs: add build instructions to README#50
Open
kimjune01 wants to merge 1 commit into
Open
Conversation
Addresses vladlavrik#31 by adding comprehensive build documentation including: - Prerequisites (Node.js 18+) - Development and production build commands - Instructions for loading unpacked extension in Chrome - Troubleshooting for OpenSSL error Fixes confusion from maintainer's comment which had typos (npm build dev → npm run dev). Verified build output directory is build/ not dist/.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The README has no build instructions. Contributors have to reverse-engineer the build process from package.json scripts and CI config.
This adds a Development section covering prerequisites, build commands, Chrome extension loading, and common troubleshooting steps.
Fixes #31