test(e2e): Assert that there are no funky build time warnings when building Next.js apps#9382
Merged
test(e2e): Assert that there are no funky build time warnings when building Next.js apps#9382
Conversation
added 2 commits
October 27, 2023 07:04
…ilding Next.js apps
AbhiPrasad
approved these changes
Oct 27, 2023
Contributor
size-limit report 📦
|
Contributor
Author
|
wat Next.js is throwing a funky build time warning by itself 🙃 |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Adds a simple assertion for the build output of the nextjs E2E tests that checks if there are any funky compilation warnings.
This PR was brought to you by #9394