@riebeckite/test 0.0.6
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/LICENSE +201 -0
- package/README.md +88 -0
- package/README_ja.md +69 -0
- package/dist/e2e/assertions.d.ts +63 -0
- package/dist/e2e/cli.d.ts +23 -0
- package/dist/e2e/files.d.ts +7 -0
- package/dist/e2e/format.d.ts +5 -0
- package/dist/e2e/html.d.ts +10 -0
- package/dist/e2e/index.d.ts +20 -0
- package/dist/e2e/index.js +573 -0
- package/dist/e2e/logger.d.ts +18 -0
- package/dist/e2e/pack.d.ts +30 -0
- package/dist/e2e/process.d.ts +34 -0
- package/dist/e2e/run.d.ts +100 -0
- package/dist/e2e/stage.d.ts +55 -0
- package/dist/golden.d.ts +22 -0
- package/dist/index.d.ts +11 -0
- package/dist/index.js +40 -0
- package/package.json +59 -0
package/LICENSE
ADDED
|
@@ -0,0 +1,201 @@
|
|
|
1
|
+
Apache License
|
|
2
|
+
Version 2.0, January 2004
|
|
3
|
+
http://www.apache.org/licenses/
|
|
4
|
+
|
|
5
|
+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
|
6
|
+
|
|
7
|
+
1. Definitions.
|
|
8
|
+
|
|
9
|
+
"License" shall mean the terms and conditions for use, reproduction,
|
|
10
|
+
and distribution as defined by Sections 1 through 9 of this document.
|
|
11
|
+
|
|
12
|
+
"Licensor" shall mean the copyright owner or entity authorized by
|
|
13
|
+
the copyright owner that is granting the License.
|
|
14
|
+
|
|
15
|
+
"Legal Entity" shall mean the union of the acting entity and all
|
|
16
|
+
other entities that control, are controlled by, or are under common
|
|
17
|
+
control with that entity. For the purposes of this definition,
|
|
18
|
+
"control" means (i) the power, direct or indirect, to cause the
|
|
19
|
+
direction or management of such entity, whether by contract or
|
|
20
|
+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
|
21
|
+
outstanding shares, or (iii) beneficial ownership of such entity.
|
|
22
|
+
|
|
23
|
+
"You" (or "Your") shall mean an individual or Legal Entity
|
|
24
|
+
exercising permissions granted by this License.
|
|
25
|
+
|
|
26
|
+
"Source" form shall mean the preferred form for making modifications,
|
|
27
|
+
including but not limited to software source code, documentation
|
|
28
|
+
source, and configuration files.
|
|
29
|
+
|
|
30
|
+
"Object" form shall mean any form resulting from mechanical
|
|
31
|
+
transformation or translation of a Source form, including but
|
|
32
|
+
not limited to compiled object code, generated documentation,
|
|
33
|
+
and conversions to other media types.
|
|
34
|
+
|
|
35
|
+
"Work" shall mean the work of authorship, whether in Source or
|
|
36
|
+
Object form, made available under the License, as indicated by a
|
|
37
|
+
copyright notice that is included in or attached to the work
|
|
38
|
+
(an example is provided in the Appendix below).
|
|
39
|
+
|
|
40
|
+
"Derivative Works" shall mean any work, whether in Source or Object
|
|
41
|
+
form, that is based on (or derived from) the Work and for which the
|
|
42
|
+
editorial revisions, annotations, elaborations, or other modifications
|
|
43
|
+
represent, as a whole, an original work of authorship. For the purposes
|
|
44
|
+
of this License, Derivative Works shall not include works that remain
|
|
45
|
+
separable from, or merely link (or bind by name) to the interfaces of,
|
|
46
|
+
the Work and Derivative Works thereof.
|
|
47
|
+
|
|
48
|
+
"Contribution" shall mean any work of authorship, including
|
|
49
|
+
the original version of the Work and any modifications or additions
|
|
50
|
+
to that Work or Derivative Works thereof, that is intentionally
|
|
51
|
+
submitted to Licensor for inclusion in the Work by the copyright owner
|
|
52
|
+
or by an individual or Legal Entity authorized to submit on behalf of
|
|
53
|
+
the copyright owner. For the purposes of this definition, "submitted"
|
|
54
|
+
means any form of electronic, verbal, or written communication sent
|
|
55
|
+
to the Licensor or its representatives, including but not limited to
|
|
56
|
+
communication on electronic mailing lists, source code control systems,
|
|
57
|
+
and issue tracking systems that are managed by, or on behalf of, the
|
|
58
|
+
Licensor for the purpose of discussing and improving the Work, but
|
|
59
|
+
excluding communication that is conspicuously marked or otherwise
|
|
60
|
+
designated in writing by the copyright owner as "Not a Contribution."
|
|
61
|
+
|
|
62
|
+
"Contributor" shall mean Licensor and any individual or Legal Entity
|
|
63
|
+
on behalf of whom a Contribution has been received by Licensor and
|
|
64
|
+
subsequently incorporated within the Work.
|
|
65
|
+
|
|
66
|
+
2. Grant of Copyright License. Subject to the terms and conditions of
|
|
67
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
68
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
69
|
+
copyright license to reproduce, prepare Derivative Works of,
|
|
70
|
+
publicly display, publicly perform, sublicense, and distribute the
|
|
71
|
+
Work and such Derivative Works in Source or Object form.
|
|
72
|
+
|
|
73
|
+
3. Grant of Patent License. Subject to the terms and conditions of
|
|
74
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
75
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
76
|
+
(except as stated in this section) patent license to make, have made,
|
|
77
|
+
use, offer to sell, sell, import, and otherwise transfer the Work,
|
|
78
|
+
where such license applies only to those patent claims licensable
|
|
79
|
+
by such Contributor that are necessarily infringed by their
|
|
80
|
+
Contribution(s) alone or by combination of their Contribution(s)
|
|
81
|
+
with the Work to which such Contribution(s) was submitted. If You
|
|
82
|
+
institute patent litigation against any entity (including a
|
|
83
|
+
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
|
84
|
+
or a Contribution incorporated within the Work constitutes direct
|
|
85
|
+
or contributory patent infringement, then any patent licenses
|
|
86
|
+
granted to You under this License for that Work shall terminate
|
|
87
|
+
as of the date such litigation is filed.
|
|
88
|
+
|
|
89
|
+
4. Redistribution. You may reproduce and distribute copies of the
|
|
90
|
+
Work or Derivative Works thereof in any medium, with or without
|
|
91
|
+
modifications, and in Source or Object form, provided that You
|
|
92
|
+
meet the following conditions:
|
|
93
|
+
|
|
94
|
+
(a) You must give any other recipients of the Work or
|
|
95
|
+
Derivative Works a copy of this License; and
|
|
96
|
+
|
|
97
|
+
(b) You must cause any modified files to carry prominent notices
|
|
98
|
+
stating that You changed the files; and
|
|
99
|
+
|
|
100
|
+
(c) You must retain, in the Source form of any Derivative Works
|
|
101
|
+
that You distribute, all copyright, patent, trademark, and
|
|
102
|
+
attribution notices from the Source form of the Work,
|
|
103
|
+
excluding those notices that do not pertain to any part of
|
|
104
|
+
the Derivative Works; and
|
|
105
|
+
|
|
106
|
+
(d) If the Work includes a "NOTICE" text file as part of its
|
|
107
|
+
distribution, then any Derivative Works that You distribute must
|
|
108
|
+
include a readable copy of the attribution notices contained
|
|
109
|
+
within such NOTICE file, excluding those notices that do not
|
|
110
|
+
pertain to any part of the Derivative Works, in at least one
|
|
111
|
+
of the following places: within a NOTICE text file distributed
|
|
112
|
+
as part of the Derivative Works; within the Source form or
|
|
113
|
+
documentation, if provided along with the Derivative Works; or,
|
|
114
|
+
within a display generated by the Derivative Works, if and
|
|
115
|
+
wherever such third-party notices normally appear. The contents
|
|
116
|
+
of the NOTICE file are for informational purposes only and
|
|
117
|
+
do not modify the License. You may add Your own attribution
|
|
118
|
+
notices within Derivative Works that You distribute, alongside
|
|
119
|
+
or as an addendum to the NOTICE text from the Work, provided
|
|
120
|
+
that such additional attribution notices cannot be construed
|
|
121
|
+
as modifying the License.
|
|
122
|
+
|
|
123
|
+
You may add Your own copyright statement to Your modifications and
|
|
124
|
+
may provide additional or different license terms and conditions
|
|
125
|
+
for use, reproduction, or distribution of Your modifications, or
|
|
126
|
+
for any such Derivative Works as a whole, provided Your use,
|
|
127
|
+
reproduction, and distribution of the Work otherwise complies with
|
|
128
|
+
the conditions stated in this License.
|
|
129
|
+
|
|
130
|
+
5. Submission of Contributions. Unless You explicitly state otherwise,
|
|
131
|
+
any Contribution intentionally submitted for inclusion in the Work
|
|
132
|
+
by You to the Licensor shall be under the terms and conditions of
|
|
133
|
+
this License, without any additional terms or conditions.
|
|
134
|
+
Notwithstanding the above, nothing herein shall supersede or modify
|
|
135
|
+
the terms of any separate license agreement you may have executed
|
|
136
|
+
with Licensor regarding such Contributions.
|
|
137
|
+
|
|
138
|
+
6. Trademarks. This License does not grant permission to use the trade
|
|
139
|
+
names, trademarks, service marks, or product names of the Licensor,
|
|
140
|
+
except as required for reasonable and customary use in describing the
|
|
141
|
+
origin of the Work and reproducing the content of the NOTICE file.
|
|
142
|
+
|
|
143
|
+
7. Disclaimer of Warranty. Unless required by applicable law or
|
|
144
|
+
agreed to in writing, Licensor provides the Work (and each
|
|
145
|
+
Contributor provides its Contributions) on an "AS IS" BASIS,
|
|
146
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
|
147
|
+
implied, including, without limitation, any warranties or conditions
|
|
148
|
+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
|
149
|
+
PARTICULAR PURPOSE. You are solely responsible for determining the
|
|
150
|
+
appropriateness of using or redistributing the Work and assume any
|
|
151
|
+
risks associated with Your exercise of permissions under this License.
|
|
152
|
+
|
|
153
|
+
8. Limitation of Liability. In no event and under no legal theory,
|
|
154
|
+
whether in tort (including negligence), contract, or otherwise,
|
|
155
|
+
unless required by applicable law (such as deliberate and grossly
|
|
156
|
+
negligent acts) or agreed to in writing, shall any Contributor be
|
|
157
|
+
liable to You for damages, including any direct, indirect, special,
|
|
158
|
+
incidental, or consequential damages of any character arising as a
|
|
159
|
+
result of this License or out of the use or inability to use the
|
|
160
|
+
Work (including but not limited to damages for loss of goodwill,
|
|
161
|
+
work stoppage, computer failure or malfunction, or any and all
|
|
162
|
+
other commercial damages or losses), even if such Contributor
|
|
163
|
+
has been advised of the possibility of such damages.
|
|
164
|
+
|
|
165
|
+
9. Accepting Warranty or Additional Liability. While redistributing
|
|
166
|
+
the Work or Derivative Works thereof, You may choose to offer,
|
|
167
|
+
and charge a fee for, acceptance of support, warranty, indemnity,
|
|
168
|
+
or other liability obligations and/or rights consistent with this
|
|
169
|
+
License. However, in accepting such obligations, You may act only
|
|
170
|
+
on Your own behalf and on Your sole responsibility, not on behalf
|
|
171
|
+
of any other Contributor, and only if You agree to indemnify,
|
|
172
|
+
defend, and hold each Contributor harmless for any liability
|
|
173
|
+
incurred by, or claims asserted against, such Contributor by reason
|
|
174
|
+
of your accepting any such warranty or additional liability.
|
|
175
|
+
|
|
176
|
+
END OF TERMS AND CONDITIONS
|
|
177
|
+
|
|
178
|
+
APPENDIX: How to apply the Apache License to your work.
|
|
179
|
+
|
|
180
|
+
To apply the Apache License to your work, attach the following
|
|
181
|
+
boilerplate notice, with the fields enclosed by brackets "[]"
|
|
182
|
+
replaced with your own identifying information. (Don't include
|
|
183
|
+
the brackets!) The text should be enclosed in the appropriate
|
|
184
|
+
comment syntax for the file format. We also recommend that a
|
|
185
|
+
file or class name and description of purpose be included on the
|
|
186
|
+
same "printed page" as the copyright notice for easier
|
|
187
|
+
identification within third-party archives.
|
|
188
|
+
|
|
189
|
+
Copyright Rerurate_514
|
|
190
|
+
|
|
191
|
+
Licensed under the Apache License, Version 2.0 (the "License");
|
|
192
|
+
you may not use this file except in compliance with the License.
|
|
193
|
+
You may obtain a copy of the License at
|
|
194
|
+
|
|
195
|
+
http://www.apache.org/licenses/LICENSE-2.0
|
|
196
|
+
|
|
197
|
+
Unless required by applicable law or agreed to in writing, software
|
|
198
|
+
distributed under the License is distributed on an "AS IS" BASIS,
|
|
199
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
200
|
+
See the License for the specific language governing permissions and
|
|
201
|
+
limitations under the License.
|
package/README.md
ADDED
|
@@ -0,0 +1,88 @@
|
|
|
1
|
+
# @riebeckite/test
|
|
2
|
+
|
|
3
|
+
Shared test utilities for Riebeckite packages, plus a generic external-consumer
|
|
4
|
+
end-to-end engine.
|
|
5
|
+
|
|
6
|
+
[日本語](./README_ja.md)
|
|
7
|
+
|
|
8
|
+
## Overview
|
|
9
|
+
|
|
10
|
+
`@riebeckite/test` has two entry points:
|
|
11
|
+
|
|
12
|
+
- `@riebeckite/test` — dependency-free helpers for package unit tests.
|
|
13
|
+
- `@riebeckite/test/e2e` — a reusable engine for testing a built site end to
|
|
14
|
+
end against published tarballs. It knows nothing about the Riebeckite
|
|
15
|
+
monorepo: the repository root, the package list, the fixtures, and the
|
|
16
|
+
content assertions are all supplied by the caller.
|
|
17
|
+
|
|
18
|
+
## Installation
|
|
19
|
+
|
|
20
|
+
```sh
|
|
21
|
+
pnpm add -D @riebeckite/test
|
|
22
|
+
```
|
|
23
|
+
|
|
24
|
+
## Unit-test helpers
|
|
25
|
+
|
|
26
|
+
`assertGolden` and `assertGoldenJson` record expensive output as committed
|
|
27
|
+
golden files instead of asserting it by hand. Node's built-in snapshot
|
|
28
|
+
assertion needs Node 22.3+, but Riebeckite supports Node 20.19+, so this helper
|
|
29
|
+
covers the supported range.
|
|
30
|
+
|
|
31
|
+
```ts
|
|
32
|
+
import { assertGolden, assertGoldenJson } from "@riebeckite/test";
|
|
33
|
+
|
|
34
|
+
assertGolden(renderHtml(), new URL("./__golden__/page.html", import.meta.url));
|
|
35
|
+
assertGoldenJson(manifest, new URL("./__golden__/manifest.json", import.meta.url));
|
|
36
|
+
```
|
|
37
|
+
|
|
38
|
+
The helpers normalize CRLF/CR to LF and collapse trailing newlines by default so
|
|
39
|
+
golden files stay stable across platforms and editors. Pass
|
|
40
|
+
`{ normalize: false }` when byte-exact output matters, and `{ message }` to add
|
|
41
|
+
context to failures.
|
|
42
|
+
|
|
43
|
+
A missing or mismatched golden file fails the test. Regenerate the recorded
|
|
44
|
+
files with `pnpm test:update` at the repository root (or `UPDATE_GOLDEN=1` for a
|
|
45
|
+
single package) and review the resulting diff.
|
|
46
|
+
|
|
47
|
+
See [Testing](../../docs/en/testing.md) for the full workflow.
|
|
48
|
+
|
|
49
|
+
## External-site engine
|
|
50
|
+
|
|
51
|
+
`@riebeckite/test/e2e` packages a set of workspace packages into tarballs,
|
|
52
|
+
installs them into an empty consumer project alongside a fixture site, and runs
|
|
53
|
+
assertions against the result. Nothing about the monorepo is hardcoded.
|
|
54
|
+
|
|
55
|
+
```ts
|
|
56
|
+
import path from "node:path";
|
|
57
|
+
|
|
58
|
+
import { runExternalSiteE2E } from "@riebeckite/test/e2e";
|
|
59
|
+
|
|
60
|
+
await runExternalSiteE2E({
|
|
61
|
+
repoRoot,
|
|
62
|
+
packages: [{ directory: "packages/core", name: "@riebeckite/core" }],
|
|
63
|
+
fixture: { site: fixtureSite, vault: fixtureVault },
|
|
64
|
+
dependencyCheckScript: path.join(repoRoot, "scripts/check_dependencies.mjs"),
|
|
65
|
+
scope: "@riebeckite",
|
|
66
|
+
cliName: "riebeckite",
|
|
67
|
+
resolveCliEntry: (siteDir) =>
|
|
68
|
+
path.join(siteDir, "node_modules", "@riebeckite", "cli", "bin", "riebeckite.mjs"),
|
|
69
|
+
cliCommands: [{ args: ["build"] }],
|
|
70
|
+
keepEnv: "RIEBECKITE_E2E_KEEP",
|
|
71
|
+
assertions: {
|
|
72
|
+
buildOutput: (siteDir, vaultDir) => {
|
|
73
|
+
// assert on the built site
|
|
74
|
+
},
|
|
75
|
+
},
|
|
76
|
+
});
|
|
77
|
+
```
|
|
78
|
+
|
|
79
|
+
The engine also exports the lower-level steps it is built from —
|
|
80
|
+
`run`/`runAsync` for spawning commands, `packPackages` for tarball creation,
|
|
81
|
+
`stageIsolatedSite` for building the consumer project, and the install and
|
|
82
|
+
artifact assertions — so a repository can compose its own flow. Work that does
|
|
83
|
+
not generalize, such as generating a starter site from the packed tarballs, runs
|
|
84
|
+
through the `afterSiteChecks` callback.
|
|
85
|
+
|
|
86
|
+
## See also
|
|
87
|
+
|
|
88
|
+
- [Testing](../../docs/en/testing.md)
|
package/README_ja.md
ADDED
|
@@ -0,0 +1,69 @@
|
|
|
1
|
+
# @riebeckite/test
|
|
2
|
+
|
|
3
|
+
Riebeckite パッケージ共通のテストユーティリティと、汎用の external-consumer E2E engine です。
|
|
4
|
+
|
|
5
|
+
[English](./README.md)
|
|
6
|
+
|
|
7
|
+
## 概要
|
|
8
|
+
|
|
9
|
+
`@riebeckite/test` には 2 つのエントリポイントがあります。
|
|
10
|
+
|
|
11
|
+
- `@riebeckite/test` — パッケージの単体テスト向けの依存ゼロ helper。
|
|
12
|
+
- `@riebeckite/test/e2e` — ビルド済みサイトを公開 tarball に対して end-to-end で検証する再利用可能な engine。Riebeckite モノレポを一切知りません。リポジトリルート、パッケージ一覧、fixture、コンテンツのアサーションはすべて呼び出し側が渡します。
|
|
13
|
+
|
|
14
|
+
## インストール
|
|
15
|
+
|
|
16
|
+
```sh
|
|
17
|
+
pnpm add -D @riebeckite/test
|
|
18
|
+
```
|
|
19
|
+
|
|
20
|
+
## 単体テストの helper
|
|
21
|
+
|
|
22
|
+
`assertGolden` と `assertGoldenJson` は、手で書くには大きすぎる出力を committed な golden ファイルとして記録します。Node 標準の snapshot 機能は Node 22.3+ が必要ですが、Riebeckite は Node 20.19+ をサポートするため、この helper が対応範囲をカバーします。
|
|
23
|
+
|
|
24
|
+
```ts
|
|
25
|
+
import { assertGolden, assertGoldenJson } from "@riebeckite/test";
|
|
26
|
+
|
|
27
|
+
assertGolden(renderHtml(), new URL("./__golden__/page.html", import.meta.url));
|
|
28
|
+
assertGoldenJson(manifest, new URL("./__golden__/manifest.json", import.meta.url));
|
|
29
|
+
```
|
|
30
|
+
|
|
31
|
+
既定では CRLF/CR を LF に変換し、末尾の改行を 1 つにまとめるため、golden ファイルはプラットフォームやエディタをまたいで安定します。バイト単位で一致させたい場合は `{ normalize: false }`、失敗時に文脈を足したい場合は `{ message }` を渡してください。
|
|
32
|
+
|
|
33
|
+
golden ファイルが無い、または一致しない場合はテストが失敗します。リポジトリルートで `pnpm test:update`(単一パッケージなら `UPDATE_GOLDEN=1`)を実行して記録を更新し、差分を確認してください。
|
|
34
|
+
|
|
35
|
+
詳しいワークフローは [Testing](../../docs/ja/testing.md) を参照してください。
|
|
36
|
+
|
|
37
|
+
## External-site engine
|
|
38
|
+
|
|
39
|
+
`@riebeckite/test/e2e` は、複数のワークスペースパッケージを tarball にまとめ、空の consumer プロジェクト(fixture サイト付き)にインストールし、結果に対してアサーションを実行します。モノレポ固有の情報はハードコードしません。
|
|
40
|
+
|
|
41
|
+
```ts
|
|
42
|
+
import path from "node:path";
|
|
43
|
+
|
|
44
|
+
import { runExternalSiteE2E } from "@riebeckite/test/e2e";
|
|
45
|
+
|
|
46
|
+
await runExternalSiteE2E({
|
|
47
|
+
repoRoot,
|
|
48
|
+
packages: [{ directory: "packages/core", name: "@riebeckite/core" }],
|
|
49
|
+
fixture: { site: fixtureSite, vault: fixtureVault },
|
|
50
|
+
dependencyCheckScript: path.join(repoRoot, "scripts/check_dependencies.mjs"),
|
|
51
|
+
scope: "@riebeckite",
|
|
52
|
+
cliName: "riebeckite",
|
|
53
|
+
resolveCliEntry: (siteDir) =>
|
|
54
|
+
path.join(siteDir, "node_modules", "@riebeckite", "cli", "bin", "riebeckite.mjs"),
|
|
55
|
+
cliCommands: [{ args: ["build"] }],
|
|
56
|
+
keepEnv: "RIEBECKITE_E2E_KEEP",
|
|
57
|
+
assertions: {
|
|
58
|
+
buildOutput: (siteDir, vaultDir) => {
|
|
59
|
+
// ビルド済みサイトに対するアサーション
|
|
60
|
+
},
|
|
61
|
+
},
|
|
62
|
+
});
|
|
63
|
+
```
|
|
64
|
+
|
|
65
|
+
engine は、それが組み立てられている下位ステップも公開します。コマンド実行の `run` / `runAsync`、tarball 作成の `packPackages`、consumer プロジェクトを組み立てる `stageIsolatedSite`、インストールと成果物のアサーションなどです。リポジトリ側で独自のフローを構成できます。一般化できない処理(たとえば packed tarball から starter サイトを生成するなど)は `afterSiteChecks` コールバックで実行します。
|
|
66
|
+
|
|
67
|
+
## 関連資料
|
|
68
|
+
|
|
69
|
+
- [Testing](../../docs/ja/testing.md)
|
|
@@ -0,0 +1,63 @@
|
|
|
1
|
+
import type { Logger } from "./logger.js";
|
|
2
|
+
/** A path that must exist after installation, with its failure message. */
|
|
3
|
+
export interface RequiredInstallPath {
|
|
4
|
+
/** Label used in the success line, e.g. `"vite/client"`. */
|
|
5
|
+
label: string;
|
|
6
|
+
/** Path relative to the site directory. */
|
|
7
|
+
relativePath: string;
|
|
8
|
+
/** Message thrown when the path is missing. */
|
|
9
|
+
missingMessage: string;
|
|
10
|
+
/** Include the path in the success line. Defaults to true. */
|
|
11
|
+
report?: boolean;
|
|
12
|
+
}
|
|
13
|
+
export interface AssertIsolatedInstallOptions {
|
|
14
|
+
/** Absolute repository root the workspace must live outside of. */
|
|
15
|
+
repoRoot: string;
|
|
16
|
+
/** Paths that must exist inside the isolated install. */
|
|
17
|
+
requiredPaths?: readonly RequiredInstallPath[];
|
|
18
|
+
logger: Logger;
|
|
19
|
+
}
|
|
20
|
+
/**
|
|
21
|
+
* Verify the install is genuinely standalone: the workspace lives outside the
|
|
22
|
+
* repository, no pnpm workspace state leaked in, and the locally installed
|
|
23
|
+
* tooling the type-check phase depends on is present.
|
|
24
|
+
*/
|
|
25
|
+
export declare function assertIsolatedInstall(siteDir: string, tempRoot: string, options: AssertIsolatedInstallOptions): void;
|
|
26
|
+
export interface AssertNoMonorepoEscapeHatchesOptions {
|
|
27
|
+
/**
|
|
28
|
+
* Directory under the repository root that site sources must not reach into
|
|
29
|
+
* via a relative parent traversal. Defaults to `"packages"`.
|
|
30
|
+
*/
|
|
31
|
+
monorepoPackagesDirectory?: string;
|
|
32
|
+
logger: Logger;
|
|
33
|
+
}
|
|
34
|
+
/**
|
|
35
|
+
* Fail if the staged site contains any way to escape into the repository:
|
|
36
|
+
* `workspace:` protocol references, a copied package directory, or source
|
|
37
|
+
* files that traverse into the monorepo's package directory.
|
|
38
|
+
*/
|
|
39
|
+
export declare function assertNoMonorepoEscapeHatches(siteDir: string, options: AssertNoMonorepoEscapeHatchesOptions): void;
|
|
40
|
+
export interface AssertPublishedArtifactsOptions {
|
|
41
|
+
/** Absolute repository root published packages must not resolve into. */
|
|
42
|
+
repoRoot: string;
|
|
43
|
+
/** Published package scope, e.g. `"@scope"`. */
|
|
44
|
+
scope: string;
|
|
45
|
+
logger: Logger;
|
|
46
|
+
}
|
|
47
|
+
/**
|
|
48
|
+
* Verify every installed scoped package resolves to a real installed directory
|
|
49
|
+
* outside the repository (never a symlink back into the monorepo).
|
|
50
|
+
*/
|
|
51
|
+
export declare function assertPublishedArtifacts(siteDir: string, options: AssertPublishedArtifactsOptions): void;
|
|
52
|
+
export interface AssertDeclaredDependenciesOptions {
|
|
53
|
+
/** Absolute path to the undeclared-dependency checker script. */
|
|
54
|
+
dependencyCheckScript: string;
|
|
55
|
+
/** Working directory for the checker. Defaults to `process.cwd()`. */
|
|
56
|
+
cwd?: string;
|
|
57
|
+
logger: Logger;
|
|
58
|
+
}
|
|
59
|
+
/**
|
|
60
|
+
* Run the repository's dependency checker against the site so it cannot
|
|
61
|
+
* silently rely on hoisted (undeclared) packages.
|
|
62
|
+
*/
|
|
63
|
+
export declare function assertDeclaredDependencies(siteDir: string, options: AssertDeclaredDependenciesOptions): void;
|
|
@@ -0,0 +1,23 @@
|
|
|
1
|
+
import type { Logger } from "./logger.js";
|
|
2
|
+
import { type RunResult } from "./process.js";
|
|
3
|
+
export interface RunCliOptions {
|
|
4
|
+
/** Absolute path to the installed CLI entry point. */
|
|
5
|
+
cliEntry: string;
|
|
6
|
+
/** Working directory for the invocation. */
|
|
7
|
+
cwd: string;
|
|
8
|
+
/** Name shown in the step line, e.g. `"riebeckite"`. */
|
|
9
|
+
cliName: string;
|
|
10
|
+
logger: Logger;
|
|
11
|
+
}
|
|
12
|
+
/**
|
|
13
|
+
* Invoke an installed CLI entry with `args`, print its combined output, and
|
|
14
|
+
* return the raw result. The step line reads `<cliName> <args...>`.
|
|
15
|
+
*/
|
|
16
|
+
export declare function runCli(args: readonly string[], options: RunCliOptions): RunResult;
|
|
17
|
+
/** Combined stdout and stderr of a run. */
|
|
18
|
+
export declare function cliText(result: RunResult): string;
|
|
19
|
+
/**
|
|
20
|
+
* Type-check the site with its locally installed TypeScript compiler. The
|
|
21
|
+
* command matches `<typescript>/bin/tsc --noEmit -p <project>`.
|
|
22
|
+
*/
|
|
23
|
+
export declare function runTypecheck(siteDir: string, project: string, logger: Logger): RunResult;
|
|
@@ -0,0 +1,7 @@
|
|
|
1
|
+
/** Predicate applied to each candidate file's absolute path. */
|
|
2
|
+
export type FilePredicate = (absolutePath: string) => boolean;
|
|
3
|
+
/**
|
|
4
|
+
* Recursively list the files under `root` that satisfy `predicate`. Missing
|
|
5
|
+
* roots yield an empty list instead of throwing.
|
|
6
|
+
*/
|
|
7
|
+
export declare function walkFiles(root: string, predicate?: FilePredicate): string[];
|
|
@@ -0,0 +1,10 @@
|
|
|
1
|
+
/** Escape a string so it can be embedded literally in a `RegExp`. */
|
|
2
|
+
export declare function escapeRegExp(value: string): string;
|
|
3
|
+
/**
|
|
4
|
+
* Extract the textual bodies of `<script>` elements that carry `attribute`
|
|
5
|
+
* (for example `"data-rb-hover-preview"`), joined with newlines.
|
|
6
|
+
*
|
|
7
|
+
* Generic on purpose: the caller supplies the attribute name so the engine
|
|
8
|
+
* never hardcodes a fixture marker.
|
|
9
|
+
*/
|
|
10
|
+
export declare function extractScriptPayloads(html: string, attribute: string): string;
|
|
@@ -0,0 +1,20 @@
|
|
|
1
|
+
/**
|
|
2
|
+
* A reusable, monorepo-agnostic engine for testing a built site end to end
|
|
3
|
+
* against locally packed tarballs.
|
|
4
|
+
*
|
|
5
|
+
* The engine owns the mechanical sequence and knows nothing about any specific
|
|
6
|
+
* repository. Callers inject the repository root, package list, fixtures, CLI
|
|
7
|
+
* shape, assertion callbacks, and keep-temp variable through
|
|
8
|
+
* {@link runExternalSiteE2E}. Lower-level primitives are exported so a
|
|
9
|
+
* repository can compose its own flow.
|
|
10
|
+
*/
|
|
11
|
+
export { type AssertDeclaredDependenciesOptions, type AssertIsolatedInstallOptions, type AssertNoMonorepoEscapeHatchesOptions, type AssertPublishedArtifactsOptions, assertDeclaredDependencies, assertIsolatedInstall, assertNoMonorepoEscapeHatches, assertPublishedArtifacts, type RequiredInstallPath, } from "./assertions.js";
|
|
12
|
+
export { cliText, type RunCliOptions, runCli, runTypecheck, } from "./cli.js";
|
|
13
|
+
export { type FilePredicate, walkFiles, } from "./files.js";
|
|
14
|
+
export { formatBytes } from "./format.js";
|
|
15
|
+
export { escapeRegExp, extractScriptPayloads } from "./html.js";
|
|
16
|
+
export { createLogger, type Logger } from "./logger.js";
|
|
17
|
+
export { type PackageSpec, type PackedPackage, type PackedPackages, type PackPackagesOptions, packPackages, } from "./pack.js";
|
|
18
|
+
export { MAX_BUFFER, quote, type RunOptions, type RunResult, run, runAsync, } from "./process.js";
|
|
19
|
+
export { type CliCommandSpec, type ExternalSiteAssertions, type ExternalSiteE2EConfig, type ExternalSiteFixture, type ExternalSiteWorkspace, runExternalSiteE2E, type SiteCheck, } from "./run.js";
|
|
20
|
+
export { type LayerExternalConsumerTypesOptions, layerExternalConsumerTypes, type NodeNextProjectSpec, type StageIsolatedSiteOptions, stageIsolatedSite, writeFileDependencies, } from "./stage.js";
|