Does not work on Vercel inside getServerSideProps from Next.js

Thanks for making this awesome npm package! 😄

• mdx-bundler version: 4.0.0
• node version: 14.16.1
• npm version: 7.12.1

Problem description:

The bundleMDX function seems to doesn’t work in Vercel when it is in getServerSideProps function from Next.js, but it actually works if it is in getStaticProps. Also both work in local, I don’t have errors at all on my local machine. You can see see that currently it is a 500 error page : https://divlo-nlxbiy7k2-divlo.vercel.app/blog/hello-world I saw that there was similar closed issue : #2

You can see the relevant code there : https://github.com/Divlo/Divlo/blob/feat/add-blog/pages/blog/[slug].tsx

Here is the log from the serverless function in Vercel :

ERROR	Error [ERR_MODULE_NOT_FOUND]: Cannot find module '/var/task/node_modules/periscopic/node_modules/estree-walker/dist/esm/estree-walker.js' imported from /var/task/node_modules/periscopic/src/index.js
Did you mean to import estree-walker/dist/umd/estree-walker.js?
    at finalizeResolution (internal/modules/esm/resolve.js:276:11)
    at moduleResolve (internal/modules/esm/resolve.js:699:10)
    at Loader.defaultResolve [as _resolve] (internal/modules/esm/resolve.js:810:11)
    at Loader.resolve (internal/modules/esm/loader.js:86:40)
    at Loader.getModuleJob (internal/modules/esm/loader.js:230:28)
    at ModuleWrap.<anonymous> (internal/modules/esm/module_job.js:56:40)
    at link (internal/modules/esm/module_job.js:55:36) {
  code: 'ERR_MODULE_NOT_FOUND'
}

Thanks for your help!

[Divlo]

We can close this issue! Things work properly on the Vercel platform!

[Divlo]

yarn has resolutions, maybe you could use that to force estree-walker@3 and see if that works.

I don’t use Next and I don’t if they’re doing any “post processing” on getServerSideProps

I did it with npm but the result is the same, Indeed it fixes the issue, thanks for your help! But yes forcing the installation of an npm package by editing manually package-lock.json, it is not great.

So the issue will be definitely be fix once this issue will be closed : https://github.com/Rich-Harris/periscopic/issues/10