Why do some Next.js sites ship a manifest including all routes while others don't? #14779
-
|
I noticed that some sites using Next.js ship a manifest containing info about all routes while other sites don't do this. It's in the
Ship the manifest: Don't ship the manifest: What's the difference? Is it an architecture thing (static vs SSG) or is it a version difference? Perhaps the manifest was moved in recent versions and some apps are still using an older version. I ask because we're building out an admin area but we don't like the idea of making public the existence and location of all our admin routes. If there's a way to disable the manifest then we'd like to do that, otherwise we'll explore how to have two Next.js apps in the same repo so we can share code between our apps. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
It was added as part of https://nextjs.org/blog/next-9-2#improved-code-splitting-strategy given that we need to know what bundles are needed for a route. This has no effect on performance and in general I wouldn't worry about figuring out the routes in that way as there's multiple ways you could figure out that those admin routes exist. |
Beta Was this translation helpful? Give feedback.
-
|
Is there any way to hide or remove it? I'm building a multi tenant site and I don't want to show all domains in the manifest. |
Beta Was this translation helpful? Give feedback.
-
|
@stevemarksd
|
Beta Was this translation helpful? Give feedback.
It was added as part of https://nextjs.org/blog/next-9-2#improved-code-splitting-strategy given that we need to know what bundles are needed for a route. This has no effect on performance and in general I wouldn't worry about figuring out the routes in that way as there's multiple ways you could figure out that those admin routes exist.