chore(site): manually control frames on code blocks

JamieMason · JamieMason · commit bc6f81393343 · 2026-05-04T20:31:41.000+01:00
diff --git a/site/src/content/docs/command/fix.mdx b/site/src/content/docs/command/fix.mdx
@@ -23,7 +23,7 @@ Fix version mismatches in your monorepo. When the same dependency has different
 
 ## Examples
 
-```bash
+```bash frame="none"
 # Preview changes without modifying files
 syncpack fix --dry-run
 # Fix only dependencies and devDependencies (exclude peer, optional)
diff --git a/site/src/content/docs/command/format.mdx b/site/src/content/docs/command/format.mdx
@@ -18,7 +18,7 @@ Format package.json files in your monorepo. Sorts fields into consistent order a
 
 ## Examples
 
-```bash
+```bash frame="none"
 # Fix every formatting issue in the monorepo
 syncpack format
 # List all formatting issues in the monorepo
diff --git a/site/src/content/docs/command/json.mdx b/site/src/content/docs/command/json.mdx
@@ -24,7 +24,7 @@ The [fix](COMMAND_FIX) and [format](COMMAND_FORMAT) commands also support `--rep
 
 ## Examples
 
-```bash
+```bash frame="none"
 # Output all dependencies as JSON
 syncpack json
 # Output only AWS SDK dependencies
diff --git a/site/src/content/docs/command/lint.mdx b/site/src/content/docs/command/lint.mdx
@@ -20,7 +20,7 @@ Check for version mismatches in your monorepo. Reports dependencies that don't m
 
 ## Examples
 
-```bash
+```bash frame="none"
 # Find all issues in "dependencies" or "devDependencies"
 syncpack lint --dependency-types prod,dev
 # Only lint issues in "react" specifically
diff --git a/site/src/content/docs/command/list.mdx b/site/src/content/docs/command/list.mdx
@@ -20,7 +20,7 @@ List all dependencies in your monorepo with their versions and locations. Shows
 
 ## Examples
 
-```bash
+```bash frame="none"
 # Sort dependencies by how many times they are used
 syncpack list --sort count
 # Show every instance of each dependency, not just their names
diff --git a/site/src/content/docs/command/update.mdx b/site/src/content/docs/command/update.mdx
@@ -25,7 +25,7 @@ Update dependencies in your monorepo to newer versions from the npm registry. Ch
 
 ## Examples
 
-```bash
+```bash frame="none"
 # Accept any update in latest (x.x.x)
 syncpack update --target latest
 # Only update minor versions (1.x.x)
diff --git a/site/src/content/docs/config/syncpackrc.mdx b/site/src/content/docs/config/syncpackrc.mdx
@@ -14,7 +14,7 @@ Syncpack searches the current directory for a:
 
 A custom name and location can be provided instead, but it must have a file extension:
 
-```bash
+```bash frame="none"
 syncpack list --config ./config/syncpack.json
 ```
 
diff --git a/site/src/content/docs/guide/migrate-v14.mdx b/site/src/content/docs/guide/migrate-v14.mdx
@@ -3,7 +3,7 @@ title: Migrate to 14
 description: Migration guide for upgrading from syncpack v13 to v14 with breaking changes and new features
 ---
 
-```bash
+```bash frame="none"
 npm install --save-dev syncpack
 ```
 
@@ -13,7 +13,7 @@ npm install --save-dev syncpack
 
 `list-mismatches` and `lint-semver-ranges` have been merged into a single `lint` command which checks whether every specifier matches the semver group and version group they belong to. The `lint` command no longer checks formatting, which is now handled by `syncpack format ––check`.
 
-```bash
+```bash frame="none"
 # v13
 syncpack list-mismatches --types prod,dev
 # v14
@@ -24,7 +24,7 @@ syncpack lint --dependency-types prod,dev
 
 `list-mismatches` and `lint-semver-ranges` have been merged into a single `lint` command which checks whether every specifier matches the semver group and version group they belong to. The `lint` command no longer checks formatting, which is now handled by `syncpack format ––check`. It's no longer possible to manage semver ranges without also checking version mismatches, because the two things are so closely linked. Changes to semver ranges affect which versions are considered valid and can indirectly cause version mismatches, so they are now always checked and changed together via the `lint` and `fix` commands.
 
-```bash
+```bash frame="none"
 # v13
 syncpack lint-semver-ranges
 # v14
@@ -35,7 +35,7 @@ syncpack lint
 
 `fix-mismatches` and `set-semver-ranges` have been merged into a single `fix` command which autofixes issue found by `syncpack lint`. The `fix` command no longer fixes formatting, which is now handled by `syncpack format`.
 
-```bash
+```bash frame="none"
 # v13
 syncpack fix-mismatches
 # v14
@@ -46,7 +46,7 @@ syncpack fix
 
 `fix-mismatches` and `set-semver-ranges` have been merged into a single `fix` command which autofixes issue found by `syncpack lint`. The `fix` command no longer fixes formatting, which is now handled by `syncpack format`. It's no longer possible to manage semver ranges without also checking version mismatches, because the two things are so closely linked. Changes to semver ranges affect which versions are considered valid and can indirectly cause version mismatches, so they are now always checked and changed together via the `lint` and `fix` commands.
 
-```bash
+```bash frame="none"
 # v13
 syncpack set-semver-ranges
 # v14
@@ -57,7 +57,7 @@ syncpack fix
 
 The `prompt` command is an interactive prompt which lists all current issues which syncpack can't fix automatically. It is not yet available in v14 and will be added at a later date. Syncpack can't automatically fix mismatches between specifiers it does not support, which are usually specifiers which are not semver, such as pnpm overrides, or complex semver specifiers like `^1.2.3 || ^2.0.0`.
 
-```bash
+```bash frame="none"
 # v13
 syncpack prompt
 # v14
@@ -70,7 +70,7 @@ syncpack prompt
 
 Renamed for consistency and also to differentiate it from other types such as specifier types.
 
-```bash
+```bash frame="none"
 # v13
 syncpack list-mismatches --types prod,dev
 # v14
@@ -81,7 +81,7 @@ syncpack lint --dependency-types prod,dev
 
 Renamed for consistency.
 
-```bash
+```bash frame="none"
 # v13
 syncpack format --specs exact,range
 # v14
@@ -92,7 +92,7 @@ syncpack format --specifier-types exact,range
 
 This has been renamed to `dependencies` to match the equivalent property of version groups and semver groups. Regular expressions are no longer supported and instead a glob pattern should be provided in the same way as they are for version groups and semver groups.
 
-```bash
+```bash frame="none"
 # v13
 syncpack list-mismatches --filter "^@types\/.+"
 # v14
@@ -122,7 +122,7 @@ The `dependencyTypes` config has been removed in favour of using `versionGroups`
 
 Or use the `--dependency-types` CLI option to filter on an ad hoc basis:
 
-```bash
+```bash frame="none"
 syncpack lint --dependency-types prod,dev,peer
 ```
 
@@ -147,7 +147,7 @@ The `specifierTypes` config has been removed in favour of using `versionGroups`
 
 Or use the `--specifier-types` CLI option to filter on an ad hoc basis:
 
-```bash
+```bash frame="none"
 syncpack format --specifier-types exact,range
 ```
 
@@ -164,7 +164,7 @@ The `lint` command no longer checks formatting, only version mismatches, so the
 }
 ```
 
-```bash
+```bash frame="none"
 # Check if formatting needed (exit 1 if needed)
 syncpack format --check
 # Safely see what formatting fixes would look like
@@ -207,7 +207,7 @@ This option is redundant in V14.
 
 The `workspace` dependency type has been renamed to `local` for clarity.
 
-```bash
+```bash frame="none"
 # v11.2.0 and earlier
 syncpack list --types prod,workspace
 # v14
@@ -220,7 +220,7 @@ syncpack lint --dependency-types prod,local
 
 Individual boolean flags replaced with `--dependency-types` option:
 
-```bash
+```bash frame="none"
 # v8
 syncpack list --prod --dev --peer
 # v14
@@ -270,7 +270,7 @@ Individual boolean properties replaced with `versionGroups` configuration:
 
 The `--overrides` option now refers to npm overrides. pnpm users must use `--pnpmOverrides` instead.
 
-```bash
+```bash frame="none"
 # v7 (pnpm users)
 syncpack list --overrides
 # v14 (pnpm users)
@@ -303,7 +303,7 @@ In v14, disable this behavior using `versionGroups`:
 
 Or exclude `local` when using CLI flags:
 
-```bash
+```bash frame="none"
 # v14
 syncpack lint --dependency-types '!local'
 ```
@@ -330,7 +330,7 @@ In v14, exclude them using `versionGroups`:
 
 Or via CLI:
 
-```bash
+```bash frame="none"
 # v14
 syncpack lint --dependency-types dev,peer,prod
 ```
@@ -341,7 +341,7 @@ syncpack lint --dependency-types dev,peer,prod
 
 Package locations now specified with repeatable `--source` option instead of positional arguments:
 
-```bash
+```bash frame="none"
 # v2
 syncpack list './package.json' './packages/*/package.json'
 # v14
diff --git a/site/src/content/docs/guide/migrate-v15.mdx b/site/src/content/docs/guide/migrate-v15.mdx
@@ -5,7 +5,7 @@ sidebar:
   badge: New
 ---
 
-```bash
+```bash frame="none"
 npm install --save-dev syncpack
 ```
 
diff --git a/site/src/content/docs/reference/dependency-types.mdx b/site/src/content/docs/reference/dependency-types.mdx
@@ -27,7 +27,7 @@ Catalog dependency types are added automatically when syncpack detects [pnpm cat
 
 Bun also recognises `workspaces.catalog` and `workspaces.catalogs.<name>`. These names work everywhere a dependency type is accepted.
 
-```bash
+```bash frame="none"
 syncpack lint --dependency-types pnpmCatalog
 syncpack list --dependency-types 'pnpmCatalog:react18'
 ```
@@ -49,7 +49,7 @@ Dependency types can be specified in these contexts:
 
 Use the `--dependency-types` option to target specific types in commands:
 
-```bash
+```bash frame="none"
 # Only check production dependencies
 syncpack lint --dependency-types prod
 
diff --git a/site/src/content/docs/reference/specifier-types.mdx b/site/src/content/docs/reference/specifier-types.mdx
@@ -124,7 +124,7 @@ Specifier types can be used in various contexts within syncpack:
 
 Use the `--specifier-types` option to target dependencies with specific version formats:
 
-```bash
+```bash frame="none"
 # Only check dependencies with exact versions
 syncpack lint --specifier-types exact
 
diff --git a/site/src/faq/ban-dependency-from-monorepo.mdx b/site/src/faq/ban-dependency-from-monorepo.mdx
@@ -21,12 +21,12 @@ Ban a dependency from being used anywhere in your monorepo.
 
 Now when you run any syncpack command, banned dependencies will be listed:
 
-```bash
+```bash frame="none"
 syncpack list
 ```
 
 And can be removed:
 
-```bash
+```bash frame="none"
 syncpack fix-mismatches
 ```
diff --git a/site/src/faq/fix-aws-sdk-version-mismatch.mdx b/site/src/faq/fix-aws-sdk-version-mismatch.mdx
@@ -26,12 +26,12 @@ Pin all dependencies from [@aws-sdk](HREF_AWS_SDK) so that they are always ident
 
 Any `@aws-sdk` packages which do not have the expected version can then be found:
 
-```bash
+```bash frame="none"
 syncpack list-mismatches
 ```
 
 And fixed:
 
-```bash
+```bash frame="none"
 syncpack fix-mismatches
 ```
diff --git a/site/src/faq/only-allow-types-in-dev-dependencies.mdx b/site/src/faq/only-allow-types-in-dev-dependencies.mdx
@@ -28,6 +28,6 @@ Only allow TypeScript [@types](HREF_TYPES) packages from being used anywhere oth
 
 Any `@types` packages which are in the wrong location can then be found and manually moved:
 
-```bash
+```bash frame="none"
 syncpack list-mismatches
 ```
diff --git a/site/src/faq/sync-engines-in-monorepo.mdx b/site/src/faq/sync-engines-in-monorepo.mdx
@@ -24,13 +24,13 @@ I've chosen a name of `engines` but it can be anything you like.
 
 Perform a one-off check of all versions defined under `engines` in your monorepo.
 
-```bash
+```bash frame="none"
 syncpack list --dependency-types engines
 ```
 
 If the versions are not identical, they can be synchronised to all use the highest of the semver versions currently in use.
 
-```bash
+```bash frame="none"
 syncpack fix-mismatches --dependency-types engines
 ```
 
@@ -51,7 +51,7 @@ Add your new custom type to your `dependencyTypes`.
 
 Now when you run any syncpack command, versions under `engines` will also be checked.
 
-```bash
+```bash frame="none"
 syncpack list
 ```
 
diff --git a/site/src/faq/sync-nodejs-version-in-monorepo.mdx b/site/src/faq/sync-nodejs-version-in-monorepo.mdx
@@ -23,13 +23,13 @@ I've chosen a name of `nodeEngine` but it can be anything you like.
 
 Perform a one-off check for every usage of `engines.node` in your monorepo.
 
-```bash
+```bash frame="none"
 syncpack list --dependency-types nodeEngine
 ```
 
 If the versions are not identical, they can be synchronised to all use the highest of the semver versions currently in use.
 
-```bash
+```bash frame="none"
 syncpack fix-mismatches --dependency-types nodeEngine
 ```
 
@@ -57,7 +57,7 @@ Add your new custom type to your `dependencyTypes` at the root level. It is incl
 
 Now when you run any syncpack command, `engines.node` will also be checked.
 
-```bash
+```bash frame="none"
 syncpack list
 ```
 
