ember-cli-pagination
rfcs
| ember-cli-pagination | rfcs | |
|---|---|---|
| 1 | 17 | |
| 272 | 794 | |
| - | 0.4% | |
| 1.8 | 9.2 | |
| almost 2 years ago | 6 days ago | |
| JavaScript | Shell | |
| 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.
ember-cli-pagination
-
Real talk: Did I make a mistake choosing Ember for my app?
ember-cli-pagination https://github.com/mharris717/ember-cli-pagination
rfcs
-
Support for in/inter page linking / scrolling in EmberJS
Navigating to URLs with #hash-targets in them is not supported by most single-page-app frameworks due to the async rendering nature of modern web apps -- the browser can't scroll to a #hash-target on page load / transition because the element hasn't rendered yet. There is an issue about this for Ember here on the RFCs repo.
- 🎉 The JS representation of Template Tag has moved to Final Comment Period! This RFC coincidentally exposes a much nicer runtime compiler API! (so I'm interested in this for my REPL, tutorial, and docs sites)
- Official support for pnpm has moved to Final Comment Period -- soon you won't have to add `--skip-npm` and other dances when wanting to use `pnpm` with Ember.
-
The road from Ember classic to Glimmer components
Ember.js development doesn’t stagnate. Progress is already being made for new improvements to the current component model. The RFC for first-class component templates has been accepted and merged in 2022 and will provide new benefits to Ember users. By first adopting Glimmer components, we’re prepared for what’s coming next.
-
"Why would I use Ember over Vue?" or "Are my impressions of the framework landscape based at all in current fact?"
yeah, I think that's being designed (for runtime).We have build-time efforts / validation already via official typescript support https://github.com/emberjs/rfcs/pull/748 with Glint: https://typed-ember.gitbook.io/glint/
-
[AskJS] What's your opinion about React 18 and do you feel the framework is at the forefront of innovation compared to Vue, Angular, Ember, Meteor, Mithril, Polymer and the others... is it going the right way for you or you would have changed a few things ?
During the 4.x series, we aim to finish the work to officially support TypeScript.
-
TypeScript Features to Avoid
The latest versions of Ember.js (Octane) have built-in decorator support and they're discussed in the RFC:
https://github.com/emberjs/rfcs/blob/master/text/0408-decora...
https://guides.emberjs.com/release/in-depth-topics/native-cl...
-
[oc] svelte-tippy a tippy.js action for svelte with full typescript support!
At ok, legit. that's like a modifier from ember.
-
Real talk: Did I make a mistake choosing Ember for my app?
have you seen: https://github.com/emberjs/rfcs/pull/779? I think that addresses the "where does this come from?" in completion.
-
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?
ember-bootstrap - Ember-cli addon for using Bootstrap as native Ember components.
prepack - A JavaScript bundle optimizer.
ember-functions-as-helper-polyfill - Implementation of RFC 756, Default Helper Manager
jsx - The JSX specification is a XML-like syntax extension to ECMAScript.
torii - A set of clean abstractions for authentication in Ember.js
language-tools - The Svelte Language Server, and official extensions which use it
svelte-native - Svelte controlling native components via Nativescript
react-use - React Hooks — 👍
denoflare - Develop, test, and deploy Cloudflare Workers with Deno.
react-plain - Helper functions for creating DOM elements in React without JSX
ember-sinon-qunit - Sinon sandbox test integration for QUnit
htmx - </> htmx - high power tools for HTML