* Update `packages/` * Update examples * Update tests * Update bench * Update top level files * Fix build * trigger
* Format missed files * Remove unnecessary rule * Fix type error
Fixes #5363 I noticed this happening when making some changes on the nextjs.org/learn app. Basically we didn't apply updates when a warning was emitted from webpack. This would cause issues for users using eslint-loader or similar too.
