Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(nextjs): Export SentryWebpackPluginOptions type #4597

Merged

Conversation

lobsterkatie
Copy link
Member

This will allow people who want typing in their next.config.js file to have it without digging into dist.

See vercel/next.js#28726.

@lobsterkatie lobsterkatie merged commit 3e481e4 into master Feb 16, 2022
@lobsterkatie lobsterkatie deleted the kmclb-nextjs-export-webpack-plugin-options-type branch February 16, 2022 20:16
lobsterkatie added a commit that referenced this pull request Feb 16, 2022
…dependency check (#4598)

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 module `webpack` and which is depended upon by the local file `config/webpack.ts`.

To solve this for the moment, this excludes the problematic file from the check.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants