fix(example/with-docker): jest can’t resolve @repo/jest-presets/node #10551
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Issue
examples/with-docker/apps/api/package.jsonandexamples/with-docker/packages/logger/package.jsonboth declare"preset": "@repo/jest-presets/node", but the TypeScript preset file (jest-preset.ts) is not published, so Jest fails to resolve it.Fix
node/jest-preset.tswithnode/jest-preset.js(plain JS, no runtime TS needed).examples/with-docker/packages/jest-presets/package.json:"files""exports"map for./nodeand./node/jest-preset.Outcome
The preset is now resolvable; tests in apps/api and packages/logger run without errors, with no change in preset behaviour.
Testing Instructions
From
examples/with-dockerrunExecute the tests:
pnpm turbo run testor run
pnpm jestinsideapps/apiandpackages/logger.Expectation: no “Cannot find preset '@repo/jest-presets/node'” error; all tests pass.