fix: conditional assetPrefix for dev mode to fix CSS loading #2445
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
When running the app in development mode, Next.js serves assets locally (http://localhost:3000/_next/static/...), but the
assetPrefix
config innext.config.ts
is telling it to fetch them fromhttps://demo.mem0.ai
. This will make these requests fail with a 404, and the stylesheets don’t load.This PR resolves this issue by adding a conditional check to avoid this. Plus, the
preload: false
is added to fonts, fixing the link preload warning in Next.js.Fixes #2444
Type of change
Please delete options that are not relevant.
How Has This Been Tested?
Tested by
pnpm run dev
, all the assets can be found by Next.js, and the demo website works properly.Checklist:
Maintainer Checklist