fix(web): exclude e2e files from Next.js production build - #578
Merged
Conversation
The web tsconfig includes all *.ts files, which causes files under apps/web/e2e to be type-checked during `next build`. `apps/web/e2e/launch-stack.ts` imports API test utilities, which are not part of the production web build and causes the Docker web image build to fail. Exclude the e2e directory from the web TypeScript config so E2E infrastructure is checked by the E2E/test tooling instead of Next.js production builds.
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
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.
The web tsconfig includes all
*.tsfiles, which causes files underapps/web/e2eto be type-checked duringnext build.apps/web/e2e/launch-stack.tsimports API test utilities, which are not part of the production web build and causes the Docker web image build to fail.Exclude the e2e directory from the web TypeScript config so E2E infrastructure is checked by the E2E/test tooling instead of Next.js production builds.