Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Fix crypto import in edge runtime with Turbopack (#65171)
## What? Ensures just importing `crypto` does not error, only when it is used it shows an error in the edge runtime. This matches webpack behavior. The `crypto` module was missing the list of unsupported packages in the Next.js Turbopack integration. Fixes #64464 Fixes PACK-2954 ## TODO While adding tests for this issue I found another bug that only happens with webpack. Specifically these 4 packages are accidentally being polyfilled even when they're not set up to be polyfilled. i.e. there's no npm package installed for polyfilling them through aliasing or such. Even in that case `punycode`, `process`, `querystring`, and `string_decorder` get polyfilled regardless, this causes the newly added test to fail. Removing the polyfills would be potentially breaking so we'll want to change it in Next.js 15 instead. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # --> Closes NEXT-3252
- Loading branch information