Discussion on: Creating a Markdown Blog with Next.js

View post

Hello!
I'm appreciating your app.
I could try a migration to your blog app.
However, after all migrations, sudden errors come out...
The matter is, I could not figure it out or fix it...

the errors come out after my all previous markdown posts migrations.
however, the funny thing is, last night when I complete all mitration and deploy on
'now', that was no problem at all.. but after a sleep,

sj-log.now.sh/
you can check the deployment was successful last night.

Do you have any idea of this?
Thank you!

$ npm start

> next-blog@3.2.1 start C:\sj-log
> node server.js

Defining routes from exportPathMap
(node:18352) UnhandledPromiseRejectionWarning: TypeError: Missing pattern at 27
    at lexer (C:\sj-log\node_modules\path-to-regexp\dist\index.js:82:23)
    at parse (C:\sj-log\node_modules\path-to-regexp\dist\index.js:97:18)
    at stringToRegexp (C:\sj-log\node_modules\path-to-regexp\dist\index.js:329:27)
    at pathToRegexp (C:\sj-log\node_modules\path-to-regexp\dist\index.js:403:12)
    at Object.match (C:\sj-log\node_modules\path-to-regexp\dist\index.js:248:14)
    at C:\sj-log\node_modules\next\dist\next-server\server\lib\path-match.js:6:42
    at DevServer.addExportPathMapRoutes (C:\sj-log\node_modules\next\dist\server\next-dev-server.js:5:41)
(node:18352) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 2)
(node:18352) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Kendall Strautman • Dec 18 '19

Hi there! Not sure about this error. The finished sample repo is deployed fine for me on Netlify right now. Maybe make sure the build command is correct? It's hard to tell without more information!