tape-six 1.7.10 → 1.7.11

package/README.md

@@ -419,6 +419,7 @@ Test output can be controlled by flags. See [Supported flags](https://github.com
 
 The most recent releases:
 
+- 1.7.11 _Documentation consistency: added missing sequential test commands to AI docs, fixed test glob references._
 - 1.7.10 _Switched from workflows to Agent Skills (agentskills.io) for consumer integration. Improved CJS import docs._
 - 1.7.9 _Merged test directories, fixed `.d.ts` typings, added `ts-check` to CI._
 - 1.7.8 _Bug fix: Deno stdout flush before exit to prevent truncated output._

package/TESTING.md

@@ -512,6 +512,8 @@ Flags control test output. Uppercase = enabled, lowercase = disabled.
 
 Common combinations: `FO` (failures only + stop at first), `FOT` (+ show time).
 
+When multiple `--flags` are given, the last one wins. To see which files are being run (overriding `--flags FO` from a script), append `--flags fo` — lowercase disables the flags.
+
 ### Environment variables
 
 - `TAPE6_FLAGS` — flags string (alternative to `--flags`).
@@ -541,7 +543,7 @@ Add to `package.json`:
 ```
 
 - `tests` — glob patterns for test files (relative to project root with leading `/`). Common for all environments.
-- `cli` — additional patterns for CLI-only environments (Node, Bun, Deno). Typically used for `.cjs` files.
+- `cli` — additional patterns for CLI-only environments (Node, Bun, Deno). Typically used for `.cjs` files that browsers cannot run. For CLI-only projects (no browser testing), it doesn't matter whether `.cjs` patterns go in `cli` or `tests` — all CLI runners handle both.
 - `node`, `deno`, `bun`, `browser` — additional patterns specific to a given environment. These are **not overrides** — they are added to `tests` (and `cli` for non-browser).
 - `importmap` — import map for browser testing (standard [import map](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/script/type/importmap) format).
 
@@ -745,6 +747,28 @@ test('MyClass', async t => {
 });
 ```
 
+### Writing a CommonJS test
+
+```cjs
+const {test} = require('tape-six');
+const {myFunction} = require('my-package');
+
+test('myFunction from CJS', t => {
+  t.equal(myFunction(1, 2), 3);
+});
+```
+
+If the module under test uses top-level `await`, `require()` cannot load it. Use `await import()` inside async tests instead:
+
+```cjs
+const {test} = require('tape-six');
+
+test('async module from CJS', async t => {
+  const {myFunction} = await import('my-async-package');
+  t.equal(myFunction(1, 2), 3);
+});
+```
+
 ### Verifying after writing tests
 
 ```bash

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "tape-six",
-  "version": "1.7.10",
+  "version": "1.7.11",
   "description": "TAP-based unit test library for Node, Deno, Bun, and browsers. ES modules, TypeScript, zero dependencies.",
   "type": "module",
   "main": "index.js",

package/skills/write-tests/SKILL.md

@@ -17,9 +17,9 @@ Write or update tests using the tape-six testing library.
 
 1. Read the testing guide at `node_modules/tape-six/TESTING.md` for API reference and patterns.
 2. Identify the module or feature to test. Read its source code to understand the public API.
-3. Create or update the test file in `tests/test-<name>.js` (or `.ts` for TypeScript projects):
-   - Import `test` from `tape-six` (ESM: `import test from 'tape-six'`; CJS: `const {test} = require('tape-six')` — named import is recommended for CommonJS).
-   - Import the module under test using the project's package name.
+3. Create or update the test file in `tests/test-<name>.js` (or `.ts` for TypeScript, `.cjs` for CommonJS):
+   - **ESM** (`.js`): `import test from 'tape-six'` and import the module under test using the project's package name.
+   - **CJS** (`.cjs`): `const {test} = require('tape-six')` and `const {...} = require('my-package')`. If the module under test uses top-level `await`, `require()` cannot load it — use `await import('my-package')` inside async tests instead.
    - Write one top-level `test()` per logical group.
    - Use embedded `await t.test()` for sub-cases.
    - Use `t.beforeEach`/`t.afterEach` for shared setup/teardown.
@@ -29,4 +29,5 @@ Write or update tests using the tape-six testing library.
 4. Run the new test file directly to verify: `node tests/test-<name>.js`
 5. Run the full test suite to check for regressions: `npm test`
    - If debugging, use `npm run test:seq` (runs sequentially, easier to trace issues).
+   - To see which files are being run, add `--flags fo` (overrides the default `--flags FO`).
 6. Report results and any failures.