rfcs
next-runtime
Our great sponsors
rfcs | next-runtime | |
---|---|---|
17 | 12 | |
793 | 601 | |
0.5% | 3.3% | |
9.2 | 9.2 | |
3 days ago | 17 days ago | |
Shell | TypeScript | |
- | 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.
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
next-runtime
-
5 Ways to Redirect URLs in Next.JS
I say "when it works" because it's not necessarily supported by all hosts. For example, Vercel of course supports it, but Netlify doesn't currently appear to. As for other hosts, you'd need to verify with them, but I'd imagine it varies.
-
My 2023 Year in Review
View on GitHub
-
4./ Client components in static and dynamic routes before Next 13
Note: at the time of writing this, there is a bug in Next (13.4.7). Although Next guarantees that you can use both app router and pages router in the same project, there is a bug that causes a full page reload when you browse from an app route to a pages route or vice versa. This is unfortunate but does not influence our tests.
-
My experience deploying a Next.js application on Netlify (using Next App Router)
So adding an edge function was the only workaround I found. Apparently it's an issue they're working on and I think it should be set as high priority since trailing slashes matter for SEO.
- What is server costs (resources) with Next.js ISR?
-
Next.js rewrites
Here are a great guide on what to use when: https://github.com/netlify/netlify-plugin-nextjs/blob/main/docs/redirects-rewrites.md
-
Netlify: Improved workflow and new role for pricing changes
It also seems like an unconscious acknowledgement that their add-on services (form handling, post-processing, identity, analytics, auth, etc.) are woefully inadequate in some cases and uncompetitive in others. $20/mo for form handling beyond 100 submissions? Okay, maybe. But the feature set is so bare it's laughable. There's minimal to no customization for notification emails, no confirmation emails, and their post-processing for form detection will bring the speed of your build pipeline to its knees on any serious site. On one site turning off post-processing yielded a build time reduction of more than double the actual build time of the site.
Not to mention the fact that by foregoing any concept of a server and forcing everything into some flavor of lambda they've created a scenario where every framework with any such functionality requires open source shepherding to function on their platform[0]. At best they've diluted their initial mission and at worst they've created an unmanageable mess. They can't even make Next.js work on their platform without causing what should issue 404s to return 500s instead[1]. The SEO implications for that are a potential death sentence and that issue has now been open for five months.
I was very optimistic about Netlify at the outset, and it worked great and still continues to work great for our test cases where we've deployed individual LPs. Where the pain seems to start is anything above a thousand pages or more, which is also coincidentally where the stakes start to get higher. I don't know how they could expect anyone at an enterprise or growing business to seriously scrutinize this platform and view it as ideal with that in mind.
[0]: https://github.com/netlify/netlify-plugin-nextjs
-
Next.js measurement: Serve images in next-gen formats even when using next/image
I don't think Netlify supports WebP currently: https://github.com/netlify/netlify-plugin-nextjs/issues/687
- Vercel Welcomes Rich Harris, Creator of Svelte
-
Make a Custom Portfolio Site Generator with StepZen's Developer Publishing Pack
I made the template here using NextJS, because Netlify has a NextJS plugin, which automates the process of using serverless functions. I inserted the call to my StepZen GraphQL endpoint in the pages/api folder to keep sensitive info off the client.
What are some alternatives?
prepack - A JavaScript bundle optimizer.
joystick - A full-stack JavaScript framework for building stable, easy-to-maintain apps and websites.
jsx - The JSX specification is a XML-like syntax extension to ECMAScript.
language-tools - The Svelte Language Server, and official extensions which use it
services - Real World Micro Services
svelte-native - Svelte controlling native components via Nativescript
denoflare - Develop, test, and deploy Cloudflare Workers with Deno.
react-use - React Hooks — 👍
SvelteKit - web development, streamlined
ember-render-modifiers - Implements did-insert / did-update / will-destroy modifiers for emberjs/rfcs#415