add library config changes to migration guide #7175
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
As far as I can tell this is so far only mentioned in this issue comment (it seems to have changed after the blog post listing all the changes in config): webpack/webpack#13584 (comment) I also needed this question and answer to figure it out: https://stackoverflow.com/questions/77951581/webpack-5-builds-for-aws-lambda-with-typescript-runtime-handlernotfound
The committers listed above are authorized under a signed CLA. |
|
@jacalata is attempting to deploy a commit to the Webpack Docs Team on Vercel. A member of the Team first needs to authorize it. |
alexander-akait
approved these changes
Mar 11, 2024
|
I think I still need someone with vercel access to approve a deployment before this can be merged. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
As far as I can tell this is so far only mentioned in this issue comment - it seems to have changed after the blog post listing all the changes in config: webpack/webpack#13584 (comment)
(I also needed this question and answer to figure it out: https://stackoverflow.com/questions/77951581/webpack-5-builds-for-aws-lambda-with-typescript-runtime-handlernotfound)