I can't make it run locally following the readme guide. about next-cms-ghost HOT 9 CLOSED

@styxlab Thank you for your assistance with this, you helped me clearing some of my doubts.

from next-cms-ghost.

@dassiorleando: Welcome to this project! It looks like some issue with custom images that you are using.

Could you please start out even simpler, by not changing the env variables (in this case the example project is generated):

1. clone repo
2. yarn
3. yarn dev

Let's see if that works and we'll take it from there.

from next-cms-ghost.

@styxlab, I had the same error but once switched to Node 12.16.1 it worked fine.

from next-cms-ghost.

Interesting, what node version were you using before?

from next-cms-ghost.

@styxlab I was using NodeJS v10.19.0.

But still, my own Ghost installation that runs on Heroku using ghost-on-heroku doesn't work.

from next-cms-ghost.

Node requirement comes from Next.js and should be v10.13.0 at the minimum, but using node v12 (or better v14) is recommended. If I understand you correctly, the example project is now working, but when you source your own content, the project is not compiling? For further debugging I need:

1. A list of exact config changes that you made
2. The error log from yarn build

from next-cms-ghost.

It's strange and maybe a local problem, I'm not sure yet.
I have just succeeded in deploying my Ghost on Heroku deployment using Vercel, they use Node 14.

I'm now using Node14 on my PC, but yarn dev doesn't work while yarn build compiles successfully.

The yarn dev error that I have is on the App itself, using Chrome Inspector tool (debugger) I'm able to see this:

Failed to load resource: the server responded with a status of 404 (Not Found)
webpack.js?ts=1621773317918:733 Uncaught (in promise) ChunkLoadError: Loading chunk node_modules_next_dist_client_dev_noop_js failed.
(error: http://localhost:3000/_next/static/chunks/fallback/node_modules_next_dist_client_dev_noop_js.js)
at Object.webpack_require.f.j (http://localhost:3000/_next/static/chunks/webpack.js?ts=1621773317918:733:29)
at http://localhost:3000/_next/static/chunks/webpack.js?ts=1621773317918:154:40
at Array.reduce ()
at Function.webpack_require.e (http://localhost:3000/_next/static/chunks/webpack.js?ts=1621773317918:153:67)
at Function.fn.e (http://localhost:3000/_next/static/chunks/webpack.js?ts=1621773317918:368:50)
at eval (webpack-internal:///./node_modules/next/dist/client/next-dev.js:31:21)
at Object../node_modules/next/dist/client/next-dev.js (http://localhost:3000/_next/static/chunks/main.js?ts=1621773317918:589:1)
at Object.options.factory (http://localhost:3000/_next/static/chunks/webpack.js?ts=1621773317918:685:31)
at webpack_require (http://localhost:3000/_next/static/chunks/webpack.js?ts=1621773317918:37:33)
at webpack_exec (http://localhost:3000/_next/static/chunks/main.js?ts=1621773317918:1335:61)
hot-dev-client.js?eeae:196

from next-cms-ghost.

I have found a solution, I'm not sure about what's happening behind but once deleted the .next folder it worked fine.

from next-cms-ghost.

Glad you found a solution.

from next-cms-ghost.