Declare the types for require.context #86042
Conversation
This API is available for both Webpack and Turbopack users. Even for Webpack users, Next.js just doesn’t use the webpack package nor the types it provides. The types are an exact copy of the types provided by webpack, so there’s no conflict if a user does have its types available.
|
Allow CI Workflow Run
Note: this should only be enabled once the PR is ready to go and can only be enabled by a maintainer |
hugotiger
left a comment
hugotiger
left a comment
There was a problem hiding this comment.
Nice fix! I noticed the mode option isn’t supported in Turbopack at the moment — do you think that’s something we should consider in this context?
I might be misunderstanding, but it seems like this also adds these types for fully Turbopack-powered setups 🤔
|
I noticed this too. Initially wrote the types myself, but it turned out those types conflicted with Webpack. Also users may use Webpack themselves, in which case |
|
Ahhh yes that makes sense! Hopefully there's a possibility to type the different environments separately in the future 😄 |
3 participants
What?
Define types for
require.context.Why?
This API is available for both Webpack and Turbopack users. Even for Webpack users, Next.js just doesn’t use the webpack package nor the types it provides.
How?
The types are an exact copy of the types provided by webpack, so there’s no conflict if a user does have its types available.