Build fails on Windows but works on WSL about tailwind-nextjs-starter-blog

[DoctorDerek]

@abstractvector Helped me sleuth out that this doesn't seem to be a reported Next.js issue, so it must be something for this project. (Thanks Matt!)

λ npm run build

> [email protected] build
> next build

info  - Using webpack 5. Reason: no next.config.js https://nextjs.org/docs/messages/webpack5 info  - Checking validity of types
info  - Creating an optimized production build
info  - Compiled successfully
info  - Collecting page data
info  - Generating static pages (3/3)
info  - Finalizing page optimization

Page                                Size     First Load JS
┌ ○ /                               7.37 kB        71.4 kB
├   └ css/48fe4f0a1886e63f0800.css  675 B
├   /_app                           0 B            64.1 kB
├ ○ /404                            3.68 kB        67.7 kB
└ λ /api/hello                      0 B            64.1 kB
+ First Load JS shared by all       64.1 kB
  ├ chunks/597.792d30.js            13.2 kB
  ├ chunks/778.98c823.js            7.11 kB
  ├ chunks/framework.bcc415.js      42 kB
  ├ chunks/main.9ca82e.js           151 B
  ├ chunks/pages/_app.017c26.js     565 B
  ├ chunks/webpack.a2d1e7.js        993 B
  └ css/9555fbe4118c83c59ab9.css    203 B

λ  (Server)  server-side renders at runtime (uses getInitialProps or getServerSideProps)
○  (Static)  automatically rendered as static HTML (uses no initial props)
●  (SSG)     automatically generated as static HTML + JSON (uses getStaticProps)
   (ISR)     incremental static regeneration (uses revalidate in getStaticProps)

A npx next-app project works fine for me on Windows 10 (npm run build).

[DoctorDerek]

Hey it's probably a npm / node version issue, I think some of the dependencies require newer npm (like husky needing npm 7 or something wacky). Mine sharing your `npm -v` and `node -v` output? I'm on Windows 10x64 and don't have a successful build on `master` branch either, but it's definitely a different stacktrace: ``` C:\dev λ cd tailwind-nextjs-starter-blog\ C:\dev\tailwind-nextjs-starter-blog (master -> origin) λ npm -v 7.11.2 C:\dev\tailwind-nextjs-starter-blog (master -> origin) λ node -v v15.14.0 C:\dev\tailwind-nextjs-starter-blog (master -> origin) λ npm run build

***@***.*** build next build && node ./scripts/generate-sitemap

'next' is not recognized as an internal or external command, operable program or batch file. C:\dev\tailwind-nextjs-starter-blog (master -> origin) λ npm install

***@***.*** prepare husky install

husky - Git hooks installed added 958 packages, and audited 959 packages in 11s 7 vulnerabilities (1 moderate, 6 high) To address issues that do not require attention, run: npm audit fix To address all issues possible (including breaking changes), run: npm audit fix --force Some issues need review, and may require choosing a different dependency. Run `npm audit` for details. C:\dev\tailwind-nextjs-starter-blog (master -> origin) λ npm run build

***@***.*** build next build && node ./scripts/generate-sitemap

info - Using webpack 5. Reason: future.webpack5 option enabled https://nextjs.org/docs/messages/webpack5 info - Checking validity of types warn - You have enabled the JIT engine which is currently in preview. warn - Preview features are not covered by semver, may introduce breaking changes, and can change at any time. info - Creating an optimized production build info - Compiled successfully info - Collecting page data

Build error occurred

TypeError: Cannot read property 'page' of undefined at C:\dev\tailwind-nextjs-starter-blog\node_modules\next\dist\export\index.js:24:30 at Array.filter (<anonymous>) at C:\dev\tailwind-nextjs-starter-blog\node_modules\next\dist\export\index.js:23:194 at async Span.traceAsyncFn (C:\dev\tailwind-nextjs-starter-blog\node_modules\next\dist\telemetry\trace\trace.js:6:584) at async C:\dev\tailwind-nextjs-starter-blog\node_modules\next\dist\build\index.js:43:49 at async Span.traceAsyncFn (C:\dev\tailwind-nextjs-starter-blog\node_modules\next\dist\telemetry\trace\trace.js:6:584) at async C:\dev\tailwind-nextjs-starter-blog\node_modules\next\dist\build\index.js:25:1475 at async Span.traceAsyncFn (C:\dev\tailwind-nextjs-starter-blog\node_modules\next\dist\telemetry\trace\trace.js:6:584) C:\dev\tailwind-nextjs-starter-blog (master -> origin) λ ```

…

[PWSys]

After I posted the issue I thought I may be behind with npm and node. I updated them both and still have the same result.
❯ npm -v
7.12.0
❯ node -v
v14.16.1

Like you, I am also getting the error

TypeError: Cannot read property 'page' of undefined

The error I originally posted was from the verbose log file. Really, neither seems to give any clues.

WSL can build the application that had npm install run from Windows, indicating it is something directly related to the built, not an issue on the install of packages.

[PWSys]

I can also confirm that other next 10.2 projects build fine on Windowsx64.

[DoctorDerek]

Yep it does seem project specific, but I have no idea where it would be coming from.

[timlrx]

Yes, I develop it on WSL. I would have to take a look at this in more detail to find the problem but it seems to be related to the additional scripts triggered i.e. node ./scripts/generate-sitemap. See if changing the build script to just next build works for you?

I don't run build on windows as it is meant to be deployed and served on Linux servers as opposed to windows servers.

[PWSys]

Thanks @timlrx . I did try the build without generating the site map, with the same results. So it is something with running next build.

[PWSys]

This looks related to #43.

The error below probably being generated because the markdown file isn't loading on Windows.

TypeError: Cannot read property 'page' of undefined

[timlrx]

That's the cause of the failed build. Have fix it and verified that it builds for Windows.

[PWSys]

Thanks @timlrx !