ci(host): register globalThis.codeceptjs so deps don't need bare import

@codeceptjs/configure and @codeceptjs/expect-helper currently do top-level
\`import 'codeceptjs'\`, which can't resolve inside this repo's CI (the
project IS the codeceptjs package, so npm doesn't drop a node_modules
entry to resolve to). The CI symlink works around it; the proper fix is
to give those packages an in-process handle so they don't need to look
up codeceptjs through Node's bare-specifier resolution.

This change is the codeceptjs-side prep:

- lib/host.js — sets globalThis.codeceptjs = { config, container, event,
  output, recorder, Helper } as a side-effect on import. Idempotent;
  matches the global @codeceptjs/helper already consults
  (\`global.codeceptjs || require('codeceptjs')\`).
- lib/codecept.js + lib/plugin/browser.js — eager import of host.js so
  the registry is populated before the user's codecept.conf.js loads
  any companion package.

Once @codeceptjs/configure and @codeceptjs/expect-helper ship versions
that read from globalThis.codeceptjs (instead of \`import 'codeceptjs'\`),
the CI symlink can be removed. Drop-in replacements for both packages
are in scripts/upstream-patches/ — apply them upstream and bump versions
in package.json.

End-user projects are unaffected: globalThis.codeceptjs is set in normal
runs too, so the new code path is the same code path everyone takes.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: DavertMik

lib/codecept.js

@@ -32,6 +32,7 @@ import globalTimeoutListener from './listener/globalTimeout.js'
 import globalRetryListener from './listener/globalRetry.js'
 import exitListener from './listener/exit.js'
 import emptyRunListener from './listener/emptyRun.js'
+import './host.js'
 
 /**
  * CodeceptJS runner

lib/host.js

@@ -0,0 +1,19 @@
+import Helper from '@codeceptjs/helper'
+import Config from './config.js'
+import container from './container.js'
+import event from './event.js'
+import output from './output.js'
+import recorder from './recorder.js'
+
+// Register an in-process handle on globalThis so companion packages
+// (@codeceptjs/helper, @codeceptjs/configure, @codeceptjs/expect-helper) can
+// reach back into the running codeceptjs instance without doing a top-level
+// `import 'codeceptjs'`. End-user projects don't need this — `codeceptjs` is
+// in their node_modules and the bare-specifier import resolves normally — but
+// inside this repo's CI the project IS the codeceptjs package and there is
+// no node_modules/codeceptjs to resolve to.
+if (!globalThis.codeceptjs) {
+  globalThis.codeceptjs = { config: Config, container, event, output, recorder, Helper }
+}
+
+export default globalThis.codeceptjs

lib/plugin/browser.js

@@ -1,4 +1,5 @@
 import output from '../output.js'
+import '../host.js'
 
 /**
  * Overrides browser helper config from the command line. Works for all browser helpers

scripts/upstream-patches/README.md

@@ -0,0 +1,27 @@
+# Upstream patches
+
+Two CodeceptJS companion packages — `@codeceptjs/configure` and
+`@codeceptjs/expect-helper` — currently do top-level `import 'codeceptjs'`.
+Inside the codeceptjs repo's own CI that import fails because the project
+**is** the codeceptjs package, so npm doesn't drop a `node_modules/codeceptjs/`
+to resolve to. We currently work around it with a one-line CI step:
+
+```sh
+ln -sfn .. node_modules/codeceptjs
+```
+
+These two patches replace the bare `import 'codeceptjs'` in each package with
+a lazy lookup against `globalThis.codeceptjs` — the same in-process registry
+that CodeceptJS sets up in `lib/host.js`. Once both patches ship as new
+betas of their packages and the version bumps land in `package.json`, the CI
+symlink can be removed.
+
+Both patches are **purely additive for end-user projects** — `globalThis.codeceptjs`
+is set in either case (the framework writes it during startup), so the
+runtime behavior in a normal user setup is unchanged.
+
+## Apply
+
+- `configure-codeceptjs.js` → `@codeceptjs/configure/codeceptjs.js`
+- `expect-helper-index.js.diff` → patch for `@codeceptjs/expect-helper/index.js`
+  (the file is large; only the import block changes).

scripts/upstream-patches/configure-codeceptjs.js

@@ -0,0 +1,39 @@
+// Replacement for @codeceptjs/configure/codeceptjs.js
+//
+// CodeceptJS handle, looked up from the in-process registry the framework sets
+// on globalThis. Avoids a top-level `import 'codeceptjs'`, which fails to
+// resolve inside the codeceptjs repo's own CI (the project IS the codeceptjs
+// package). Each named export is a Proxy that forwards property access to the
+// live framework module at call time, so hooks register against the same
+// singletons the runner is using.
+
+function lazy(name) {
+  return new Proxy({}, {
+    get(_, key) {
+      const cjs = globalThis.codeceptjs
+      if (!cjs) {
+        throw new Error('CodeceptJS host not available — call configure functions from inside a codecept.conf.js / codecept run, or make sure CodeceptJS >= 4.0 is loaded first.')
+      }
+      const target = cjs[name]
+      if (!target) {
+        throw new Error(`CodeceptJS does not expose ${name} on the host registry.`)
+      }
+      const v = target[key]
+      return typeof v === 'function' ? v.bind(target) : v
+    },
+  })
+}
+
+const codeceptjs = new Proxy({}, {
+  get(_, key) {
+    const cjs = globalThis.codeceptjs
+    if (!cjs) throw new Error('CodeceptJS host not available — call configure functions from inside a codecept.conf.js / codecept run.')
+    return cjs[key]
+  },
+})
+
+export default codeceptjs
+export const config = lazy('config')
+export const container = lazy('container')
+export const event = lazy('event')
+export const output = lazy('output')

scripts/upstream-patches/expect-helper-index.js.diff

@@ -0,0 +1,24 @@
+--- a/index.js
++++ b/index.js
+@@ -1,8 +1,21 @@
+ import { use, expect, assert } from 'chai';
+ import chaiExclude from 'chai-exclude';
+ import chaiMatchPattern from 'chai-match-pattern';
+ import chaiJsonSchemaAjv from 'chai-json-schema-ajv';
+-import { output } from 'codeceptjs';
++
++// CodeceptJS output module. Looked up lazily on each property access from the
++// in-process handle the framework registers on globalThis — this avoids a
++// top-level `import 'codeceptjs'`, which fails to resolve inside the codeceptjs
++// repo's own CI (the project IS the codeceptjs package).
++const output = new Proxy({}, {
++  get(_, key) {
++    const o = globalThis.codeceptjs?.output
++    if (!o) throw new Error('CodeceptJS output module not available — make sure the test is running through the CodeceptJS runner.')
++    const v = o[key]
++    return typeof v === 'function' ? v.bind(o) : v
++  }
++})
+
+ use(chaiExclude);
+ use(chaiMatchPattern);