Conversation
Replace Jest and ts-jest with Vitest's native Node TypeScript runner, add shared Vitest setup helpers, and configure Vitest-aware linting and Prettier.
Replace ESLint and Prettier scripts/configuration with Oxlint and Oxfmt, retain TSDoc validation through the compatible plugin bridge, and update lint-disable directives.
Run Lara tests in one shared fork with a Weaver environment that initializes before every test and stops Java only after Vitest has completed worker reporting. Replace per-project setup/config files and preserve legacy file isolation.
Expose a fixed-path validator for weaver package distributions and cover missing, symlinked, malformed, and valid java-binaries layouts.
|
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 131659dd2e
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| new URL("./weaverEnvironment.ts", import.meta.url), | ||
| ), | ||
| environmentOptions, |
There was a problem hiding this comment.
Keep code-only tests out of the Weaver environment
When npm run test:code is run from a clean checkout without DefaultWeaver/build/install/DefaultWeaver, this environment calls Weaver.setupWeaver before running even plain Node tests such as code/ChildProcessHandling.test.ts; setupJavaEnvironment then performs readdirSync on the missing distribution and the suite fails before collecting tests. The removed code/jest.config.ts explicitly used the Node environment, so preserve a separate Node project/environment for code-only tests rather than applying the Weaver environment globally.
Useful? React with 👍 / 👎.



No description provided.