can nextjs be used in a non-javascript framework ?

[sandys]

hi guys,
nextjs is something that we have watched with a lot of excitement. However, the big issue we had was that our api stack is already in python+flask. We want to build several admin dashboards and we are seriously considering nextjs... but it is not obvious on how this will work.

is nextjs supposed to be used as the view layer of a non-javascript stack : say flask or rails ? Somewhat like this - https://realpython.com/blog/python/the-ultimate-flask-front-end/

or is it intended to be a javascript framework ?

[impronunciable]

I don't know if I'm answering your question but next.js is not supposed to replace your backend. Next is a client-side framework that happens to have a server-side component to allow features like HMR and SSR. You can definitely combine it with your flask app.

[timneutkens]

The best description to give Next.js is a frontend server. It can communicate with any backend using getInitialProps 😄 This is a good example: https://github.com/zeit/next.js/tree/master/examples/data-fetch

[sandys]

hi Dan, thanks for the answer! does nextjs need to "run" using a nodejs instance... or can it be built as a static page with everything coming from a CDN ? we would rather not bring in a nodejs dependency into an existing stack. I think I am looking at this - #604 . If this gets done, then the nextjs code gets compiled as a pre-build step and deployed with the flask app (where it gets served as a static asset). no nodejs dependency! I think this issue can be closed - basically, we are looking at server side reactjs to have zero dependency on nodejs.

…

On Wed, May 10, 2017 at 6:39 PM, Dan Zajdband ***@***.***> wrote: I don't know if I'm answering your question but next.js is not supposed to replace your backend. Next is a client-side framework that happens to have a server-side component to allow features like HMR and SSR. You can definitely combine it with your flask app. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#1933 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAEsU8qoVUa-5n8QMSf2PO1i1XTz6IaPks5r4bcIgaJpZM4NWleL> .

[sandys]

hi Tim, I think that description is going to change after #1576 gets released right ? Because then the "server" part goes away and so does getInitialProps (maybe replaced with getStaticInitialProps)

…

On Wed, May 10, 2017 at 7:08 PM, Tim Neutkens ***@***.***> wrote: The best description to give Next.js is a frontend server. It can communicate with any backend using getInitialProps 😄 This is a good example: https://github.com/zeit/next.js/tree/master/examples/data-fetch — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#1933 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAEsUzfvmB9f93JILWetrvEKdohlrwasks5r4b3ogaJpZM4NWleL> .

[impronunciable]

@sandys exactly. You'll be able to use next export and just use it without the nodejs side. AFAIK there are people already using that branch

[timneutkens]

Exactly like Dan said 👍

[rgbkrk]

What would the best way to provide CSRF tokens and base URL to the next app? Query parameters?