[compiler] Fix misleading code example (#7889)

When the compiler bails out on code, it leaves it untouched and unoptimized, so it's always safe for the compiler to bailout. `panicThreshold` in most cases should be kept as `'none'` unless you want to fail the build on these safe bailouts. It's really only useful during dev when you're working on increasing the coverage of the compiler on your codebase. I think having it shown here is confusing so I'm opting to just remove it for this particular code example.
reactjs · react-translations-bot · Jul 18, 2025 · Jul 18, 2025 · Jul 21, 2025 · Jul 21, 2025
commit d7160a896bce75dddd602dc28c13a4abdfecde2c
@@ -101,16 +101,15 @@ module.exports = {
       test: './src/experimental/**/*.{js,jsx,ts,tsx}',
       plugins: [
         ['babel-plugin-react-compiler', {
-          compilationMode: 'annotation', // Only compile "use memo" components
-          panicThreshold: 'none' // More permissive for experimental code
+          // options ...
         }]
       ]
     },
     {
       test: './src/production/**/*.{js,jsx,ts,tsx}',
       plugins: [
         ['babel-plugin-react-compiler', {
-          panicThreshold: 'critical_errors' // Stricter for production code
+          // options ...
         }]
       ]
     }