fix(ci): Exclude config/types.ts in @sentry/nextjs from circular dependency check
#4598
Conversation
This file contains 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
AbhiPrasad
approved these changes
Feb 16, 2022
lobsterkatie
deleted the
kmclb-nextjs-exclude-config-types-from-madge
branch
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 library we use to detect circular dependencies,
madge, has a bug wherein local files whose names match node modules cause false positives. (For more details, see pahen/madge#306.) In our case, it was triggered by #4597, which added an export from file (config/types.ts) which depends on the node modulewebpackand which is depended upon by the local fileconfig/webpack.ts.To solve this for the moment, this PR excludes the problematic file from the check.