Skip to content

Add NextJS example template #966

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

Closed
joepio opened this issue Sep 11, 2024 · 5 comments · Fixed by #1009
Closed

Add NextJS example template #966

joepio opened this issue Sep 11, 2024 · 5 comments · Fixed by #1009
Assignees
Labels
@tomic/lib @tomic/lib @tomic/react @tomic/react

Comments

@joepio
Copy link
Member

joepio commented Sep 11, 2024

  • Start from the Create template #952 #959 branch, but create a new branch. Rebase from time to time to keep Polle's changes synced.
  • Add a new folder for a NextJS project, similar to how there's a SvelteKit project
  • Aim to have a similar look, feel and featureset to the SvelteKit Project.
  • Use the same template (which creates some classes and instances)
@joepio joepio added @tomic/lib @tomic/lib @tomic/react @tomic/react labels Sep 11, 2024
@joepio
Copy link
Member Author

joepio commented Oct 15, 2024

Can you push current WIP branch and mention this issue @RoelLeijser?

@joepio
Copy link
Member Author

joepio commented Oct 15, 2024

Also, include the definition of done doc here!

@RoelLeijser
Copy link
Contributor

When deploying to Netlify sometimes it gives the response:
error decoding lambda response: error decoding lambda response: unexpected end of JSON input
Sometimes is does deploy but, then it 404s the whole (or a part?) of the _next/static/chunks directory. When deploying locally or to Vercel this is not a problem.

image

@RoelLeijser
Copy link
Contributor

Netlify dev also spins up a working server, so I think the problem is on deployment.

Netlify recently changed their next plugin. I think this creates a compatibility problem. The plugin is automatically added when the site is deployed to Netlify, which makes sure the version is up to date. There is no difference when explicitly specifying the version in the netlify.toml file.

@RoelLeijser
Copy link
Contributor

Netlify and Vercel both succesfully deployed 🎉

Solved by adding the --build flag to netlify deploy, not mentioned in https://docs.netlify.com/cli/get-started/. The Netlify CLI always builds before deploying, so I don't know why this fixed it, I think it might have to do with caching.

Netflify https://atomic-blog-template.netlify.app
Vercel https://nextjs-blog-template-woad.vercel.app

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
@tomic/lib @tomic/lib @tomic/react @tomic/react
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants