syncpack
syncpack copied to clipboard
Consistent dependency versions in large JavaScript Monorepos.
### Description When two workspaces are in separate hierarchies and need to reference a common patch as a dependency, I use the relative path to the patch directory. However, in...
## Description Syncpack doesn't indents/formats the package json based on the .editorconfig options ## Suggested Solution It should read from editorconfig or eslint to format the package json properly
## Description Get package json files patterns - paths not normalized with older npm version Version of syncpack: 9.8.4 OS: Windows Package Manager: NPM --- I have the following root...
## Description Going from [12.3.0 -> 12.3.1](https://renovatebot.com/diffs/npm/syncpack/12.3.0/12.3.1) introduced a breaking change (going ESM). I had a CJS package that depended on the types from `syncpack`, and I cannot build it...
## Description I have a package `@myorg/remix` where we keep common Remix utilities. It has `peerDependencies` set as follows: ``` "peerDependencies": { ... "@remix-run/node": "^2.8.1", "@remix-run/react": "^2.8.1", }, ``` I...
## Description When using syncpack 12.3.1, running `yarn syncpack update` results in every package being given the version number of the last checked package. e.g. if `some-package` has a new...
## Description When you use `$pkg` as the version in pnpm overrides, which should just use the version specified in `dependencies`, syncpack is unhappy. ## Suggested Solution replace $pkg by...
## Description 1. create any valid syncpack config json 2. add `"$schema": "https://unpkg.com/[email protected]/dist/schema.json"` to your config 3. the schema fails to validate due to the presence of a `$schema` field...
## Description `syncpack format` orders dependencies differently than npm does, so package.json can easily become "unformatted" every time you install a new package (npm likes to re-sort things). This is...
## Description In the monorepo I work in, there are a large number of package.json files configured using (yarn, soon pnpm) workspaces, and then some few additional package.json files that...