DeprecationWarning: No "main" or "exports" field defined

next-mdx-remote 4.0.0-rc.1 node v16.10.0

[DEP0151] DeprecationWarning: No "main" or "exports" field defined in the package.json for ***\node_modules\next-mdx-remote\ resolving the main entry point "index.js", imported from ***.js.
Default "index" lookups for the main are deprecated for ES modules.

[jescalan]

You can ignore the deprecation warning for now. Put up a PR that should get rid of it https://github.com/hashicorp/next-mdx-remote/pull/223

[philsp]

Hmm, building the following (compacted) example from the readme on Node 16.13.2 LTS (Windows (x64)) also shows the deprecation warning. Is there any other way to import this package that I’m missing?

pages/index.js

import { serialize } from 'next-mdx-remote/serialize'
import { MDXRemote } from 'next-mdx-remote'

const Test = () => <em>Test</em>;

export default function TestPage({ source }) {
  return <MDXRemote {...source} components={{ Test }} />
}

export async function getStaticProps() {
  return { props: { source: await serialize('Some **mdx** text, with a component <Test />') } }
}

package.json

{
  "scripts": {
    "build": "next build"
  },
  "dependencies": {
    "next-mdx-remote": "4.0.0-rc.1",
    "next": "12.0.7",
    "react": "17.0.2",
    "react-dom": "17.0.2"
  }
}