-
Notifications
You must be signed in to change notification settings - Fork 75
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Does not work on Vercel #2
Comments
Ah, I forgot to add a few deps. Fixed now! Thanks! |
@all-contributors please add @benwis for bugs |
I've put up a pull request to add @benwis! 🎉 |
🎉 This issue has been resolved in version 1.0.2 🎉 The release is available on: Your semantic-release bot 📦🚀 |
I hate to be this guy, but updating to the fixed version and redeploying appears to have the exact same error. I wonder if vercel is doing something that prevents rollupBabel from finding it |
Make sure that |
Also, make sure you're using the latest version and don't have the old version in a lockfile. |
Also, I noticed that you don't need |
That's great, I will be using files soon :) I used yarn, the yarn.lock is present and mdx-bundler is a regular dep :) |
Does it work if your run the production build locally? |
Yep, works great locally with yarn start and it contoniues to work on Fly.io with my Express based app |
Can you give me all the logs from a failed deploy on vercel? |
I can but the deploy succeeds without errors. Maybe its because we're missing @babel/core?.
…On Wed, Feb 17, 2021 at 6:03 AM, Kent C. Dodds ***@***.***> wrote:
Can you give me all the logs from a failed deploy on vercel?
—
You are receiving this because you were mentioned.
Reply to this email directly, [view it on GitHub](#2 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/ABVBTCNFX35BV65MUJNLC6TS7PEC5ANCNFSM4XXTLOAQ).
|
|
Adding @babel/core to package.json in the mdx-bundler node_modules folder does not appear to fix it.I'm still not sure if vercel is redownloading my packages or not, but I think it should be. In case its not obvious, feel free to fork or reuse the most recent github example repo. It should be easy to download and deploy it to vercel so you can see any issues and there is nothing secret in it. |
I've just released another version that includes |
And let me know if the error is any different or if it's still: |
Ok, actually, this last commit might fix the issue. Should be released in a moment. Go ahead and give this a try: 52eeea5 |
You did it. As you can see, it works fine now: Dang dynamic imports |
Cool! Thanks for your help here :)
—
Kent C. Dodds
…--- original message ---
On February 17, 2021, 1:47 PM MST notifications@github.com wrote:
Closed #2.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or unsubscribe.
--- end of original message ---
|
First issue! Do I get a prize?
mdx-bundler
version: 1.0.1node
version: 12yarn
version: 1.22.1Relevant code or config
What you did: I setup a pretty straightforward blog post compiler on my vercel app and deployed it.
What happened: I can't get it to work, it always complains about babel missing
Cannot find module '@babel/preset-react' Require stack: - /var/task/node_modules/@babel/core/lib/config/files/plugins.js - /var/task/node_modules/@babel/core/lib/config/files/index.js - /var/task/node_modules/@babel/core/lib/index.js - /var/task/node_modules/@rollup/plugin-babel/dist/index.js - /var/task/node_modules/@remix-run/core/compiler.js - /var/task/node_modules/@remix-run/core/index.js - /var/task/node_modules/@remix-run/vercel/index.js - /var/task/index.js - /var/task/___vc_launcher.js - /var/runtime/UserFunction.js - /var/runtime/index.js
Reproduction repository:
https://remix-vercel.benwis.vercel.app/blog/compile-mdx-on-remix
You can see the error here.
Problem description:
It seems to work fine locally and then not when deployed on vercel. Runs great on my Express app.
Suggested solution:
I don't know, installing the package did not make the error go away. It is definitely in my package.json
The text was updated successfully, but these errors were encountered: