refactor(jest-worker)!: allow only absolute workerPath
#12343
Merged
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.
Summary
jest-worker
continued.It might be good idea to accept only absolute
workerPath
.Right now the
BaseWorkerPool
class if trying to resolve relativeworkerPath
fromnode_modules/jest-worker/build/base/BaseWorkerPool.js
. Seems like this might break ifjest-worker
's build is bundled. Or I missed something?More over the main
Worker
class is requiring the sameworkerPath
to be able detect exposed methods: https://github.com/facebook/jest/blob/b89a1bbe3652a3f5a8969ce768f3b74298ca021d/packages/jest-worker/src/index.ts#L31-L33Can the same relative path work in both of the classes, which live in different directories? Not sure. With absolute
workerPath
all is clear and simple.Test plan
Tests should pass.