@brillout/test-e2e 0.5.26 → 0.5.27

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.
@@ -34,7 +34,7 @@ function tolerateErrorBuiltIn({ logSource, logText }) {
34
34
  logText: 'The service was stopped: write EPIPE',
35
35
  logSource: 'stderr',
36
36
  },
37
- /* Ignore Chrome logging warning when it cannot do its creepy tracking: https://stackoverflow.com/questions/69619035/error-with-permissions-policy-header-unrecognized-feature-interest-cohort/75119417#75119417
37
+ /* Ignore Chrome logging warning when it cannot do its creepy tracking: https://stackoverflow.com/questions/69619035/error-with-permissions-policy-header-unrecognized-feature-interest-cohort
38
38
  ```
39
39
  [15:57:20.273][/test/abort/test-dev-server.test.ts][npm run dev:server][Browser Warning] {
40
40
  "type": "warning",
@@ -7,10 +7,8 @@ const verbose = (0, parseCli_1.check)('--verbose');
7
7
  const inspect = (0, parseCli_1.check)('--inspect');
8
8
  const debugEsbuild = (0, parseCli_1.check)('--debug-esbuild');
9
9
  const bail = (0, parseCli_1.check)('--bail');
10
- /* Defined in ./findFiles.ts
11
- * I don't think we use the --exclude option anymore? Can we remove it?
12
- const exclude = check('--exclude')
13
- */
10
+ // Defined & used in ./findFiles.ts
11
+ const exclude = (0, parseCli_1.check)('--exclude');
14
12
  (0, parseCli_1.validate)();
15
13
  const cliOptions = {
16
14
  verbose,
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@brillout/test-e2e",
3
- "version": "0.5.26",
3
+ "version": "0.5.27",
4
4
  "bin": "./bin.js",
5
5
  "main": "./dist/index.js",
6
6
  "scripts": {