bud VS goja

Yeah. It seems like Bud is the best option I have to get what I want: https://github.com/livebud/bud/

Hit me up if you have a longer time horizon and want to give https://github.com/livebud/bud a shot!

Awesome!

This would be such a game-changer for server-side rendering Javascript in Go with V8.

I'd love to integrate this into Bud[1].

[1] https://github.com/livebud/bud

I've also been seeing updates on this project, which is kind of preferring Svelte https://github.com/livebud/bud

https://github.com/livebud/bud - similar idea, but uses Svelte (a JS framework) to do the front end stuff. It’s smart enough to render the JS stuff on the server when possible, so you end up with the best of both worlds.

https://github.com/livebud/bud this framework is achieving SSR in go. Not Vue specifically last I saw, but maybe you can draw inspiration from what they did https://www.reddit.com/r/golang/comments/uoxocj/bud_the_fullstack_web_framework_for_go_developers/i8ke92h/?utm_source=reddit&utm_medium=web2x&context=3

See https://github.com/livebud/bud to learn more.

Just to clarify: Fymo is taking the same approach as Bud. See: https://github.com/livebud/bud/discussions/248 for details 🙂

An open-source GoLang project also took the same approach, livebud/bud.

I know how to create APIs. I actually don't wanna do an API link with the front end. You can check a framework built in GoLang, livebud/bud in Github. Seeking something like that, 'cause the project is still being developed.

dop251/goja

Your comment was posted 4 minutes ago. That means you still have enough time to edit your comment to change it so it contains real URLs:

<https://github.com/PuerkitoBio/goquery>

<https://github.com/dop251/goja>

(Please do not reply to this comment—I won't be able to delete it once the previous post is fixed if it contains replies.)

Apparently "not depending on Node or V8" means depending on some random Go JS engine instead.

Goja https://github.com/dop251/goja

Either call a JavaScript interpreter like node with exec.Command and read its stdout, or use a pure Go JavaScript interpreter like goja or otto.

Just to also say this is implemented in pure Go we aren't including V8 or any external dependencies we instead use https://github.com/dop251/goja which is a JS VM written completely in Go.

If you want to serialize a function to JSON one idea may be to embed a scripting language like JavaScript into your program. The goja package is a very good solution: a native ES5 JavaScript (with some ES6 syntax support as well) natively implemented in Go so you can get tight data bindings to your Go types and funcs. For your JSON marshalling you could serialize a JavaScript function source (text) and when reloading that, parse that text with goja to be able to run it dynamically in your Go program. Basically you'd need to get away from pure Go for this and towards something that is JSON compatible to (de)serialize to text.

Not really. It was built in-house and I don't know of anything about it that went public. I recall it using Goja for the JS runtime. Code was embedded into the binary (think embed package). There was some kind of sorcery to convert what would be HTTP network calls in the browser into local function calls during SSR, but I'm hazy on how it worked I'm afraid.