Skip to content
Sign inJoin waitlist

Troubleshooting — Marai Neesu Next.js

Most problems with this Next.js template come from a content typo, a missing image or a form variable not set on the host. Those answers come first.

Then come the questions buyers ask most.

npm install fails, or the site behaves oddly after an update. Delete node_modules/ and package-lock.json, then npm install again. Check that node -v is 20.9 or newer.

Port 3000 is already in use. npm run dev -- -p 3001, or stop whatever holds the port.

npm run dev or npm run build stops with “Failed to fetch font Manrope”. The font is downloaded from Google Fonts when the site builds (and the first time the development server runs), and the message ends with “Please check your network connection”. Connect, check your proxy or firewall, and run it again. To build without that download, host the font yourself with next/font/local (Making it look like your brand).

Module not found: Can't resolve '@/content/…' The path or the file name is wrong. @/ means src/, so @/content/site is src/content/site.ts. File names are case-sensitive on the servers that build your site, even when they are not on your laptop.

Property 'x' is missing in type … A content item lacks a field that src/content/types.ts requires. Your editor names the file and the line; add the field, or mark it optional in the type.

Cannot find name 'PageProps' (or 'LayoutProps') from npx tsc --noEmit. Next.js generates those types into .next/. Run npm run dev or npm run build once (or npx next typegen), then check again.

An image does not appear. The file must be in public/images/ and the content must refer to it as /images/<file>: same spelling, same extension, no public in the path. An image from another address (a CMS) needs its host in images.remotePatterns in next.config.ts.

A photo is cropped in the wrong place. Every photo sits in a frame and is cropped to fill it, from the centre, and the frames change shape between phone, tablet and desktop. Crop the photo to the shape you want and keep the subject away from the edges (Editing the content).

The build fails but npm run dev was fine. The build is stricter: it checks the types and renders every page. Read the first error, not the last; it names the file. A common cause is a missing field in a content item (the development server doesn’t check types).

The build stops after I added an icon. The style guide lists every icon on purpose, so a new one must be added to icons in src/app/style-guide/tokens.ts, or delete src/app/style-guide/ (Making it look like your brand).

A form says “Something went wrong”. The provider rejected the request, or a variable is missing. The reason is in your host’s function logs (Vercel: the deployment’s Logs tab), after [forms] New contact inquiry could not be delivered (or “New newsletter subscriber”). Check that the environment variables are set for the environment you deployed to, that FORM_PROVIDER names a provider that exists, and redeploy after adding them. The Contact form also shows it when a required field arrives empty: a field you made required must be on the page (Forms).

A form says “Thank you” but nothing arrives. With FORM_PROVIDER=console (the default, also when the variable is missing) submissions are only written to the server log: set a provider (Forms). If you added a field named fax, rename it: that name is the hidden spam trap, and a submission that fills it is dropped.

The share image or title is the old one. Facebook, LinkedIn and X cache them. Use their debuggers to refresh, and confirm that site.url is your domain.

The desktop header disappears when I scroll. That’s on purpose, as on the original design: scrolling down fades the bar, the logo and the Contact button and leaves the menu; scrolling up, or a click on the menu, brings them back (Pages and sections). Tablets and phones keep the full bar.

A link I added to the menu doesn’t show on phones (or the other way round). The header’s menu is navigation and the phone menu phoneNavigation, two lists in src/content/site.ts: add the link to both.

The footer’s clock shows the wrong time. It shows the current time in footer.timeZone (an IANA name such as "Europe/London"), next to footer.city, both in src/content/site.ts. It is empty until the page’s script runs.

A project’s badge leads to the Services page instead of the service. The badge links to the “More Details” address (url) of the service whose title matches the project’s service, letter for letter; when none matches, it falls back to the Services page.

The “I’m interested in” choices of the Contact form are wrong. They are the titles of the services in src/content/collections/services.ts: rename or remove a service and the choices follow.

The Blog shows only six posts. That’s on purpose: “Load More” shows the rest, and every post is in the page’s HTML from the start. Change pageSize in src/content/pages/blog.ts to show more at first.

A new post isn’t first in the Blog. The Blog doesn’t sort by date: it shows the posts in the order of src/content/collections/posts.ts, newest first in the demo. Put the new post at the top of the list.

“See more posts” is missing under a post. No other post has the same category (the spelling and the capital letters must match), and the section is left out then.

Nothing moves: the tickers stand still. The visitor’s system (yours, if you see it) has “reduce motion” switched on, and the site honours it (Making it look like your brand).

An AGENTS.md or a CLAUDE.md appeared in the project. Next.js 16.4 adds them when npm run dev runs next to an AI coding assistant (Install and run). Keep or delete them; the site doesn’t use them.

Can I use this template for a client? See License: that is the one place that answers it for your licence.

Can I remove the style guide, a whole page or a section? Yes:

  • the style guide: delete src/app/style-guide/;
  • a page (the Course or the Products, if you sell nothing): see Pages and sections;
  • a section: delete its line in the page file, for example <TestimonialsSection … /> in src/app/page.tsx (Pages and sections).

Can I change the font to my brand’s? Yes: Making it look like your brand.

Do I need a CMS? No. Content is files you edit. Add one when somebody who does not use a code editor has to publish (Using a headless CMS).

Can I write the site in another language? All the copy is content, so write it in your language, including the screen-reader labels in menuLabels (src/content/site.ts) and src/content/pages/shared.ts. Then set lang in src/app/layout.tsx (and locale in its openGraph and in src/lib/meta.ts) and the date formats in src/lib/format.ts ("en-US"). The template has no language switch or language-based routing.

Does the site need a cookie banner? As shipped, the template sets no cookies and loads no third-party scripts: the font is served from your own domain. Any analytics you add is yours to declare.

Can I show dates in another format? Yes. Post dates (“Jul 8, 2024”) come from formatDate and project months (“September 2023”) from formatMonth, both in src/lib/format.ts.

Can I sell a site I build with this? Building sites for clients is what the licence is for; reselling the template itself as a template is not. The licence has the exact wording.

Will it work with Tailwind plugins, shadcn/ui, or my component library? Yes. It is a standard Next.js + Tailwind CSS 4 project; add packages as usual. The design tokens are plain CSS variables, so other libraries can read them.

How do I update to a new version of the template? Download the new release and copy your src/content/, public/, your icons and your theme.css into it. Then re-apply any component changes you made. CHANGELOG.md lists what moved.

Can you customise it for me, or build my site? Yes. Marcframe, the studio behind this template, updates templates to your needs (brand, content, new pages and features), builds custom templates and designs new websites. Get in touch at marcframe.com/contact or hire us on Contra.

Something is broken and none of this helps. Support and updates: https://framebrick.co/support. Send the page, the browser, and the error text or a screenshot: it makes the answer much faster.