react: Bug: (17.0.0-rc.0) No changes to Native Component Stacks in production environment

The React 17 RC blog post states “In React 17, the component stacks are generated using a different mechanism that stitches them together from the regular native JavaScript stacks. This lets you get the fully symbolicated React component stack traces in a production environment.”

I’ve been trying to see a difference between React 16.13.1 and React 17.0.0.rc.0, and so far have been unable to do so.

React version: 17.0.0.rc.0

Steps To Reproduce

1. Start a new app with Create React App.
2. Run npm install react-error-boundary.
3. Use the code shown below in your App.js.
4. Run npm run build to create a production build.
5. Start a web server and open in a browser to see the error.

import React from 'react';
import { ErrorBoundary } from "react-error-boundary";

function ErrorFallback({ error }) {
  return (
    <div>
      <p>Something went wrong:</p>
      <pre style={{ color: "red" }}>{error.message}</pre>
    </div>
  )
}

function Bomb(foo) {
  return (
    <>
      <h1>💣</h1>
      {foo.toUpperCase()}
    </>
  )
}

function App() {
  return (
    <ErrorBoundary FallbackComponent={ErrorFallback} onReset={() => {}}>
      <h1>Error Testing</h1>
      <Bomb />
    </ErrorBoundary>
  );
}

export default App;

The current behavior

The stack trace I’m getting is exactly the same with React 16.13.1 and React 17.0.0-rc.0.

The expected behavior

I’m expecting to get component names in my stack trace, or to see some difference in the stack traces between React versions.

Apologies if I’m debugging the wrong thing here, but I’m trying to figure out what actually changed in React 17. Appreciate your time.