Clarify a custom server doesn't mean you can't use an existing backend. #23200
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
leerob
requested review from
divmain,
ijjk,
lfades,
Timer and
timneutkens
as code owners
ijjk
reviewed
Mar 18, 2021
Co-authored-by: JJ Kasper <jj@jjsweb.site>
leerob
commented
Mar 18, 2021
ijjk
approved these changes
Mar 18, 2021
flybayer
pushed a commit
to blitz-js/next.js
that referenced
this pull request
Apr 29, 2021
…d. (vercel#23200) I've been this confusion quite a few times. > So with my requirements, how big of a sin is it to use Next only for the frontend and get all its data, JWT tokens, etc. from my NodeJS backend by calling its respective APIs to said backend? > Even the docs mention that running a custom server is not a great idea...
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
I've been this confusion quite a few times.