surface
Koa
Our great sponsors
surface | Koa | |
---|---|---|
11 | 71 | |
1,992 | 34,837 | |
1.7% | 0.4% | |
7.9 | 5.4 | |
17 days ago | 2 days ago | |
Elixir | JavaScript | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
surface
-
htmlgui.nvim - Create html + css + lua apps with neovim as 'browser'. ( proof of concept )
I should have been more clear that my intent was to create/use a compiler for some kind of component syntax. There are lots of them, from Surface (Elixir), Blade (PHP/Laravel), and JSX (React, Vue, Etc)
- Would you still choose Elixir/Phoenix/LiveView if scaling and performance weren’t an issue to solve for?
-
Why I selected Elixir and Phoenix as my main stack
There I learned more deeply about LiveView and Surface UI.
-
Something similar to Vuetify for Phoenix LiveView?
I think Surface is the ideal candidate for this. But it doesn’t have the components you are looking for but you can build anything with it. Hopefully, in future we can have set of headless components built using Surface 🤞
-
Single source of truth with Phoenix LiveView
I have worked with Phoenix LiveView and Surface-UI for about a year; I would like to share some of the things I learned the hard way.
-
Course/Extensive tutorials for Phoenix 1.6?
This is just an idea, but what about implementing using Phoenix.View(via use MyAppWeb, :view in your module)? Then assign I think has access to @conn. Then maybe work some magic to still allow Phoenix.Component syntax - but at this point, this is something I believe is a flow that might be in development. Try investigating / asking in Surface, because that is a lot more similar to React in its approach. In fact, I think Surface is where more aggressive features are pushed out, and ironed-out features get included into Phoenix. This was the case for Phoenix.Component, and HEEX.
-
Porting files generated by phoenix to surface
This post is intended to get you started with surface provided components. I provided the original code and surface versions so you can compare the differences yourself without installing anything. After installing surface following the installation guide https://surface-ui.org/getting_started add surface_bulma in your mix.exs, this will allow you to use the table component.
-
We Got to LiveView
I totally get the "Am I doing this the right way?" feeling, especially coming from Rails where everything was so opinionated and wanting to stay idiomatic.
Phoenix, while it does have opinions, is far less opinionated in the sense that it doesn't do it darndest to force you into certain conventions (for example, if your module name doesn't match your file name, Phoenix won't complain). Its generators do try and push you toward using good DDD practices (which is my opinion is a GREAT thing), but of course the generators are completely optional.
I don't have experience writing large LiveView apps but I would say that if you are familiar with any component-based frameworks (like React), I would take a look at SurfaceUI[1]. It simplifies a few "gotchas" in LiveView (though I would say they are very minor gotchas and worth learning about at some point) and gives you a component-rendering syntax more like React. Once you get going, you'll learn that LiveView doesn't have all the headaches that come with bigger React apps (like having to memoize functions or comparing props to avoid a re-render and whatnot). The recent release candidate for Phoenix 1.6 has made strides for a cleaner component syntax, but if you're having trouble with LiveView, Surface might bring some familiarity.
[1] https://github.com/surface-ui/surface
-
Phoenix 1.6.0-RC.0 Released
Have you seen Surface UI? Pretty cool. Collection of LiveView components. https://surface-ui.org/
- Surface UI – A server-side rendering component library for Phoenix
Koa
-
Hono vs. H3 vs. HatTip vs. Elysia - modern server(less) replacements for Express
Since "Express.js is an old framework that has not evolved for a long time. It's not a good choice for new projects since it can easily lead to security issues and memory leaks." -- H3. Which is also the case for Koa.
-
Instrumenting AWS Lambda functions with OpenTelemetry SDKs
In this example, we're using the serverless framework to quickly set up the Lambda function along with an API gateway for the entry point. The lambda function is a simple Koa REST API with a few functional endpoints.
-
Server-side Rendering (SSR) From Scratch with React
The initial step is to create our entry point, from where the page will be rendered. In this case, we will use the koa framework.
-
The Ascent of Node.js: How a runtime changed the Web
Koa.js: By the team behind Express, Koa.js utilized async/await for middleware, resulting in cleaner and more readable code.
-
Stop using express.js
Koa
-
Node.js Developers: The Key Players in Building Fast and Scalable Web Applications
Koa.js: https://koajs.com/
-
Node JS Microservice Frameworks for Developing Scalable Web Apps.
Koa -Next Generation Node Microservice Framework
-
What is your ideal setup for new project for solo developers
Backend is more tricky. - RESTful APIs I prefer Koajs - For a RPC/microsevice, I have only used gRPC - For a CLI, yargs and inquirer
-
Why I selected Elixir and Phoenix as my main stack
There are lot of different frameworks out there. If you learn one, there is no guarantee that the next job you find will use the same. For example if you learn Express and the next one used Koa or Nest.
-
10 Node.js Frameworks Every Developer Should Know
Koa.js is a minimal and flexible Node.js web application infrastructure, which provides a robust set of features for web and mobile applications. It is an open-source framework developed and maintained by the creators of Express.js, the most popular web framework for Node.js.
What are some alternatives?
react_phoenix - Make rendering React.js components in Phoenix easy
Nest - A progressive Node.js framework for building efficient, scalable, and enterprise-grade server-side applications with TypeScript/JavaScript 🚀
torch - A rapid admin generator for Elixir & Phoenix
Next.js - The React Framework
phx_component_helpers - Extensible Phoenix liveview components, without boilerplate
fastify - Fast and low overhead web framework, for Node.js
phoenix_live_view - Rich, real-time user experiences with server-rendered HTML
Express - Fast, unopinionated, minimalist web framework for node.
Raxx - Interface for HTTP webservers, frameworks and clients
loopback-next - LoopBack makes it easy to build modern API applications that require complex integrations.
plug - Compose web applications with functions
feathers - The API and real-time application framework