denoflare
ember-render-modifiers
Our great sponsors
denoflare | ember-render-modifiers | |
---|---|---|
4 | 3 | |
625 | 82 | |
4.2% | - | |
8.8 | 4.4 | |
4 days ago | 11 months ago | |
TypeScript | 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.
denoflare
- Write Once, Run on Cloudflare, Deno Deploy, AWS Lambda, Supabase Edge Functions
-
Building a full stack app with Deno Fresh and Fauna
Fresh really takes a fresh new approach to web dev. It is still quite new but the ecosystem is rapidly growing. Up until now the Deno ecosystem was a missing a full stack framework and Fresh seems to fill that void quite effectively. You can create scalable, performant applications with Fresh and Fauna quite easily. On top of that you can make fully serverless full stack applications on the edge when you deploy your Fresh app to Deno deploy, denoflare.dev or Netlify.
-
Deno Raises $21M
Agree regarding tooling.
So much so that I wrote Denoflare (https://denoflare.dev/) to make writing Cloudflare Workers using standard Deno a breeze: no wrangler, toml, webpack, npm etc required
-
Vercel Welcomes Rich Harris, Creator of Svelte
Do you have experience with denoflare? I really would like to try it, but I can't even get the basic `hello-worker` sample working, see https://github.com/skymethod/denoflare/issues/2
ember-render-modifiers
-
The road from Ember classic to Glimmer components
A second issue was that lifecycle hooks that depended on this wrapping element no longer got invoked. Those lifecycle events contain the Element reference, e.g. didInsertElement. To migrate these we made use of the render-modifiers package. Ever since Glimmer and Octane, there are new ways to encapsulate this logic like using the constructor and destructor, writing custom modifiers, or using resources. For the sake of limiting the scope we opted to keep this a separate effort.
-
Working with Excel Worksheet in Ember
To call a setup/init function after the wrapper component was rendered you could make use of the ember-render-modifiers addon (https://github.com/emberjs/ember-render-modifiers).
-
Vercel Welcomes Rich Harris, Creator of Svelte
What I like about Ember is that it gives a lot of rigid structure that, at least at one point, made it comparatively easy to work on multiple Ember based projects and be productive sooner.
As you've pointed out, a problem with that project is that there's a ton of intimate knowledge for how things work under the hood or why things are the way they are. They also seem to oscillate between opting for simplicity and opting for complexity and magic.
One example would be the latest version of Ember which doesn't even ship with `@ember/render-modifiers` by default despite how everyone will end up installing it anyway because it's necessary; they were talking about providing an alternative based on the actor model, despite modifiers being far easier to understand, somehow they are still wrong:
> Either way, we recommend using these modifiers with caution. They are very useful for quickly bridging the gap between classic components and Glimmer components, but they are still generally an anti-pattern.
https://github.com/emberjs/ember-render-modifiers
Why on earth did they reinvent components and ship them without providing the supposedly correct way of interacting with their lifecycle? You actually have to install a separate add-on to develop a production-ready app with Ember, which completely flies in the face of the idea that you can run `ember new` and have pretty much everything you need.
Strangely (an thankfully), the RFC for the needlessly complicated alternative for lifecycle interaction is effectively stalled:
https://github.com/emberjs/rfcs/pull/567
By their own language, the only official way to interact with component/element lifecycle is an antipattern.
/rant
What are some alternatives?
react-plain - Helper functions for creating DOM elements in React without JSX
SvelteKit - web development, streamlined
prepack - A JavaScript bundle optimizer.
tauri - Build smaller, faster, and more secure desktop applications with a web frontend.
next-runtime - The Next.js Runtime allows Next.js to run on Netlify with zero configuration
jsx - The JSX specification is a XML-like syntax extension to ECMAScript.
svelte-native - Svelte controlling native components via Nativescript