The TypeScript pnpm CLI freezes at v11; pnpm 12 will be the Rust pacquet port. To make that split legible, all TypeScript source, test, and build directories move under a new top-level pnpm11/ directory. The name states the version boundary rather than implying a behavioral fork, since the two stacks are meant to behave identically. Scope is source-only: the shared workspace root stays at the repo root. pnpm-workspace.yaml, package.json, pnpm-lock.yaml, .pnpmfile.cjs, .meta-updater, __patches__, .changeset, .husky, and the lint/spell configs remain in place, so one pnpm workspace and one Cargo workspace still span all three products. pnpr/client and pacquet/tasks/registry-mock stay as cross-product workspace members. Rewiring the move required: - pnpm-workspace.yaml globs prefixed with pnpm11/ - root package.json script paths, eslint.config.mjs, tsconfig.lint.json, .gitignore, and CODEOWNERS updated - .meta-updater/src/index.ts literals repointed (pnpm11/pnpm/package.json, pnpm11/__utils__, pnpm11/__typings__, and the main package directory) - regenerated every moved package's repository/homepage URL via meta-updater - pnpm11/pnpm/bundle-deps.ts and __utils__/scripts/src/typecheck-only.ts climb one more level to reach the repo root .meta-updater stays at the repo root because @pnpm/meta-updater resolves its config at <cwd>/.meta-updater/main.mjs. TS CI (.github/workflows/ci.yml) now only runs when pnpm11/-relevant paths change, via a dorny/paths-filter changes job plus a TS CI / Success aggregate gate; branch protection should require only that gate.
43 lines
1.5 KiB
TypeScript
43 lines
1.5 KiB
TypeScript
import fs from 'node:fs'
|
|
import os from 'node:os'
|
|
import path from 'node:path'
|
|
|
|
import { expect, test } from '@jest/globals'
|
|
|
|
import { getGitBranchLockfileNames, getGitBranchLockfileNamesSync } from '../lib/gitBranchLockfile.js'
|
|
|
|
process.chdir(import.meta.dirname)
|
|
|
|
test('getGitBranchLockfileNames()', async () => {
|
|
const lockfileDir: string = path.join('fixtures', '6')
|
|
const gitBranchLockfileNames = await getGitBranchLockfileNames(lockfileDir)
|
|
expect(gitBranchLockfileNames).toEqual(['pnpm-lock.branch.yaml'])
|
|
})
|
|
|
|
test('getGitBranchLockfileNamesSync()', () => {
|
|
const lockfileDir: string = path.join('fixtures', '6')
|
|
expect(getGitBranchLockfileNamesSync(lockfileDir)).toEqual(['pnpm-lock.branch.yaml'])
|
|
})
|
|
|
|
test('git-branch lockfile matcher requires literal dots and a branch segment', () => {
|
|
const lockfileDir = fs.mkdtempSync(path.join(os.tmpdir(), 'pnpm-git-branch-lockfile-'))
|
|
try {
|
|
for (const name of [
|
|
'pnpm-lock.main.yaml', // branch lockfile
|
|
'pnpm-lock.feature.x.yaml', // branch name containing a dot
|
|
'pnpm-lock.yaml', // base lockfile, not a branch lockfile
|
|
'pnpm-lock-main-yaml', // no literal dots
|
|
'my-pnpm-lock.main.yaml', // does not start at the beginning
|
|
'README.md',
|
|
]) {
|
|
fs.writeFileSync(path.join(lockfileDir, name), '')
|
|
}
|
|
expect(getGitBranchLockfileNamesSync(lockfileDir).sort()).toEqual([
|
|
'pnpm-lock.feature.x.yaml',
|
|
'pnpm-lock.main.yaml',
|
|
])
|
|
} finally {
|
|
fs.rmSync(lockfileDir, { force: true, recursive: true })
|
|
}
|
|
})
|