docs(install): correct npm source, document peer deps, fix tailwind path - #3
Merged
Conversation
- Update install command description: npm registry, not GitHub Packages - Add 'Peer dependencies' section explaining auto-install vs explicit install - Manual-install tailwind @source now uses node_modules path (matches the vite + js_entry paths), so all three references point at one location
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
monorail:install— says it installs from "GitHub Packages", butmonorailphpis published to the npm registry.@sourcepath with the Vite input +config('monorail.assets.js_entry')— all three now point atnode_modules/monorailphp/.... Previously the manual-install snippet pointed atvendor/monorail/monorail/..., which didn't match the other paths and used the old composer name.Test plan