Ari Perkkiö

> |- TypeError: Cannot destructure property 'plugins' of 'undefined' as it is undefined. > at Module.StarlightIntegration [as default] (D:\GH\Programming-0101\SkunkWorks-DG\omni-kit\node_modules\.pnpm\@[email protected][email protected]_@[email protected][email protected][email protected]_\node_modules\@astrojs\starlight\index.ts:31:2) This error is coming from Starlight: https://github.com/withastro/starlight/blob/83d4507e1a385226879bd64147e4e09fef5f79a2/packages/starlight/index.ts#L30-L33 You'll need to add...

This should be doable, as `child_process.fork()` also supports it: https://nodejs.org/api/child_process.html#child_processforkmodulepath-args-options Though we'll need to make sure it works on Windows too, as we've had URL issues there before.

Proposition for the `runTests` phase here: - `onTestFileQueued(file: TestModule)` - collection of module is about to start - `onTestFileStart(file: TestModule)` - module is about to run - `onHookStart(...)` - `before*`...

> if we report suite hooks (`beforeAll`/`beforeEach`), should we report `onSuiteStart`? Do we need that anywhere? I don't think `onTaskUpdate` reports this atm. Currently slowly running `beforeAll` etc. hooks are...

`beforeAll/afterAll` are showed by reporters, let's keep supporting them like before. I feel like I'm missing something here. 🤔 - https://github.com/vitest-dev/vitest/pull/6893#discussion_r1839800573. https://github.com/vitest-dev/vitest/blob/8764f5c15760c596f408c30ae1849b3284555c81/packages/vitest/src/node/reporters/task-parser.ts#L66-L75


This (and the next PR that actually opens custom runtime API) does expand Tinypool's usage to such use cases. But for Vitest browser mode, @sheremet-va has a bit different idea....

Vite doesn't intercept `node:child_process`. Previous discussion is at https://github.com/vitest-dev/vitest/discussions/3851. Also related to https://github.com/vitest-dev/vitest/issues/4899.

Currently the code editor does not have type aware intellisense. However this is something we are planning to improve in future.

> Is this a different engine? Looks like Angular's tutorial is using the same editor (CodeMirror) that TutorialKit uses. This simply hasn't been implemented on TutorialKit's side.