https://github.com/trydofor/pnpm-lock-testing

Last synced: over 1 year ago
JSON representation

testing pnpm-lock.yaml

README

# pnpm-lock-testing

```bash
find . -name "node_modules" -type d -prune -exec rm -rf {} +
find . -name "pnpm-lock.yaml" -type f -exec rm -f {} +
```

## 1-solo

```bash
cd 1-solo

## (1) no lockfile change
## Lockfile is up to date, resolution step is skipped
pnpm i

## (2) only add date-fns to lockfile
pnpm add date-fns@4.0.0

## (3) no lockfile change
pnpm up nuxt

## (4) nuxt's deps are changed in lockfile
## only range-version, not fixed-version
pnpm up

```

## 2-mono

```bash
cd 2-mono

## (1) no lockfile change
## Lockfile is up to date, resolution step is skipped
pnpm i

## (2) only add date-fns to lockfile
pnpm -r add date-fns@4.0.0

## (3) no lockfile change
pnpm -r up nuxt

## (4) nuxt's deps are changed in lockfile
## only range-version, not fixed-version
pnpm -r up
```

## 3-hoist

```bash
cd 3-hoist

## (1) BAD!! lockfile change as new project
## TODO pnpmfile.cjs hooks cause changes
pnpm i
```

## 4-hook1 change version

```bash
cd 4-hook1

## (1) change date-fns from 4.0.0 to 4.1.0
## Lockfile is up to date, resolution step is skipped
pnpm i
```

## 5-hook2 add version

```bash
cd 5-hook2

## (1) add date-fns 4.0.0
## Lockfile is up to date, resolution step is skipped
pnpm i
```

## 6-hook3 delete version

```bash
cd 6-hook3

## (1) delete date-fns 4.0.0
## Lockfile is up to date, resolution step is skipped
pnpm i
```

## 7-hook4 change nuxt version

```bash
cd 7-hook4

## (1) change nuxt from 3.12.2 to 3.15.0
## Lockfile is up to date, resolution step is skipped
pnpm i
```