fix: remove website-generator from prepublishOnly #126
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
Fixes npm publish failures by removing
website-generatorfrom theprepublishOnlyscript intextchecker-elementpackage.Problem
The
prepublishOnlyscript was failing duringlerna publishbecause:website-generatorwas incorrectly included in the publish lifecycle--output-dirflag but was never properly configuredSolution
npm run website-generatorfromprepublishOnlyscriptwebsite-generatorscript to use direct path (node ../@textlint/website-generator/bin/cmd.js) for potential future manual useprepublishOnlynow only runsbuild:public-libandbuild, which are the actual requirements for publishingContext
The actual deployment flow is:
websitescript → textchecker-elementwebsitescript →vite buildwebsite-generatorscript is separate and not used in deploymentTest Plan
lerna publish --skip-git --skip-npmfrom repository root to verify prepublishOnly script succeedslib/andpublic-dist/directories--output-dirflag