 |
VOOZH | about |
|
VOOZH | about |
We’re so glad you’re here. You can expect all the best TNS content to arrive Monday through Friday to keep you on top of the news and at the top of your game.
Check your inbox for a confirmation email where you can adjust your preferences and even join additional groups.
Follow TNS on your favorite social media networks.
Become a TNS follower on LinkedIn.
Check out the latest featured and trending stories while you wait for your first TNS newsletter.
The JSR is an open source package registry for modern JavaScript and TypeScript, created last year by the Deno team. But it was never meant to be a Deno project, according to a new post by Ryan Dahl, Luca Casonato and Leo Kettmeir: It’s supposed to be an openly governed JavaScript/TypeScript community service.
To further that end, they’ve created a new independent governing board of directors, complete with a governance charter.
The new JSR board members include:
None of whom are too busy. Ahem.
The team also added the full charter to the article, for those curious about such things. And to be fair, it’s wise to be curious about what happens with your favorite open source offerings.
The JSR is as somewhat self-explanatory, but it’s worth noting that each package has a quality score that’s determined by a number of factors — such as completeness of documentation and optimal type declarations for fast type-checking.
In January, Node released three major Common Vulnerabilities and Exposures (CVEs):
The blog post explains how to migrate, but, in related news, if you can’t migrate right away, there is help: HeroDevs announced this week it will support these three versions of Node.js as part of its Never-Ending Support initiative. HeroDevs is the only option listed in endoflife.date.
HeroDevs is the the founding partner for The OpenJS Foundation’s Ecosystem Sustainability Program, of which Node.js is a part.
LinkedIn has been — like most of us — exploring how to use AI in its many products. One challenge the engineering team faced is how to develop rapid prototypes while still getting feedback from the non-technical domain experts, according to LinkedIn software engineer Ajay Prakash and senior engineering manager Lukasz Karolewski.
“When performing prompt engineering, it is not enough to test just the prompts in isolation, sometimes we need to test multiple prompts chained together using the orchestration frameworks like LangChain,” they wrote this week.
Enter Jupyter Notebooks. Now most of you are probably familiar, but just in case, Jupyter Notebooks are interactive web applications that let users create and share documents that can contain code, equations, visualizations, etc.
“To validate ideas effectively, a very tight feedback loop was necessary to allow for real-time collaboration and iteration,” Prakash and Karolewski wrote. “To achieve this, we adopted a unique prompt engineering process leveraging Notebooks, which broke down barriers between technical and non-technical team members.”
In the article, published Thursday on the site, they explained how Jupyter Notebooks is a reusable solution that “allows engineers to quickly set up custom prompt engineering playgrounds for their use-cases along with test datasets.”
Jupyter Notebooks are also accessible to non-technical users, “making prompt engineering inclusive and user-friendly,” they wrote.
The engineers also noted the challenges LinkedIn faced when trying to deploy large language models in production.
Angular does not *officially* support microfrontends, but this week, Angular developer, trainer and consultant Manfred Steyer wrote a detailed look at how to implement them with Angular using Native Federation.
Steyer created Native Federation, a community project built upon web standards that provide close integration with the Angular CLI.
“To fully decouple the idea of Federation from specific bundlers, I started the project Native Federation several years ago,” Steyer explained. “Native Federation wraps any bundler and communicates with them via an adapter.”
The focus is on portability and standards like ECMAScript modules and Import Maps, he added.
He explores how to use Native Federation with Module Federation to create a “bridging solution” that can used to integrate Micro Frontends built with Angular’s web pack-based builder. Module Federation is a solution that enables lazy loading and dependency sharing, he explained.
“Native Federation builds on these concepts with a focus on standards and portability,” Steyer stated. “It provides a seamless integration into the Angular CLI and its performant esbuild-based ApplicationBuilder, which is also the foundation for advanced features like SSR and hydration.”
ApplicationBuilder was introduced in Angular version 17 and was designed to offer a faster, streamlined build process.
Steyer actually begins the article with useful exploration of the pros and cons of Microfrontends.
“Microfrontends promise significant advantages for enterprise-scale applications, such as enhanced team autonomy and independent deployment,” he wrote. “These benefits make this architectural style particularly appealing in multi-team corporate environments where streamlined communication and rapid development cycles are critical.”
But, he added, there are trade-offs such as an inconsistent UI/UX, increased load times, and complex runtime integrations.
“Furthermore, frameworks like Angular, designed for compile-time optimization, face limitations in runtime integration scenarios,” he cautioned. “The Angular team, therefore, recommends alternatives such as splitting an application into libraries managed within a monorepo, which aligns better with Angular’s strengths in type safety and efficient compilation.”
Do you have Developer News or a story idea to share? Drop us a line.
