refactor: address issue with bazel resolution of peer dependencies (RC) #31784
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.
Key changes include:
Removal of PNPM Hook: The
.pnpmfile.cjsfile, which previously converted peer dependencies into direct dependencies, has been deleted. This workaround is no longer necessary with the adoption of dynamic imports. TheMODULE.bazelfile has been updated to remove references to it.Dynamic Imports
build_webpackpackage, staticimportstatements forwebpackandwebpack-dev-serverare replaced with dynamicimport()calls. This defers their loading until they are actively required during the process.ssr-dev-server,browser-syncis now loaded usingcreateRequirerelative to the workspace root, improving resolution reliability.Build Configuration: Associated
BUILD.bazelfiles have been updated to remove dependency declarations that are now obsolete due to the new lazy-loading approach.