Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Does not seem to build on MacOS #50

Closed
timmeade opened this issue Feb 1, 2024 · 4 comments
Closed

Does not seem to build on MacOS #50

timmeade opened this issue Feb 1, 2024 · 4 comments
Assignees
Labels
bug Something isn't working

Comments

@timmeade
Copy link

timmeade commented Feb 1, 2024

I am working on a M1 Mac.

This does not seem to work on it.

Contentlayer on pnpm dev (or yarn dev) stops at:

Contentlayer config change detected. Updating type definitions and data...

On research i found that 'yarn build' needs to be run in the vscode terminal. As it will not run in macos terminal. I verified this is true. Upon running under vscode I get:

> Build error occurred
Error: Failed to collect page data for /_not-found
    at /Users/tim/Code/labs/next-forge-working/node_modules/.pnpm/[email protected]_@[email protected]_@[email protected][email protected][email protected]/node_modules/next/dist/build/utils.js:1258:15
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
  type: 'Error'
}
error Command failed with exit code 1.

Pulling the plug on this now. Looks great on paper but not enough time currently to fix these issues. Maybe later.

Tim

@timmeade
Copy link
Author

timmeade commented Feb 1, 2024

Looks like contentlayer is not being maintained currently:

contentlayerdev/contentlayer#615

Seems to be issue I am seeing

@timmeade
Copy link
Author

timmeade commented Feb 1, 2024

OK I took a shot and run pnpm dev inside vscode terminal.

I was able to get the first page.

Note: the prisma studio is still throwing and error.

@haydenbleasel
Copy link
Owner

Yeah I'm running into that contentlayer problem intermittently. Might swap out for next/mdx.

@timmeade What error is Prisma Studio throwing?

@haydenbleasel
Copy link
Owner

Hey folks, might be fixed now that the deps are bumped and I migrated to the temp contentlayer2 fork. Let me know how you go.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants