feat(cli): add command to update dependencies

Author: JamieMason

.github/workflows/ci.yaml

@@ -11,7 +11,7 @@ jobs:
     strategy:
       matrix:
         os: [ubuntu-latest, windows-latest]
-        node-version: [16.x]
+        node-version: [18.x]
 
     steps:
       - uses: actions/checkout@v2
@@ -45,7 +45,10 @@ jobs:
         env:
           FORCE_COLOR: 3
           TERM: xterm-256color
-      - uses: paambaati/[email protected]
+
+      - name: Code Climate
+        uses: paambaati/[email protected]
+        if: matrix.os == 'ubuntu-latest'
         env:
           CC_TEST_REPORTER_ID: ${{ secrets.CC_TEST_REPORTER_ID }}
         with:

.syncpackrc.js

@@ -18,6 +18,11 @@ const config = {
       packages: ['**'],
       pinVersion: '11.1.0',
     },
+    {
+      dependencies: ['ora'],
+      packages: ['**'],
+      pinVersion: '5.4.1',
+    },
   ],
 };
 

CODE_OF_CONDUCT.md

@@ -2,124 +2,109 @@
 
 ## Our Pledge
 
-We as members, contributors, and leaders pledge to make participation in our
-community a harassment-free experience for everyone, regardless of age, body
-size, visible or invisible disability, ethnicity, sex characteristics, gender
-identity and expression, level of experience, education, socio-economic status,
-nationality, personal appearance, race, religion, or sexual identity
-and orientation.
+We as members, contributors, and leaders pledge to make participation in our community a
+harassment-free experience for everyone, regardless of age, body size, visible or invisible
+disability, ethnicity, sex characteristics, gender identity and expression, level of experience,
+education, socio-economic status, nationality, personal appearance, race, religion, or sexual
+identity and orientation.
 
-We pledge to act and interact in ways that contribute to an open, welcoming,
-diverse, inclusive, and healthy community.
+We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and
+healthy community.
 
 ## Our Standards
 
-Examples of behavior that contributes to a positive environment for our
-community include:
+Examples of behavior that contributes to a positive environment for our community include:
 
-* Demonstrating empathy and kindness toward other people
-* Being respectful of differing opinions, viewpoints, and experiences
-* Giving and gracefully accepting constructive feedback
-* Accepting responsibility and apologizing to those affected by our mistakes,
-  and learning from the experience
-* Focusing on what is best not just for us as individuals, but for the
-  overall community
+- Demonstrating empathy and kindness toward other people
+- Being respectful of differing opinions, viewpoints, and experiences
+- Giving and gracefully accepting constructive feedback
+- Accepting responsibility and apologizing to those affected by our mistakes, and learning from the
+  experience
+- Focusing on what is best not just for us as individuals, but for the overall community
 
 Examples of unacceptable behavior include:
 
-* The use of sexualized language or imagery, and sexual attention or
-  advances of any kind
-* Trolling, insulting or derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information, such as a physical or email
-  address, without their explicit permission
-* Other conduct which could reasonably be considered inappropriate in a
-  professional setting
+- The use of sexualized language or imagery, and sexual attention or advances of any kind
+- Trolling, insulting or derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or email address, without their
+  explicit permission
+- Other conduct which could reasonably be considered inappropriate in a professional setting
 
 ## Enforcement Responsibilities
 
-Community leaders are responsible for clarifying and enforcing our standards of
-acceptable behavior and will take appropriate and fair corrective action in
-response to any behavior that they deem inappropriate, threatening, offensive,
-or harmful.
+Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior
+and will take appropriate and fair corrective action in response to any behavior that they deem
+inappropriate, threatening, offensive, or harmful.
 
-Community leaders have the right and responsibility to remove, edit, or reject
-comments, commits, code, wiki edits, issues, and other contributions that are
-not aligned to this Code of Conduct, and will communicate reasons for moderation
-decisions when appropriate.
+Community leaders have the right and responsibility to remove, edit, or reject comments, commits,
+code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and
+will communicate reasons for moderation decisions when appropriate.
 
 ## Scope
 
-This Code of Conduct applies within all community spaces, and also applies when
-an individual is officially representing the community in public spaces.
-Examples of representing our community include using an official e-mail address,
-posting via an official social media account, or acting as an appointed
-representative at an online or offline event.
+This Code of Conduct applies within all community spaces, and also applies when an individual is
+officially representing the community in public spaces. Examples of representing our community
+include using an official e-mail address, posting via an official social media account, or acting as
+an appointed representative at an online or offline event.
 
 ## Enforcement
 
-Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported to the community leaders responsible for enforcement at
-[email protected].
-All complaints will be reviewed and investigated promptly and fairly.
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community
+leaders responsible for enforcement at [email protected]. All complaints will be reviewed and
+investigated promptly and fairly.
 
-All community leaders are obligated to respect the privacy and security of the
-reporter of any incident.
+All community leaders are obligated to respect the privacy and security of the reporter of any
+incident.
 
 ## Enforcement Guidelines
 
-Community leaders will follow these Community Impact Guidelines in determining
-the consequences for any action they deem in violation of this Code of Conduct:
+Community leaders will follow these Community Impact Guidelines in determining the consequences for
+any action they deem in violation of this Code of Conduct:
 
 ### 1. Correction
 
-**Community Impact**: Use of inappropriate language or other behavior deemed
-unprofessional or unwelcome in the community.
+**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or
+unwelcome in the community.
 
-**Consequence**: A private, written warning from community leaders, providing
-clarity around the nature of the violation and an explanation of why the
-behavior was inappropriate. A public apology may be requested.
+**Consequence**: A private, written warning from community leaders, providing clarity around the
+nature of the violation and an explanation of why the behavior was inappropriate. A public apology
+may be requested.
 
 ### 2. Warning
 
-**Community Impact**: A violation through a single incident or series
-of actions.
+**Community Impact**: A violation through a single incident or series of actions.
 
-**Consequence**: A warning with consequences for continued behavior. No
-interaction with the people involved, including unsolicited interaction with
-those enforcing the Code of Conduct, for a specified period of time. This
-includes avoiding interactions in community spaces as well as external channels
-like social media. Violating these terms may lead to a temporary or
-permanent ban.
+**Consequence**: A warning with consequences for continued behavior. No interaction with the people
+involved, including unsolicited interaction with those enforcing the Code of Conduct, for a
+specified period of time. This includes avoiding interactions in community spaces as well as
+external channels like social media. Violating these terms may lead to a temporary or permanent ban.
 
 ### 3. Temporary Ban
 
-**Community Impact**: A serious violation of community standards, including
-sustained inappropriate behavior.
+**Community Impact**: A serious violation of community standards, including sustained inappropriate
+behavior.
 
-**Consequence**: A temporary ban from any sort of interaction or public
-communication with the community for a specified period of time. No public or
-private interaction with the people involved, including unsolicited interaction
-with those enforcing the Code of Conduct, is allowed during this period.
-Violating these terms may lead to a permanent ban.
+**Consequence**: A temporary ban from any sort of interaction or public communication with the
+community for a specified period of time. No public or private interaction with the people involved,
+including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this
+period. Violating these terms may lead to a permanent ban.
 
 ### 4. Permanent Ban
 
-**Community Impact**: Demonstrating a pattern of violation of community
-standards, including sustained inappropriate behavior,  harassment of an
-individual, or aggression toward or disparagement of classes of individuals.
+**Community Impact**: Demonstrating a pattern of violation of community standards, including
+sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement
+of classes of individuals.
 
-**Consequence**: A permanent ban from any sort of public interaction within
-the community.
+**Consequence**: A permanent ban from any sort of public interaction within the community.
 
 ## Attribution
 
-This Code of Conduct is adapted from the [Contributor Covenant][homepage],
-version 2.0, available at
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.0, available at
 https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
 
-Community Impact Guidelines were inspired by [Mozilla's code of conduct
-enforcement ladder](https://github.com/mozilla/diversity).
+Community Impact Guidelines were inspired by
+[Mozilla's code of conduct enforcement ladder](https://github.com/mozilla/diversity).
 
 [homepage]: https://www.contributor-covenant.org
 

README.md

@@ -54,6 +54,12 @@ Displays a series of prompts to fix mismatches which syncpack cannot fix automat
 Ensure dependency versions used within `"dependencies"`, `"devDependencies"` etc follow a consistent
 format.
 
+### [update](https://jamiemason.github.io/syncpack/update)
+
+Interactively update packages to the latest versions from the npm registry, wherever they are in
+your monorepo. You can update every dependency, just dev/peer/prod dependencies, just packages which
+match a name filter, and more.
+
 ## Badges
 
 - [![NPM version](http://img.shields.io/npm/v/syncpack.svg?style=flat-square)](https://www.npmjs.com/package/syncpack)

jest.config.js

@@ -11,9 +11,9 @@ module.exports = {
   coverageThreshold: {
     global: {
       branches: 80,
-      functions: 90,
-      lines: 90,
-      statements: 90,
+      functions: 82,
+      lines: 87,
+      statements: 86,
     },
   },
   moduleFileExtensions: ['ts', 'js'],

package.json

@@ -12,7 +12,8 @@
     "syncpack-list": "dist/bin-list/index.js",
     "syncpack-list-mismatches": "dist/bin-list-mismatches/index.js",
     "syncpack-prompt": "dist/bin-prompt/index.js",
-    "syncpack-set-semver-ranges": "dist/bin-set-semver-ranges/index.js"
+    "syncpack-set-semver-ranges": "dist/bin-set-semver-ranges/index.js",
+    "syncpack-update": "dist/bin-update/index.js"
   },
   "bugs": "https://github.com/JamieMason/syncpack/issues",
   "contributors": [
@@ -30,26 +31,30 @@
     "Tom Fletcher (https://github.com/tom-fletcher)"
   ],
   "dependencies": {
-    "@effect/data": "0.12.5",
-    "@effect/io": "0.26.0",
-    "@effect/match": "0.24.4",
+    "@effect/data": "0.12.9",
+    "@effect/io": "0.27.0",
+    "@effect/match": "0.24.5",
+    "@effect/schema": "0.21.0",
     "chalk": "4.1.2",
     "commander": "11.0.0",
     "cosmiconfig": "8.2.0",
     "enquirer": "2.3.6",
     "fs-extra": "11.1.1",
     "globby": "11.1.0",
     "minimatch": "9.0.1",
+    "ora": "5.4.1",
+    "prompts": "2.4.2",
     "read-yaml-file": "2.1.0",
     "semver": "7.5.2",
     "tightrope": "0.1.0",
     "ts-toolbelt": "9.6.0"
   },
   "devDependencies": {
-    "@tsconfig/node14": "1.0.3",
+    "@tsconfig/node18": "2.0.1",
     "@types/fs-extra": "11.0.1",
     "@types/jest": "29.5.2",
     "@types/node": "14.18.36",
+    "@types/prompts": "2.4.4",
     "@types/semver": "7.5.0",
     "@typescript-eslint/eslint-plugin": "5.59.11",
     "@typescript-eslint/parser": "5.59.11",
@@ -65,7 +70,7 @@
     "typescript": "5.1.3"
   },
   "engines": {
-    "node": ">=14"
+    "node": ">=18"
   },
   "files": [
     "dist"

site/docs/update.mdx

@@ -0,0 +1,33 @@
+---
+id: update
+title: update
+---
+
+Interactively update packages to the latest versions from the npm registry.
+
+## CLI Options
+
+```
+-s, --source [pattern]  glob pattern for package.json files to read from (default: [])
+-f, --filter [pattern]  only include dependencies whose name matches this regex
+-c, --config <path>     path to a syncpack config file
+-t, --types <names>     only include dependencies matching these types (eg. types=dev,prod,myCustomType)
+-h, --help              display help for command
+```
+
+## Examples
+
+```bash
+# uses defaults for resolving packages
+syncpack update
+# uses packages defined by --source when provided
+syncpack update --source "apps/*/package.json"
+# multiple globs can be provided like this
+syncpack update --source "apps/*/package.json" --source "core/*/package.json"
+# uses dependencies regular expression defined by --filter when provided
+syncpack update --filter "typescript|tslint"
+# only inspect "devDependencies"
+syncpack update --types dev
+# only inspect "devDependencies" and "peerDependencies"
+syncpack update --types dev,peer
+```

site/sidebars.js

@@ -25,6 +25,7 @@ const sidebars = {
       'list',
       'prompt',
       'set-semver-ranges',
+      'update',
     ],
     'CLI Options': [
       'option/config',

src/bin-fix-mismatches/effects.ts

@@ -11,41 +11,41 @@ import type { VersionGroupReport } from '../get-version-groups';
 import { DELETE } from '../get-version-groups/lib/delete';
 import { logGroupHeader } from '../lib/log-group-header';
 
-export const fixMismatchesEffects: VersionEffects = {
-  FilteredOut() {
+export const fixMismatchesEffects: VersionEffects<void> = {
+  onFilteredOut() {
     return Effect.unit();
   },
-  Ignored() {
+  onIgnored() {
     return Effect.unit();
   },
-  Valid() {
+  onValid() {
     return Effect.unit();
   },
-  Banned: (input) => {
+  onBanned(input) {
     return Effect.sync(() => removeVersions(input));
   },
-  HighestSemverMismatch: (input) => {
+  onHighestSemverMismatch(input) {
     return Effect.sync(() => setVersions(input));
   },
-  LowestSemverMismatch: (input) => {
+  onLowestSemverMismatch(input) {
     return Effect.sync(() => setVersions(input));
   },
-  PinnedMismatch: (input) => {
+  onPinnedMismatch(input) {
     return Effect.sync(() => setVersions(input));
   },
-  SameRangeMismatch: (input) => {
+  onSameRangeMismatch(input) {
     return Effect.sync(() => pipe(input, logHeader, logSameRangeMismatch));
   },
-  SnappedToMismatch: (input) => {
+  onSnappedToMismatch(input) {
     return Effect.sync(() => setVersions(input));
   },
-  UnsupportedMismatch: (input) => {
+  onUnsupportedMismatch(input) {
     return Effect.sync(() => pipe(input, logHeader, logUnsupportedMismatch));
   },
-  WorkspaceMismatch: (input) => {
+  onWorkspaceMismatch(input) {
     return Effect.sync(() => setVersions(input));
   },
-  TearDown(ctx) {
+  onComplete(ctx) {
     return Effect.sync(() => deleteEmptyObjects(ctx));
   },
 };