Next Build
#17027
Replies: 1 comment 7 replies
-
I think you might be confusing two separate things.
|
Beta Was this translation helpful? Give feedback.
7 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
My doubt is the following one:
If my webapp is on production mode (online), and I need to commit a new change and by this, it will requires me to run the command 'next build'. My question is, if everytime that I hit 'next build', I would need to restart the webapp?
The origin of my doubt is:
Let's suppose that I have made a webapp using Next with a custom server. And let's imagine that my webapp has a 'Function', or 'Method', that somehow receives a new page to the folder page, with a brand new component that my original webapp doesn't have. So, by the all means, I would need to run 'next build' to make it effective. However, if I do it, my concern is if it will not 'break/crash' the on-going webapp that it's online.
Sure thing I can use the '/page/[:slug]', however, it's only effective if my webapp has all components/code for it. The origin point is that the 'Function/Method (mentioned previous)', will receive a new file for the folder page (doing it from the server, of course), with a code (component) that my webapp don't have originally.
Beta Was this translation helpful? Give feedback.
All reactions