Hello,
If you are facing the same error, simple steps to fix it, is to just follow the below link topic from Vercel:
Hope this helps to resolve your issue!
Happy learnings.
Tag: vercel
Hello,
If you too facing this error : Module not found: Error: Can’t resolve ‘private-next-pages/’ in ‘/vercel/path0’
while deploying your NextJs project over Vercel platform, please follow what solution and mistake I was doing.
As, I tried to debug this error by right away check the the next in the log highlighted (in screenshot above) recommending to following alias rule to be set if you have touched you next.config.js file with any webpack settings.
In my case I did have to touched the next.config.js file and so I have add the same lines of code recommend in the follow link of Next.js doc
But for me still I didn’t found the right solution, because was in the naming of folder under nextjs project.
Basically, I was loading the static content into the dynamic route in Nextjs (Like example reference here).
What I have missed was the name of the folder under pages directory I have created named as “learn” it should be similar to name “posts” as created one at root level of the project to hold the “.md” or “.html” file content to pass down to dynamic route page which will be under /pages/posts/[id].js
Sharing here screenshot of the directory where the naming was a mistake
After renaming the folder name “learn” to “posts” the error went off and found my deployment working successfully.
Hope this small mistake tip help you to solve this problem.
If you have found any mistake in the post. Please don’t hesitate to hit me on my email jat@doableyo.com to rectify.
Enjoyed reading this? How about sharing with your friends or in groups, this would help!
Thanks, Happy Learning!
Hello there, welcome to my random question post.
I was facing small issue to add multiple address to bcc to the sendgrid nodejs example :
What I was tried to do ( which was wrong in accepting as sendgrid bcc parameters value)
let testAccount = {
emailSubject: subjectMsg,
emailFrom: `Application <${process.env.CESEmailFrom}>`,
emailTo: email || process.env.OWNER_TO_EMAIL_ADDRESS,
emailBcc: process.env.OWNER_EMAIL_ADDRESS //note here
};(this is just a payload I am preparing to pass to seng-grid function), process.env.OWNER_EMAIL_ADDRESS was holding values like : email1@testdomain.com, email2@testdomain.com so which is incorrect to pass a comma separated string value.
Instead, we just need to tweak a little at the same bcc, line to pass it as Javascript Array value. Here is the example of working code (note the bcc line in the code below):
let testAccount = {
//user: process.env.CESUsername,
//pass: process.env.CESPassword,
emailSubject: subjectMsg,
emailFrom: `Kitchen Anak <${process.env.CESEmailFrom}>`,
emailTo: email || process.env.OWNER_TO_EMAIL_ADDRESS,
emailBcc: process.env.OWNER_EMAIL_ADDRESS && process.env.OWNER_EMAIL_ADDRESS.split(',') || '',
};Using javascript split function, I was able pass it as a array, isn’t that simple? 🙂
Facing other error related to sendgrid bcc option
Along this, I have also then faced error after fixing above, still on my Vercel deployment code, then which was related to sendGrid bcc parameter for multiple email address.
According to sendGrid documentation we should have unique email address for ‘to’, ‘cc’ and ‘bcc’ options while sending email, in my case I was having ‘bcc’ email address set in at ‘to’ option.
Hence, so creating a duplicate error log at API level of code. (attaching screenshot of error occurred) and then fixed it by removing or keeping all the ‘to’ and ‘bcc’ parameters unique! Volia, that simple 🙂
Result after correcting email address successful.
Thanks for visiting & Happy Learning!