docs: rewrite README, add CONTRIBUTING, and polish project metadata#1
Merged
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
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.
Summary
Polishes the project's open-source front door. No runtime/behavior changes beyond a pnpm-version requirement bump.
npx+ version-manager PATH gotcha with fnm/nvm/asdf/volta/mise), and a "What's in the name" note (the-wrightmaker tradition, a nod to Playwright).@figwright/mcpdescription and addedkeywordsfor discoverability; aligned the root description to match.engines.pnpmto>=11.0.0and aligned the docs (the project already pinspnpm@11.8.0viapackageManager).Validation
typecheck,lint,format:check,knip,build,test(664 tests).publintreports no issues for@figwright/mcp.Out of band