supertokens-golang VS Next.js

The problem

I am looking for a service or effective technique using which I can get quick and reliable translation of our Node SDK (https://github.com/supertokens/supertokens-node) applied to our Python (https://github.com/supertokens/supertokens-python) and Golang (https://github.com/supertokens/supertokens-golang) SDK.

Our SDKs are not just wrappers around an OpenAPI spec, so we can’t use existing tools to auto generate our backend SDK. Or even if we did, that would only generate a very tiny percentage of our SDK. Other than being API wrappers, our SDKs:

- Provide several overridable functions for users to hook into.

- Manage reading from the request and writing to the response objects of various web frameworks of these languages.

- Expose APIs to via a middleware (that again integrates into various web frameworks). Each API has a lot of logic that includes input checking, business logic of that API, calling various other APIs to do actions like send emails, and finally writing an output JSON.

Currently, we are hand writing each of these SDKs, and as you may imagine, it is very expensive. As a result, we have the Node SDK (which is our most used one) far ahead in terms of features compared to our other two SDKs.

As an example of the set of changes that need to be replicated in the other SDKs, have a look at this PR: https://github.com/supertokens/supertokens-node/pull/670/files (many of the files are build files which can be ignored, but even then, it’s 200+ files changed, a large chunk of which are adding tests).

What I have already tried

I have primarily played around with GPT-4 with different types of prompts for simpler PR changes (for example this PR: https://github.com/supertokens/supertokens-node/pull/782/files).

For the TS code changes, I tried a prompt that gave the raw git diff of the node PR and the contents of the python function in which the changes are to be applied, and then asked to generate python snippet with the changes, and the output was quite accurate.

For test case changes, I gave the existing python test file and added it to ask new test cases based on the diff, and that went quite well too (though not at all perfect - i had a bunch of false imports, or made up function names, but 90% of it was good).

This, of course, is a very simple PR, and it would have taken me lesser time to do it by hand than try with the prompts, but I wonder if there is a way to scale this to make it work (even if it’s 50-60% correct).

My ask

If anyone has experience with working with LLMs for this or a similar purpose, or if there is a service out there which can help me with this, I would love to be connected. You can email me on [email protected].

Thank you!

For backend integration, SDKs are currently available for the following: Golang, Python, and Node.js. Meanwhile, for the frontend, it is available with React.js, React Native, and Vanilla JS (Vue/ Angular/ JS).

Next.js is a powerful React framework that enables developers to build server-rendered applications, static websites, and more. It's designed for production and provides features like automatic code splitting and optimized prefetching.

// source: https://github.com/vercel/next.js/blob/canary/packages/next/src/lib/worker.ts#L121C15-L129C16 for (;;) { onActivity() const result = await Promise.race(\[ (this.\_worker as any)\[method\](...args), restartPromise, \]) if (result !== RESTARTED) return result if (onRestart) onRestart(method, args, ++attempts) }

https://github.com/vercel/next.js/discussions/27666 One of them said 'renaming folder to uppercase' might cause trouble. git might not recognize case-sensetive changes by default.

Next.js has long cemented itself as one of the front runners in the web framework world for JavaScript/TypeScript projects so we’re going to be using that. More specifically we’re going to be using V14 of Next.js which allows us to use some exciting new features like Server Actions and the App Router.

Web frameworks like Next.js will usually include this feature, but do check that they set the caching headers correctly!

Vite and Next.js are both top 5 modern development framework right now. They are both great depending on your use case so we’ll discuss 4 areas: Architecture, main features, developer experience and production readiness. After learning about these we’ll have a better idea of which one is best for your project.

> It’s important to be aware of what you are getting if you go with React, and what you are getting is a far cry from what a framework would offer, with all the corresponding pros and cons.

Would you like to elaborate on that?

In my experience, with something as great, size/ecosystem-wise as React, there will almost always be at least one "mainstream" package for whatever you might want to do with it, that integrates pretty well. Where a lot of things might come out of the box with a framework, with a library I often find myself just needing to install the "right" package, and from there it's pretty much the same.

For example, using https://angular.io/guide/i18n-overview or installing and using https://react.i18next.com/

Or something like https://angular.io/guide/form-validation out of the box, vs installing and using https://formik.org/

Or perhaps https://angular.io/guide/router vs https://reactrouter.com/en/main

Even adding something that's not there out of the box is pretty much the same, like https://primeng.org/ or https://primereact.org/

React will typically have more fragmentation and therefore also choice, but I don't see those two experiences as that different. Updates and version management/supply chain will inevitably be more of a mess with the library, admittedly.

Now, projects like Next https://nextjs.org/ exist and add what some might regard as the missing pieces and work well if you want something opinionated and with lots of features out of the box, but a lot of those features (like SSR) are actually pretty advanced and not always even necessary.

Next.js: For the website and the admin dashboard

Until the time of writing, there is no official example of how to enable runtime environmental variables in a Dockerized Next.js app, as utilizing unstable_noStore would only dynamically evaluate variables on the server (node.js runtime). There is also an interesting discussion regarding this topic on GitHub.

next.js is a very popular React framework. remix-adonisjs includes more functionality through the AdonisJS backend ecosystem, and should be easier to self-host and self-manage.