Resolve webpack loaders and dependencies relative to kolibri-tools #12052
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
Where you can find the dependencies for each of a project's dependencies depends on that project's package manager. With Studio using
pnpm
, the webpack config becomes relative to the Studio context, and Studio does not declare these dependencies, because it relies onkolibri-tools
as a toolbox for all of them.This PR updates the webpack config to use
require.resolve
on any Webpack loader or plugin that is passed by its string package name. It also updateskolibri-tools
to import all node-specific dependencies using thenode:
protocolReferences
Required by: learningequality/studio#4462
Reviewer guidance
Does anything break?
Testing checklist
PR process
Reviewer checklist
yarn
andpip
)