Recent from the oven… a bun!
In September, model 1.0 of Bun was launched. So what is that this ‘bun’ factor, can we eat it?
Bun is a quick, all-in-one toolkit for working, constructing, testing, and debugging JavaScript and TypeScript, from a single file to a full-stack utility. Right this moment, Bun is steady and production-ready.
The devs behind bun took Apples JavascriptCore and added a whole lot of ZIG code to construct a whole javascript toolkit. It replaces node.js, transpilers, bundlers, package deal managers and testing libraries.
Though not all FE frameworks are supported but, I’ve acquired unimaginable outcomes when putting in tasks. However much more essential it actually felt like a drop in alternative! Getting it to work solely takes a few minutes.
If you wish to pace up your frontend pipelines I extremely encourage wanting into this instrument to handle your packages!
View Transitions
Nonetheless experimental however again in March Chrome determined to help it! You need to use these transitions to make an online web page behave extra like an app with out including a bunch of javascript libraries.
Theo up to date his astro web site to the newest model to check out it’s implementation of this API and it’s form of thoughts blowing how little work is concerned in getting this to work*!
Server Facet all of the issues!
I’ve been stepping up my NextJS sport over the previous yr, I actually like all of the magic it does for me and with model 14 its including Server Actions!
Since v13 launched server facet parts I used to be form of bummed that I nonetheless wanted to create an API path to deal with my type submission on the server (keep in mind by no means belief the shopper).
However no extra of this! We will now specify if an motion is simply out there on the server.
Rewrite all issues Angular
Angular acquired a shiny new dev portal. However this isn’t all, someplace this month you may anticipate model 17 to drop. And it comes with a great deal of new issues!
For my part an important change is the brand new element stream. I’m hoping they’ve a approach to make this migration straightforward… however I’m nervous the brand new syntax they introduce would require a bit of labor.
Up till now you added an ngIf assertion to a element in your template to show one thing primarily based on logic.
