Zoltan Kochan
fc2f33912e
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.
21 lines
780 B
TypeScript
21 lines
780 B
TypeScript
import { expect, test } from '@jest/globals'
|
|
import { extractComments, insertComments } from '@pnpm/text.comments-parser'
|
|
|
|
test('extract and insert JSON5 comments', () => {
|
|
const json5WithComments = `/* This is an example of a package.json5 file with comments. */
|
|
{
|
|
/* pnpm should keep comments at the same indentation level */
|
|
name: 'foo',
|
|
version: '1.0.0', // it should keep in-line comments on the same line
|
|
// It should allow in-line comments with no other content
|
|
type: 'commonjs',
|
|
}
|
|
/* And it should preserve comments at the end of the file. Note no newline. */`
|
|
const { comments } = extractComments(json5WithComments)
|
|
expect(insertComments(`{
|
|
name: 'foo',
|
|
version: '1.0.0',
|
|
type: 'commonjs',
|
|
}`, comments!)).toBe(json5WithComments)
|
|
})
|