feat(update): update mode #3
Open
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.
fix: #2
I've completed the first version of the
updatefeature. If this approach looks good, I'd be happy to add an interactive mode next.Key points and questions:
Added
settings.jsonfile since it's recommended by@antfu/eslint-configand needed for proper editor setupCurrently using the YAML parser which is well-tested, but we could switch to parsing the
pnpm.workspacefile manually since its format is straightforward. What do you prefer?Should we add automatic code formatting (using Prettier/ESLint) when writing files?
Since
pnpm listdoesn't show version requirement symbols (like^or>=), I defaulted to using^. We can either:Updated the console output colors, using taze as inspiration for the color scheme
Note: Originally planned to support
peerDependenciesandoptionalDependencies, but removed this for now sincepnpm listonly shows dev dependency status.