Parse issue when page is in .tsx (no front-matter / layouts declared)

[silesky]

This is something I just ran into, and I thought I would make a report, since this project is meant to be a drop-in replacement for @next/mdx.

When the pages are in .tsx rather than .mdx, (any they import mdx) and do not use the built-in layout behavior, I get the following:

/* pages/index.tsx */

import { Layout } from '../layout';
import Home from '../pages-components/home/home.mdx';
const HomePage = () => {
  return (
    <Layout headDescription="Home" headTitle="Home">
      <Home />
    </Layout>
  );
};

export default HomePage;

It also displays the following webpack error:

/* next.config.js */
....
const nextConfig = {
  reactStrictMode: true,
  productionBrowserSourceMaps: true,
};

// Enable MDX in Next.js
module.exports = require('@jsdevtools/next-mdx')()(nextConfig);