Uncaught (in promise) TypeError: fs.readdirSync is not a function #2
Comments
Hey @stickhandle thanks for reporting this. Could you please tell me which env are you running this? Like node version, Chrome version, OS, etc? I tried a fresh new clone, DONE Compiled successfully in 385ms 08:02:07
^C⏎
➜ nextein-example git:(master) npm run export
> nextein-example@1.0.0 export /Users/elmasse/tmp/nextein-example
> nextein build && nextein export
> using build directory: /Users/elmasse/tmp/nextein-example/.next
copying "static" directory
copying "static build" directory
> exporting path: /post/first-post
> exporting path: /post/second-post.html
> exporting path: /cars/bmw
> exporting path: /cars/tesla
> exporting path: /food/pizza
> exporting path: /food/taco
> exporting path: /sub-section/sub-sub-section/sub-one
> exporting path: /home/third-post
> exporting path: /uncategorize
> exporting path: /
> exporting path: /all-posts
> exporting path: /sub-section
> exporting path: /tags
> exporting path: /cars
> exporting path: /food
➜ nextein-example git:(master)
|
Thanks for checking in to this @elmasse. |
Ok, seems to be a Windows issue. I'll fire up a Windows 10 VM and give it a try. Thanks again for your time to report this! |
In case it helps, Firefox gives a little different info.
And while running as http-serve on the out folder, the console output:
|
Hi @stickhandle, Could you try the latest changes? It should install nextein v1.3.1 which should solve this problem. |
Looks good @elmasse . Great work on the quick turnaround. And thanks for nextein. |
Thank you for taking the time to report the issue! And thanks for giving nextein a chance! |
Running a fresh install (clone) with npm run dev , I see the following in the console (for url http://localhost:3000):
On browser (Chrome) page refresh, the page returns correctly.
When clicking any link (in header, like http://localhost:3000/all-posts) page returns as:
Again, on refresh, the page displays correctly.
EDIT: Note the issue presents for npm run export/http-serve scenario as well
The text was updated successfully, but these errors were encountered: